Email Account Reads, Couldn't Sign in. Your Domain Reqires Device Management

You don't have to surrender your unique, brand-centric domain names with Firebase Hosting. You can use a custom domain (like instance.com or app.example.com) instead of a Firebase-generated domain for your Firebase-hosted site.

Firebase Hosting provisions an SSL certificate for each of your domains and serves your content over a global CDN.

The remainder of this certificate walks you lot through these steps to connect your custom domain.

Fix your domain for Hosting

Make certain that you've completed the "Get Started" wizard from your project's Firebase Hosting page so that yous have a Firebase Hosting site in your Firebase project.

Step 1: Add together domain

1. From your projection's Hosting folio, enter the wizard for connecting a custom domain:

   • If you have only one Hosting site, click Connect domain.
   • If you have more than i Hosting site, click View for the desired site, so click Connect domain.

2. Enter the custom domain proper noun that you'd similar to connect to your Hosting site.

3. (Optional) Bank check the box to redirect all requests on the custom domain to a second specified domain (such that case.com and world wide web.instance.com redirect to the same content).

4. Click Continue to initiate the validation process.

Pace 2: Verify domain ownership

If requested in the Connect Domain setup wizard, verify your apex domain.

These steps ensure that your domain is non already linked with a Firebase project and that you lot own the specified domain.

1. In your domain provider'southward site, locate the DNS management page.

2. Add together and salvage a new tape with the following inputs:

   • Blazon: Add a TXT record.

     Firebase Hosting requires that you keep this TXT record continually present in your DNS settings to testify your ownership of the domain and to authorize Firebase to assign and renew SSL certificates for your site.

     Your domain provider may list this term every bit "Record Type".

   • Host: Enter your noon domain key.

     Proving your ownership of an apex domain, or root domain, proves your ownership of all its subdomains.

     Your domain provider may listing this term every bit "Host Name", "Name", or "Domain".

   • Value: Copy the unique verification value into the field.

     Firebase Hosting checks for this value to testify your domain ownership.

     Your domain provider may listing this term as "Data".

3. Allow upward to 24 hours for propagation of your updated TXT records, then click Verify.

   Note that you lot may click Abolish to safely shut the Connect Domain window and reopen at a later time. This does not affect the propagation fourth dimension, but you will exist prompted to re-enter your domain name when you reopen the window.

   After ample propagation time, clicking Verify in the Connect Domain window of the Firebase console allows you lot to begin the SSL certificate provisioning process.

   In well-nigh cases, propagation of your records and verification of your domain volition happen inside a few hours, depending on your domain provider. Refer to your domain provider's documentation for detailed instructions for adding TXT records and propagation times.

   If clicking Verify prompts an error message, your records have not propagated or your values may exist incorrect.

Step 3: Go live

In the Connect Domain window of the Firebase console, select Quick Setup for a new site or Advanced Setup if you already have a site running on another hosting provider and need a zero-reanimation migration.

Quick Setup

1. Return to your domain proper name provider's DNS management site to create DNS A records pointing your page to Firebase Hosting. Add and relieve records with the following inputs:
• Type: Add two DNS A records.
  
• Host: Enter your custom domain cardinal for both records.

The host you betoken is the domain on which you want to serve content; this domain can be an noon domain or subdomain.

Your domain provider may list this term equally "Host Proper name", "Name", or "Domain".

• Value: Assign ane value to each DNS A tape to point your domain to the specified IP addresses.
Your domain provider may list this term equally "Information", "Points To", "Content", "Address", or "IP Accost".
2. Allow time for your SSL certificate to be provisioned. This may take up to 24 hours after you point your A records to Firebase Hosting. In nearly cases, propagation of your records and provisioning of your SSL cerificate will happen within a few hours, depending on your domain provider.

Advanced Setup

1. The Connect Domain window of the Firebase console volition request that you lot provide a token to migrate your existing site. Yous but demand to complete 1 of the following to provide the token:
• Update DNS TXT records: Visit your domain provider'due south DNS management site. Add a TXT record with your domain key and the provided value.
Allow upward to 24 hours for propagation of your TXT records.
• Upload a file to an existing site: Upload the token onto your existing site at the specified URL and verify its existence.
This page must be served over HTTPS and doesn't have to be valid or secure. The encrypted token is but valid for one try. If migration fails, a new token will be generated for your records.
2. Allow time for your SSL document to exist provisioned. This may have up to 24 hours. In about cases, propagation of your records and provisioning of your SSL certificate will happen within a few hours, depending on your domain provider.
3. Later your SSL certificate is provisioned, return to your DNS provider's DNS direction site to add DNS A records pointing your page to Firebase Hosting. Add and relieve records with the following inputs:
• Blazon: Add ii DNS A records.
• Host: Enter your custom domain key for both records.

The host you bespeak is the domain on which you want to serve content; this domain tin be an noon domain or subdomain.

Your domain provider may listing this term as "Host proper name", "Name", or "Domain".

