I purchased a domain from domain.com, followed the steps of firebase custom domain connect up to second point (Verify ownership). I added the TXT record as described.
Verified with dig -t txt +noall +answer my-domain.com and the response holds 2 records:
my-domain.com. 3455 IN TXT "v=spf1 ip4:66.96.128.0/18 ?all"
and
my-domain.com. 3455 IN TXT "google-site-verification=verification code"
The Firebase console keeps alerting
We couldn't verify your domain my-domain.com. Please check your settings and try again.
What could be the possible error & what can I try next?
Related
I am trying to access a subdomain belonging to a separate ngrok account.
How do I logout and login to a different ngrok account from the command line on a macbook?
Got it. You need to access your ngrok authToken and paste the following in the terminal:
ngrok authtoken AUTH_TOKEN_VALUE
In my case, I needed to stop using the account entirely and move to the trial provision.
I did this by locating the .ngrok.yml file where the authtoken is being stored and commented this line out.
The file was located in the default location for this is: ~/.ngrok2/ngrok.yml unless you specified a different location when registering the account on your machine.
I have an AppEngine app that uses Firebase auth to manage users.
I recently added a custom domain to the AppEngine app, and that worked fine.
Now I'm trying to manage the Password Reset template and change the sender email to match my domain. But when I follow the instructions to add the 2 TXT records and 2 CNAME records, the verification never completes. It's been in this state for almost 2 days. What am I doing wrong?
Instructions are:
Edit the DNS settings Firebase provided to match these patterns:
CNAME 1
HOST: firebase1._domainkey
VALUE: mail-YOURDOMAIN-com.dkim1._domainkey.firebasemail.com.
CNAME 2
HOST: firebase2._domainkey
VALUE: mail-YOURDOMAIN-com.dkim2._domainkey.firebasemail.com.
TXT 1
HOST: #
VALUE: v=spf1 include:_spf.firebasemail.com ~all
TXT 2
HOST: #
VALUE: firebase=YOURDOMAIN
I have purchased a domain from Godaddy let's say myCustomDomainName.com
I have created a project and deployed a web page in FireBase - https://home-myCustomDomainName.firebaseapp.com/
I have linked a custom domain in the project console
In GoDaddy the A records and TXT Records are also updated.
The site was up for a while. I could access my website using https://myCustomDomainName.com as well as https://www.myCustomDomainName.com
But now I keep getting Site can't be reached error. [I am however able to reach the site through firebase URL https://home-myCustomDomainName.firebaseapp.com/]
[]3
Even ping requests fail.
Please advice on what could be wrong and how to avoid this error.
Take out the www and the .com and use # or your sub host
e.g.
example.com:
Type: A, Value:#, IP: x.y.z.a
subdomain.example.com
Type: A, Name:subdomain, IP: x.y.z.a
I'm having trouble verifying namecheap domain with firebase hosting
Tried to follow this posts instructions without success:
Unable to Verify Custom Domain with Firebase Using Namecheap
and this
Adding custom hosting domain: "Unexpected TXT records found. Continuing to watch for changes."
So my definitions are like this:
Type: TXT Record
Host: #
Value: globalsign-domain-verification=...
TTL: Automatic
Type: TXT Record
Host: #
Value: firebase=mydomain.info
TTL: Automatic
Type: CNAME Record
Host: www
Value: myprojectname.firebaseapp.com.
TTL: Automatic
Type: A Record
Host: #
Value: First IP Address retrieved with MXToolbox
TTL: Automatic
Type: A Record
Host: #
Value: Second IP Address retrieved with MXToolbox
TTL: Automatic
When I execute "dig -t txt +noall +answer mydomain.info", it returns:
mydomain.info. 1798 IN TXT "globalsign-domain-verification=..."
mydomain.info. 1798 IN TXT "firebase=myprojectname"
(It has the extra dot at the end of the domain)
But still in firebase dashboard I have this message:
Verifying ownership
Unexpected TXT records found. Continuing to watch for changes.
and later:
Verification failed
Couldn't find the correct TXT records in your DNS records
I'm trying to solve this problem for several days now.
After not having my domain verify for over 24 hours and trying numerous things, I eventually deleted the CNAME record of [projectname].firebaseapp.com. A few minutes later, it verified with no problem.
These are the steps that they want you to do:
Only have the TXT Record for the verification.
After verification, add two A Records.
This is what I did:
Add TXT record and two A records.
Get verified
Hope this helps. I submitted a ticket to firebase to propose that they modify the instructions to make it clear that you can't put the CNAME to your project URL.
Strongly recommend that you contact Firebase support. I had a similar issue going on for days and only after they manually intervened behind the scenes it was resolved. Good luck...
I was facing the same problem. instead of domain, I used # in host and it worked. I am on a Free plan.
Always ensure that you are using a paid version of Firebase. Domains do not get verified if you are using a free account. I had to downgrade one of my old projects in order to verify my new project. Apparently, firebase allows only a certain number of projects to be upgraded to a blaze plan. I hope this helps.
I have recently moved a project over to another server. The domain name is the same, it has just been pointed to the new server. The URL is exactly the same. Since moving the project over however I get this error when the app tries to connect to googles OAuth api.
{
"name": "Error calling GET https:\/\/www.googleapis.com\/analytics\/v3\/management\/accounts\/~all\/webproperties\/~all\/profiles?key=AIzaSyBKUP8JriiOnFnbJm_QYt_bHTMuHf-ilAI: (403) There is a per-IP or per-Referer restriction configured on your API key and the request does not match these restrictions. Please use the Google Developers Console to update your API key configuration if request from this IP or referer should be allowed.",
"url": "\/analytics\/statistics.json"
}
The obvious reason (based on the error message) would be that I haven't added the new server IP into the list of allowed IP's in the devlopers console under APIs & auth->Credentials->Key for server applications.
I have added the IP. I've checked the domain has propagated by pinging it and the new IP comes up which has been entered in the console so i'm struggling to work out why it doesn't work.
Has anybody come across this before that may be able to help me solve it?
Go to Project -> APIs & Auth -> Credentials -> API Key -> Create New Key -> Browser Key. It may take upto 5 minutes to reflect changes.
And it worked for me.
After you added your new server IP you need to generate a new API key from the Console. This message shows up when access in not properly configured. Look here and scroll down to "accessNotConfigured".
So, go to your developer console, Project -> APIs & Auth -> Credentials -> Public API Access -> Create New Key -> Server Key. Use this new key and you should be good to go.
I've had this problem for a while as well but finally solved it:
I noticed when trying wget http://bot.whatismyipaddress.com/ from my server it would actually return an IPv6-address, when on the API key's config page I had entered the IPv4-Address of my server. Once I added the IPv6-Address, my requests where finally accepted.
Go to Project -> APIs & Auth -> Credentials -> Public API Access -> Create New Key -> Server Key >> Accept requests from these server IP addresses (Optional) section,
then remove all the IP Address and Update it first, then try it. And, later you can add the specific IP address which did weirdly work for me.