Hi @Prateek Rathore , the first issue could be caused by your application (trough its runtime) not supporting or using TLS 1.2 which is the version required by Azure AD B2C however it catches my attention that reaching one of the custom domains has no issue. Are you targeting both custom domains from a single deployed application?
Second issue must be a consequence of first request failing thus no OpenID Connect metadata document is available.
Let us know if this answer was helpful to you or if you need additional assistance. If it was helpful, please remember to accept it and complete the quality survey so that others in the community with similar questions can more easily find a rated solution.