These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for SSL overview . help needed please! on the new forum.
Web Hosting and Cloud Computing Control Panels
Hey Jeremy,
Yes, you need an IP for each SSL website, and you need to be able to give each new SSL website an IP for the SSL option to be available.
That said, if you only need one SSL site, you can get away with only having one IP, and we probably ought to document the process for doing that better (and we probably ought to allow one to be created before enforcing the "needs an IP" rule).
I'll ask Jamie to chime in with his thoughts on whether we can safely add a bend in the rules for this special case.
In the meantime, you could add your virtual server without SSL, and then use the Webmin Apache module (in the Servers category) to create a new virtual server for SSL with everything matching the Virtualmin created domain, except the port information.
So, something like this in the "Create a New Virtual Server" form:
Handle connections to address: Specific address .. 192.168.1.1
Port: 443
Document Root: /home/domain/public_html
Server Name: domain.tld
Copy directives from: domain.tld
Where domain.tld is your domain name, and 192.168.1.1 should be replaced with your actual server IP.
Save it, and apply changes. You may need to delete the "default" server on 443, if one exists.
--
Check out the forum guidelines!