i bought an SSL certificate and followed a guide to import the SSL to my IIS 7, then, i stablished the bindings
https All unassigned 443
Hostname ( Cant write any text here)
SSL: customerwebsite.com (Not the real URL)
Restarted the website and tried to access via https to the site but a "Connection is not secure" advert is shown on the browser. I tried to see more information about the cert and it shows information of another SSL, it shows that the SSL was issued to TP-LINK, it doesnt show the information of the SSL that i have installed.
Do you know please what can i do in this case? This is so important. I need to install that SSL.
Thanks for all the help.
I Installed the SSL and then configured the bindings.
Related
We have developed an angular website and we have both personal server and a registered domain extension. We were able to host through public ip using iis but when the domain name was used in throws NET::ERR_CERT_AUTHORITY_INVALID. It also redirects to https by default.
We also tried using xampp too. We don't want to use any cloud servers as our custom domain extension can't be used.
kindly help us to host the website.
As you mentioned the error message: ERR_CERT_AUTHORITY_INVALID.
This issue is related to your certificate. If you do not currently have a certificate, you can choose to create a self-signed certificate, or apply for a certificate from the Authority.
If you already have a certificate and still have this issue, you can check to see if it is expired and try renewing the certificate.
I have recently bought a web server where I issued SSL certificate and I also bought my domain. I also have VPS server where my API will be located and accessed from the web server. Now the question is this -- is there any way I can use my automatically generated SSL certicate for my VPS server as well?
I added domain like xxx.yyyy.sk and forwarded it to my VPS IP address. When I tried SSL https:// I just received an error ERR_SSL_PROTOCOL_ERROR. (this happened while I used my automatically generated certificate)
I also tried issuing certificate on my own in my VPS server using OpenSSL but it seems like I have overwritten my automatically generated certificate because now the certificate is valid but browser says it's not secure..
Is there any way to prevent this 'not secure' status? It's quite annyoing and I want to get rid of it since I am building an e-shop and it would not be appropriate for users to see 'not secure' once they fill in sensitive data.
Thank you for any sensible answers!
You can use the following command to generate a certificate with letsencrypt.
sudo certbot certonly --standalone -d xxx.yyyy.sk
I choose to host my website in Azure.So I've created a App Service.Then Created a new domain for my App then created/bind the SSL certificate to my corresponding website.
After done with the SSL certificate .I'm still seeing my website url as http//: and not https://
Also i'm not seeing the Green URL for my Website ..!
It look like this
(P.s : My App Service Tier is AzureFreeTier (Basic: 1 Small)
My SSL Type is SNL SSL)
Please help to resolve my problem here
Thanks in Advance,
Jayendran
You need to do a redirect from HTTP to HTTPS. Installing a certificate just makes using HTTPS with your custom domain name possible.
You can either:
Configure your app to redirect to HTTPS when it receives a request over HTTP + enable HTTP Strict Transport Security
Or use an extension in Web Apps to do the first thing:
To install the extension, open your web app blade in Azure Portal. Go to Extensions, then click Add. Then you should find Redirect HTTP to HTTPS from the list and install it.
That will redirect any HTTP calls to HTTPS for you. I would still recommend adding Strict-Transport-Security headers to your responses to make sure your clients do not access your site insecurely the next time.
The reason you arrive to your site on HTTPS after AAD login is because the HTTPS version of your app's URL has been configured in AAD as the reply URL.
And this:
Your Connection to this site is not fully secure Attackers might be able to see the images
is a mixed content warning. It means you are loading content (e.g. images) using an HTTP URL in your pages. Change them to HTTPS and you will solve that problem.
I am attempting to add ssl to my custom domain for the windows azure websites. I have configured everything properly according to the guides, but for an unknown reason when I attempt to access my website via HTTPS, it returns with a connection denied error. the redirect still works perfectly fine with a standard HTTP request.
for reference (https://www.cryptoalias.io)
short version of method (in case I missed something):
bought a SSL cert from comodo.com
generated a .pfx from the .cer they issued to me (using iis)
uploaded .pfx to azure
verified cname: created custom domain redirect to azure
bound ssl to custom domain
configured A name redirect to the VIP azure issued me. remove cname redirect
attempt to connect to https = nothing, http works.
sorry I realize this is rather short on information, but I'm not sure what more I could provide besides the actual SSL cert.
You need to configure your cert on 2 domains: cryptoalias.io and www.cryptoalias.io. Because if you go to https://cryptoalias.io/ your cert works fine.
I have a website that is being configured with SSL, and I am using a self-signed certificate for testing purposes, for now. The machine is running Windows 2008 R2 with IIs 7.5 and Apache Tomcat 5.5.
The problem is FireFox is gives the error that the connection is untrusted because it's a self-signed certificate and it also says that the site is using an invalid security certificate. I tried importing the certificate into Firefox, to remedy the situation, and it did not help. However, with IE, exporting the certificate from IIS and importing it into the browser's Trusted Root Certificate Authorities store permitted IE to trust the self-signed certificate.
It's important to note that the server's fully qualified domain name is webdev.dev.mysite.com, whereas the website address is webdev.mysite.com and I've had no problems with the site under HTTP. And with the help of the site here, I setup the self-signed certificate such that it's name is webdev.mysite.com.
How can I get Firefox to trust the self-signed certificate?
Thank you very much for any help.
I believe this page should help you:
In FireFox, go to Tools -> Options
Click the Advanced Tab, then the View Certificates button
Go to the Servers tab and press the Add Exception button
Note: It might depend on your version of Firefox
Source: www.poweradmin.com/help/sslhints/FireFox.aspx