I'm having hard time in understanding how the SSL part of this firebase works
as there is no option to change
and its causing many issues if we use other SSL apart from firebase
is there any way where we can disable firebase ssl
and use custom one
or can some one tell me how to reset this ssl issued by firebase (which is different domain and its just partial not full/strict https)
The SSL certificates Firebase Hosting uses come from letsentrypt.org. They are full SSL certificates, but they are shared between many domains. From the Firebase documentation on its SSL certificate provisioning:
Your domain will be listed as one of the Subject Alternative Names (SAN) in the FirebaseApp SSL certificate. You can view this certificate using the browser's security tools. While the domain is provisioning, you might see an invalid certificate that does not include your domain name. This is a normal part of the process and will resolve after your domain's certificate is available.
If your project is on the paid Blaze plan, you can reach out to Firebase support to set up a SSL certificate you provide on Firebase Hosting for it.
Related
I have two sites hosted on firebase. Browsers accessing either site are reporting "This site can't provide a secure connection".
The ssl certificates my sites are issued to gautiervanrossom.com and besworth.io respectively. I don't know anything about these entities.
How can I reset my firebase ssl to the correct url?
Do Firebase’s free SSL certificates on your custom domain expire? If so, how do I renew it?
Firebase Hosting certificates (like all SSL certificates) may expire, but will in that case be auto-renewed.
If there is a problem on your domain due to certificate expiration, reach out to Firebase support for personalized help in troubleshooting. There is nothing more you can do about it.
Try to read the Official Google Documentation regarding Firebase
https://firebase.google.com/docs/hosting/custom-domain
Also, check this stackOverflow ticket, it also discussed about expiration
Firebase hosting : SSL Certificate has expired and haven't been renewed
I deleted a firebase project. I had linked to a custom domain, and now I cannot access the custom domain. It gives me an error, NET::ERR_CERT_COMMON_NAME_INVALID
The domain is http://apps.diggle.tech/ and it gets redirected to https when I visit the URL.
Your site is no longer associated with Firebase Hosting, however Firebase Hosting does add HSTS headers to sites to ensure they're always served over HTTPS. These are cached in the browser for a period of time, and so since you had previously visited the Firebase Hosting version of your site it is still enforcing HTTPS.
Since your new hosting setup doesn't support HTTPS, you're seeing an SSL error. You will need to either add SSL to your new hosting configuration or just wait for the HSTS cache to expire.
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 example.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.
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.
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.
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.
I am building an eCommerce platform and I would like to give my user's the ability to point their domain (e.g. bobsburgers.com) to an HTTPS-protected subdomain on my site (e.g. bobsburgers.shoplolz.com). Getting a wildcard certificate for the dynamic subdomain is simple, but how does one allow their users to use their own domain while requiring HTTP? I'm currently hosted on Heroku but I'm curious at a higher level how this can work, if at all.
Based on my research the only way to do this is to have the site owner upload an SSL certificate and use an HTTPS-enabled reverse proxy which can be configured dynamically to accept new SSL certificates for newly added domains.