I have installed Godaddy Certificate with steps below
https://in.godaddy.com/help/manually-install-an-ssl-certificate-on-my-iis-8-server-4951
After adding in Binding on port 443, the website opens with https on the server machine.
When tried to access from outside machine, it shows this site cannot be reached.
It is still working with http everywhere.
Note - basic things are all done like restarting server.
Related
I am using ngrok to make my local instance of Apache (running through XAMPP on Windows 10) viewable to the internet. It works fine to access http://example.com but if I try https://example.com it gives me a certificate error (because the certificate is issued for its ngrok.io domain). I know I can avoid the cert error by using a url that ngrok generates for https, but I'd rather use my own domain name. How can I avoid the certificate error and get my site to load over https? I've seen a few guides for enabling https/ssl on localhost, but that's not what I need to do - I need to enable it for example.com, not localhost, and as I said, serving the site over http is working fine.
I'm trying to set up a different website on IIS but it keeps wanting to use an SSL certifcate that is configured for a different website within the same IIS.
e.g. https://localhost:443 has a security certificate but i want to create http://localhost:98/
Steps I've done:
Created a new application pool
Created the website within IIS
Edited bindings to point to a specific IP address and port: e.g: http://123.456.789.10:98/
Edited binding for localhost to use a different port: 98 e.g: localhost:98/
What's happening is that now whenever I go to localhost:98 or the ip address, it keeps redirecting the site back to the website that has the SSL certificate for it
eg. I click localhost:98/ but it redirects to https://localhost/
What can possibly be incorrect with this setup? I had it working before but then when i tried to apply a different SSL certificate, it didn't work, i re-set up everything and it's constantly pointing to this situation.
I am currently trying to install a self-signed SSL certificate on a wamp server (running apache 2.4.2).
I have almost word for word followed this answer to do so.
When trying to connect via https:// on chrome it nearly always fails, returning ERR_CONNECTION_CLOSED or ERR_CONNECTION_ABORTED but if you keep refreshing, it will sometimes connect as expected (though only 1 in 20 at best...)
I'm not particularly experienced with any of this, but if anyone can point me in the direction of something I may be doing wrong then that would be much appreciated!
If your server is up and you are able to browse the website with http:// then you need to check if the port 443 is open or not. Also, if you have proxy, firewall and load balancer then you need to check that port 443 is open on the same
Using this guide I managed to access my server from remote hosts. However, now I want to enable SSL on my server and I know that there is an option in the configuration to enable SSL but the https URL added is on localhost. How do I do the same as in the tutorial but with SSL, just add another binding but with port 443? or is there something more to it.
Thanks.
I have successfully added SSL certificate to my url. now url is "https://puinex5xgm-l1". Its working fine on browser. but whenever I try to add port to this ulr "https://puinex5xgm-l1:90/" its giving me "SSL connection error ERR_SSL_PROTOCOL_ERROR". My apache server is running on port 90.
While creating certificate I have used domain name as "puinex5xgm-l1".
Please help.
ERR_SSL_PROTOCOL_ERROR is not related to the certificate. My guess is that you don't have https on port 90 enabled but instead plain http, which then will cause such an error.
I have found the solution.
I have made changes in "httpd-ssl.conf" file. Here, I have used "VirtualHost default:90" instead of "VirtualHost default:443".
Now Apache server listening my port.
Its working fine now.