Sorry, it's a low-range server right now, there's no way to add a certificate.
Hi Fred,
The issue with Apache is that an SSL cert can normally only be assigned to one virtual host, unless a unique IP address or port is assigned to the 2nd virtual host:
http://www.virtualmin.com/node/20250This approach would work if we could get, say, port 444 (or any other) reserved for our virtual host. Then we'd just require ssl in apache's .htaccess file (would have to be done by 'root'). This would automatically redirect http access to https on port 444
The problem with this approach is that anyone that manually goes to https would still go to port 443 on the Host, and would then end up at the wrong site, even though they typed in the name of our forum.
YUCK! There is a better work-around for use with Apache called 'SNI' (Server Name Indication):
http://wiki.apache.org/httpd/NameBasedSSLVHostsWithSNI"With SNI, you can have many virtual hosts sharing the same IP address and port, and each one can have its own unique certificate (and the rest of the configuration)."
Unfortunately, due to the level at which this approach must be implemented, it would have to be preformed by 'root' on the host server. This is probably more work than our service provider is interested in doing for us, but we could ask. It'd be a nice upgrade for them, and their own SSL cert expires on May 5 this year, so they might be willing to make the other changes at the same time.
In summary, there may well be no simple + effective way out of this. In that case I think our best way forward is to train our forum members:
- DO NOT use the same password as your email
- Login with HTTPS
- Create a Security Certificate Exception in your web browser
A 'sticky' thread could be created and place at the top of the Forum to do this.