Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Unable to Verify Custom Domain with Firebase Using Namecheap

Tags:

firebase

After I followed the instruction by inserting the Text Record 1 that firebase has provided into my NameCheap, this error message keeps popping up:

Current Status: Sorry, we were unable to verify your domain.

This message has been shown up for about 5 days now.

I've captured screenshots of firebase and namecheap setting as below:

enter image description here

enter image description here

After @Frank van Puffelen suggested to change the host value from my domain name to @, this is the screenshot, and we'll wait and see after a few hours, hopefully it can verify successfully.

enter image description here

After waiting for a few hours this message appears:

enter image description here

like image 782
Vicheanak Avatar asked Nov 29 '15 05:11

Vicheanak


2 Answers

From other reports and the information on this Google page for verifying namecheap domains, it looks like you may have to use @ for the host field.

In the Namecheap site, click Manage next to the domain you want to verify with your Google service.

  1. Click the Advanced DNS tab on the domain dashboard.

  2. Scroll down and click Add New Record under the host records table.

  3. Select TXT Record from the record type drop-down list.

  4. Paste the entire verification record into the Value field.

  5. Enter @ in the Host field.

  6. Leave the TTL field set to Automatic.

  7. Click the green check mark to save your TXT record.

Note: The change may take up to 24 hours to update. However, as you go through the next steps in the Setup Wizard, the wizard immediately starts checking for your new TXT record to verify your domain.

Can you try that? If it doesn't work, let me know and also reach out to [email protected].

like image 142
Frank van Puffelen Avatar answered Oct 16 '22 20:10

Frank van Puffelen


Your attached screens do not show your CNAME configuration. Even though firebase instructions indeed only asks for two TXT records, records that are both correctly set up as your screens show, I believe that these pair of TXT records that firebase requests do not free you up from the need of setting up at least a CNAME record in addition to both TXT records.

This was my case: while I did not set a CNAME record, firebase never recognized my domain.

I am not an expert (sorry!), but in the lack of other answers, even I may be helpful to suggest that you set up your CNAME record to point to:

CNAME record
host: www
value: [yourfirebaseappname].firebaseapp.com.
(Please note the dot after the '.com').

In my case this was enough to make firebase works well and recognize my domain.

In my specific case, and I'll register here at least for my own future use, I prefered to use, as an after step, both A records supplied from firebase as my way to route to my domain without www.

I believe this can be done with CNAME, but in my case the final setup was:

Advanced DNS Management
type: CNAME record
host: www
value: [my-domain-name-without-www]

type: A record
host: @
value: [IP address from firebase, like '1.2.3.4']

type: A record
host: @
value: [Second IP address from firebase, like '2.3.4.5']

Everything is working fine using this configuration. Goal reached.

As a todo future step, It would be useful to learn how to achieve similar goal using the CNAME record pointing to firebase domain instead of A records pointing to firebase supplied IP addresses.

Hope this helps other users in similar situation!

like image 44
Vladimir Brasil Avatar answered Oct 16 '22 19:10

Vladimir Brasil