32
votes

I am able to complete the connect to custom domain step successfully and https://example.com is correctly loading my static file app which is hosted on Firebase.

However, browser is warning about the site's SSL certificate is not matching example.com. I looked at the certificate and it is of firebase.com, not mydomain.com.

This certificate is provided by Firebase for example.com (my custom domain name) and I expect it to be matching it. Is this expected?

I know the other solution is to get my own certificate for example.com. However, it seems that Firebase won't let me deploy my own cert.

Update

I retried it some time back and it is fixed. And the whole suite of firebase db/functions and corresponding sdk/cli are working really well. Great for small dev team.

3
hello @webp did you manage to find a solution for this? - drv
@drdrdrdr not yet unfortunately. However, I now host my app on google app engine and get my own ssl cert with letsencrypt.org. For instructions on using letsentrypt with app engine, this is helpful - webp
@webp were you ever able to get it working with firebase? - r3wt
@webp i did. i sent support a message and they fixed it without even responding to me. - r3wt
@r3wt Good to know it's something they can fix. Thanks for circling back. I may need this in the future. - webp

3 Answers

42
votes

Solution: Don't have to do anything about it other than just wait.

Faced the same problem when connecting to my custom domain on Firebase Hosting. However, it will only be insecure when the status is pending. The status can be found on your Firebase Hosting Dashboard.

My connection turned secured with a green lock after around 3 hours, and the status reflected in the dashboard changed to connected.

0
votes

This error message called domain name mismatch warning that occurs because of the domain is pointed to a shared IP addresses.

You need to confirm that your hosting provider supports SNI technology which allows install different certificates on the same IP. Please ensure that the certificate is installed correctly on your desired server and enable SNI. If your hosting provider doesn’t support SNI technology, you should have to dedicated IP to host your SSL.

0
votes

In the add custom domain menu, check by changing the setup mode to advanced and complete the provide token on existing domain task by copying the TXT value to your dns records according to the instruction.

This solved my problem.