Virtual Server Private Cert in Usermin

6 posts / 0 new
Last post
#1 Fri, 10/30/2009 - 15:58
webwzrd

Virtual Server Private Cert in Usermin

One of my virtual servers is on it's own IP and I have a ssl certificate installed, however a visit to 10000 or 20000 on this domain still uses the servers cert. How do I allow this domain to use it's own cert when accessing usermin?

Seems like I had this working on a prior server, but I'm having trouble locating the answer now.

Brian

Fri, 10/30/2009 - 18:21
andreychek

Webmin and Usermin can each only have one SSL certificate installed.

So, you'll need to decide which one it is you want your users to see as they access the site.

I personally have it so that any users going to admin.any_domain.tld redirects to a URL that contains a valid SSL cert.

To copy a given SSL cert into Webmin or Usermin, you can go into Services -> Manage SSL Certificates, and click "Copy to Webmin/Usermin".

-Eric

Fri, 10/30/2009 - 18:23
webwzrd

I managed to get the virtual domain's private ssl cert working for that domain's usermin, but somehow in the process I broke it working on port 443 for the domain. Bad timing because this client gets a lot of end of the month payments.

Any suggestions would be appreciated.

Fri, 10/30/2009 - 18:39
webwzrd

We must have both submitted the last two responses at about the same time.

I have the severs cert now handling the servers shared IP webmin access and the one the belongs to the unique IP is working to access that domains webmin access. But as I said above, somehow I lost the ability to access port 443 on that separate IP.

Are you still saying that even though I had some success with the original goal, it's not suppose to work that way?

Actually at this point the most important thing it to get port 443 working again.

Fri, 10/30/2009 - 19:01
webwzrd

Okay, got everything working.

I noticed one odd thing in httpd.conf, the 443 section was at the bottom of all the other sites on the server, yet the port 80 section was up near the top of the list - This must have occurred after I had done an ssl restore on the site. On the other site (server's domain name) that has a certificate, the 443 section is right above the 80 sections. I therefore move the 443 section from the bottom to where it made more sense and (I'll be darn) it worked.

Fri, 10/30/2009 - 19:06
andreychek

Good, glad to hear you got it working, thanks for the update!

-Eric

Topic locked