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.
Related
I have hosted website with a different port like http://example.com:8888
Its working fine but when I try to access with HTTPS(https://example.com:8888) it's giving me ERR_SSL_PROTOCOL_ERROR (This site can’t provide a secure connection)
I am using XAMPP and I have also configured an SSL certificate.
Please help me to configure with HTTPS.
You need to enable ssl in the VH listening on the new port
SSLEngine On
and you have to provide all the proper configurations required such as the keyfile, and the certificate file.
Official doc: https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html
I have two iis websites. One I have a localhost on port 80 and was setup for dydns with ssl port forwarding external: 443 and internal port:1124 and the website is working perfectly with dydns access.
I wanted to setup another website with the ssl port but was unable to do so. As when I set the port forwarding external Ssl:443 and the internal ssl port:1129. the other dydns entry redirects to the first website. This website does not work without https.
So. How do I setup two websites for ssl port forwarding on the same machine?
Any help is appreciated.
You don't necessary need an entirely different port for each website you host on the same machine. You can use the same http/80 and https/443 to serve multiple website through virtual hosts.
I'm not familiar with IIS, but I do know that it's possible on IIS just like Apache and NGINX does. You can read about setting up virtual hosts on IIS here. Also I answered a similar question here.
In the past, my web application hosted in Weblogic 12c and OHS 12c, the url is http://serverName/webName
SSL is pretty new to me, now I managed to turn on
1. SSL in Weblogic, web application can access through https://serverName:7002/webName
2. SSL in OHS virtual host on port 4443, vertified using https://serverName:4443
Now I am having challenge making my web application accessible through https://serverName:4443/webName or https://serverName/webName. Need guidance on how to edit OHS configuration (ssl.conf, mod_wl_ohs.conf, httpd.conf, etc) to achieve above.
You also need to enrich your mod_wl_ohs.conf with the following 2 directives :
SecureProxy ON
WLSSLWallet "/path/to/wallet/directory/as/defined/in/your/ssl/conf/file"
You may find more details on these directives here :
https://docs.oracle.com/cd/E28280_01/web.1111/e10144/directives.htm#CIHFAAJB
But if you would like for the "https://serverName/webName" to work, since the default port for SSL is 443, you need to change OHS listening port from 4443 to 443 inside ssl.conf
I have a windows 2012 server and have applied an SSL certificate following godaddy's guide:
https://uk.godaddy.com/help/iis-7-install-a-certificate-4801
I have applied the binding on the site in IIS however when I try to view the https site I get "refused to connect".
I have updated the firewall setting to allow port 443.
Any ideas?
It was due to my site using a load balancer.
An additional load balancer for port 443 was required.
Anyone using rackspace will find this useful:
To allow secure traffic you would need an additional load balancer
allowing traffic on port 443, with a shared VIP with the current one.
https://support.rackspace.com/how-to/configure-a-load-balancer/
There is a SharePoint web application on my server that is already https and listening on port 443 (which I don't own/administer). Currently, my SharePoint web application is http and on port 88. How do I SSL enable it on a different port other than 443? I think that if I create another SSL binding on 443, the other site or mine or both will become unusable, is that correct? What is the best approach for more than 1 SSL enabled SharePoint site on a web server? Can I do this via host headers, or dedicated IP Addresses and if yes then how?
Check out this blog. Either use different IP's or a wildcard certificate.
But if you are using SharePoint 2013 on Windows Server 2012, then there is a new thing called SNI (New to IIS anyway) that allows you to use the hostname at the beginning of the handshake to identify the certificate to use.
To enable this all you have to do is go into IIS -> edit bindings, and check "Require Server Name Indication". This will switch the cert binding from IP:Port to Hostname:port, allowing for multiple web applications to use ssl with the same ip and port.
See:
http://en.wikipedia.org/wiki/Server_Name_Indication
And
http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-server-name-indication-sni-ssl-scalability
Also, you can ssl enable it on a port other than 443 by:
Editing the bindings in IIS
Then edit the AAM in Central Admin
You probably shouldn't do this though because your users will have to type the port after the websites name since it isn't using the 443 default.