I have just installed virtualmin on a fresh Centos 6 installation. I am setting up the SSL part for my website. I installed the certificate and it looks ok, I think. I got one of those cheap PositiveSSL certificate for around $5 a year. Anyway, when I try to access my website using https, Chrome is saying Error 102, connection refused. I scoured the web for answers and searched the forum for previous posts but didn’t find anything useful. Anyway, I am hoping one of you “gurus” might be able to give me some ideas.
I hadn’t heard of anyone running into that before… I did some Googling, and saw that some people run into that when Chrome is configured to use a proxy server.
You can use the steps here to determine if your OS is configured to use a proxy server:
Hi Eric, I am not using a proxy server to access the internet. If it was a proxy server issue, then I shouldn’t be able to access virtualmin admin interface as well, which is secured by a self signed certificate.
The website also gives me an error irrespective of which browser I use, Firefox, Internet Explorer, etc.
I think that looks right. I am more of a web developer, not much of a server admin, that’s why I thought virtualmin might make it easy for me to setup websites.
Yeah, in case of some “cheap-ass” SSL authorities, you need to provide a “chained/intermediate certificate”, if yours don’t depend directly on a root CA. Check out “Server Configuration / Manage SSL Certificate”, tab “CA Certificate” and upload the intermediate cert of your SSL provider there.
“If your virtual server’s SSL certificate is from a certificate authority that is not directly known to major browsers, you may need to upload the CA’s certificate using this form. The selected file can contain multiple CA certificates in PEM format, one after the other.”
Thanks guys… I think I got this sorted. I got 2 CA certificates file from Comodo when I bought the SSL cert. I just appended the other cert at the bottom of the PositiveSSLCA cert and uploaded it like you said.
To be honest, I never had to do that with other SSL certs that I have installed previously. In this case, you are right, I did buy a “cheap-ass” cert, cost me $5 a year because I didn’t need top-notch security in this case. The website I am working on is just serving images.
In hindsight, I probably should have gone with a more expensive option, given that I just lost a day troubleshooting this problem.