Firebase hosting issue external ssl certificate, domain delivered by namecheap - ssl

I have an application in firebase hosted using a domain name from neamcheap but it's not working!
How to activate the ssl certificate with external domain name that i had bayed from you ( Domain name and Ssl certificate namecheap) in order to use it for firebase hosting ?

Related

Provide SSL certificate for internal Website

I have a website in my local network and the website is not ssl secured.
Many clients can not reach the website because of
"ERR_SSL_VERSION_OR_CIPHER_MISMATCH"
Is there any way to secure websites in a local network with ssl? I am using an Active Directory Server in my network.
There are also a lot of local Websites on a vmware that are not secured. I would like to secure them easily.
• I would suggest you to please install ADCS (Active Directory Certificate Services) role in your Active Directory and create a self-signed SSL certificate through it for your internal use. Since, Active Directory is a trusted public key authentication infrastructure provider, the concerned role installed on it for the said purpose does not need certificates from globally trusted CA (certification authority) and can be thus, used locally. For the time being, if you want to create a self-signed SSL certificate on the concerned server, you will have to install ‘Web Server (IIS)’ role and then open the ‘IIS manager’ console from where you can generate the SSL self-signed certificate and bind the same to the website on that server itself. For this process, kindly refer to the link below which explains in detail the steps to be followed for generating a self-signed certificate and binding it to a website: -
https://www.thewindowsclub.com/create-self-signed-ssl-certificates-in-windows-10
Please note that the above stated process is for that server on which the website is hosted locally. Thus, the self-signed certificate generated will not be useful on other servers in your environment.
• To generate an SSL certificate for a web service/website that is hosted on a cluster of servers configured for the same purpose/website, then you will have to configure an SSL certificate template from a root CA, in your case, an AD server installed with ADCS role will serve as a root CA in your domain environment. Then assign that template to the CA (AD server in your case) for it to authorize the issuing of the configured SSL template to the concerned server where the website for which this SSL certificate is to be installed is hosted. For more detailed information regarding this, please refer to the documentation link below: -
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn781428(v=ws.11)#obtain-an-ssl-certificate-from-ad-cs
Please note that the above link states the issuing of the SSL certificate for an ADFS Server. You will need to change the Subject Name of the issued certificate to that website for which you are issuing this certificate.

SSL CSR for server farm on IIS

I have 2 IIS web servers with my website hosted. I have a 3rd server with IIS for ARR. I have created a server farm with name ABC.com on 3rd server and added the 2 IIS web servers to the farm. Disabled SSL offloading for security purpose.
My website name is https ://www.ABC.com. I have mapped my website name to IP address of 3rd ARR server.
Correct me if I am doing wrong.
I want the request flow to have https throughout the request.
Now in which server should I create CSR request for SSL certificate, and where all should I install the SSL certificate.
Only 1 SSL is required or multiple SSL certificates are needed?
Should I use ABC.com farm name while creating CSR?
After research I found that SSL has to be created on IIS Webserver seperately and IIS ARR server separately. And they have to be installed on the respective servers where created.

SSL certificate issue GoDaddy domain , Heroku Server hosting , Cloudflare SSL

I have bought my domain name www.thoughtgrub.com from goDaddy.
However I am hosting it on Heroku.
I needed an SSL certificate so I set that up using cloudflare.
When I check whether SSL is installed using https://www.digicert.com/help/
It says certificate installed correctly.
However web browser shows www.thoughtgrub.com as unsecure.
also https://thoughtgrub.com --> throws Site cannot be reached error or
shortener.secureserver.net/error_404
What's going wrong?
IS there any other method to achieve https certification?
you need to go to heroku settings and click on add SSl certificate.

Heroku SSL Endpoint for Wildcard certificate - adding staging env

I have a production application that is using a wildcard SSL certificate via Heroku's SSL endpoint - bar.com. The staging app doesn't have an SSL endpoint set up. Instead, I added it as a subdomain to bar.com as foo.bar.com. I am getting Your connection is not private error when I try to access my staging app via https. Should a separate SSL Endpoint get set up for the staging app? If so, how would I add it to my existing wildcard SSL?
The wildcard certificate for *.bar.com. Will automatically secures unlimited number of 1st Level sub-domains under bar.com. The wildcard certificate already secures foo.bar.com in the certificate for *.bar.com. All you need to do it to simply install the wildcard certificate for *.bar.com on the server where foo.bar.com is hosted.

Heroku SSL Endpoint with purchased certificate does not seem to work

I have purchased an SSL certificate and installed it to my Heroku app.
However when I try to access my site via https, Chrome reports that:
The identity of this website has not been verified. • Server's
certificate does not match the URL.
Other browsers report a similar message.
Inspecting the certificate information in Chrome shows that my site is still using Heroku's certificate, issued by Digicert (instead of my own CA).
Any ideas as to what I could be missing?
The problem had to do with an incorrectly set DNS record.
As per the documentation (...), once the certificates are uploaded to Heroku, do:
heroku certs
This provides you the correct end point for the SSL enabled domain. This is a domain that looks like "tokyo-2121.herokussl.com".
Next, go to your DNS service provider and update/add the CNAMe record for the SSL enabled domain to point to "tokyo-2121.herokussl.com".