• Value: Assign one value to each DNS A record to bespeak your domain to the specified IP addresses.
Your domain provider may listing this term as "Data", "Points To", "Content", "Address", or "IP Address".

Wait for SSL document provisioning

Subsequently we verify domain ownership, we provision an SSL certificate for your domain and deploy it across our global CDN within 24 hours afterwards you point your DNS A records to Firebase Hosting.

Your domain will exist listed equally one of the Subject Alternative Names (SAN) in the FirebaseApp SSL certificate. You lot can view this document using the browser'south security tools. While the domain is provisioning, you might see an invalid certificate that does non include your domain name. This is a normal part of the process and volition resolve subsequently your domain'due south certificate is available.

For Advanced Setup users, your website will exist hosted by your previous hosting provider until the setup condition in your project'due south Firebase Hosting page updates to Continued.

Your custom domain cardinal

When adding or editing DNS records, different domain providers expect you to enter dissimilar inputs for the Host field inside their DNS management sites. We've compiled common inputs from popular providers below. Refer to your domain provider's documentation for detailed instructions.

Domain type	Custom domain key
Apex domain	Common inputs include: @ The noon domain name (for example, example.com) Leaving the Host field blank
Subdomain	Mutual inputs include: The full subdomain proper name (for example, app.example.com) Only the subdomain portion (for instance, app merely, and leaving out .example.com) Only www for the subdomain of www.example.com

Mutual domain providers

Here are some common domain providers and the types of input each might require. This data is kept upwardly-to-date every bit much as possible, but refer to your domain provider's documentation for detailed instructions.

Cloudflare

Blazon	Host	Value
DNS TXT record inputs
TXT	example.com	verification value provided in Firebase console
DNS A records inputs
A	example.com	199.36.158.100
A	www	199.36.158.100

Google Domains

Type	Host	Value
DNS TXT tape inputs
TXT	@	verification value provided in Firebase panel
DNS A records inputs
A	@	199.36.158.100
A	www	199.36.158.100

Google Cloud DNS

Type	Host	Value
DNS TXT record inputs
TXT	example.com	verification value provided in Firebase panel
DNS A records inputs
A	example.com	199.36.158.100
A	www	199.36.158.100

NameCheap

Type	Host	Value
DNS TXT tape inputs
TXT	@	verification value provided in Firebase console
DNS A records inputs
A	@	199.36.158.100
A	@	199.36.158.100

Squarespace

Type	Host	Value
DNS TXT record inputs
TXT	@	verification value provided in Firebase panel
DNS A records inputs
A	@	199.36.158.100
A	www	199.36.158.100

Setup status descriptions for custom domains

Status	Description
Needs setup	You may need to change a configuration with your DNS records. In about cases, your DNS A records oasis't propagated from your domain name provider to Firebase Hosting servers. Troubleshooting tip: If it'due south been more than 24 hours, check that you've pointed your records to Firebase Hosting. In rarer cases, specially if you're using the Advanced Setup menstruum, SSL challenges might be failing because: Your DNS records have A records or CNAME records that point to other hosting providers. Troubleshooting tip: Check that your A records bespeak merely to Firebase Hosting, and remove all CNAME records. Migration failed, and the token (DNS TXT records or uploaded file provided to your site) is now invalid. Troubleshooting tip: Click View for the domain, then provide the new token to your existing domain.
Pending	You correctly gear up your custom domain, just Firebase Hosting hasn't provisioned an SSL certificate. Occasionally, the post-obit issues can stall the minting of an SSL certificate for a custom domain: Your CAA records are likewise restrictive. Troubleshooting tip: Ensure that the certificate authorities `letsencrypt.org` and `pki.goog` are allowed to create SSL certs for your domain. Your challenge lawmaking is invalid. If you're using the Advanced Setup menstruum and migration failed, your token (and its claiming code) are now invalid. Troubleshooting tip: Click View for the domain, and so provide the new token to your existing domain. You requested certs for also many subdomains. Troubleshooting tip: Mostly, Firebase Hosting recommends no more than 20 subdomains on 1 apex custom domain, due to SSL document minting limits.
Connected	Your custom domain has the proper DNS records and has an SSL certificate. You can serve your site's content.
Needs Re-Verification	Firebase may require yous to manually re-verify your domain ownership if any of the following situations happen: The TXT record added when yous initially verified your domain ownership was contradistinct or removed from your domain's DNS settings. Notation that multiple TXT records with a google-site-verification token are allowed on a single domain. We crave that the TXT record is continually present in your DNS settings as this proves you own the domain and authorize us to assign and renew SSL certificates for your site. The person who verified domain ownership is no longer assigned an IAM role that contains the required permission to verify domain ownership. These roles include Owner, Editor, Firebase Admin, and Firebase Develop Admin. Troubleshooting tip: Visit your project's Hosting folio to complete the re-verification process within the specified time window (usually 30 days) to avoid your custom domain from being automatically asunder from Firebase Hosting.

brownalid1997.blogspot.com

Source: https://firebase.google.com/docs/hosting/custom-domain

Share this post