searched for the answer but could not find anything.
When you visit siteworx and webmail you get a warning due to there being no ssl cert on there.
Is there a way to use an excising ssl cert with the siteworx login so there is no warning notice?
webmail login, is there a way to go to mydomain/webmail and use a ssl cert so there is no warning notice?
failing that using the ip address/webmail login, can this be configured so there is no warning notice?
What kind of “existing cert” do you mean? If you already have a SSL certificate for your domain and it works for home, the same cert should cover the webmail URL. The same cert should also work for Siteworx if you prefer names instead of IPs. For control panels I prefer using https with the server IP and just add an exception in the browser to nix the error.
If you don’t have a cert for the domain then try the LetsEncrypt plugin. You don’t need to add an extra namespace for the webmail URL.
HI Bear
Sysnop is correct in all aspects.
You could use your nodeworx ssl (as long as it is not self signed).
Your IP would not have a SSL on it due to SSL no longer available for IP addresses
You could use the Lets Encrypt plugin, and get an SSL from SSL on the domains you wish to use
If using your nodeworx SSL, you are best advised to change the rewrite for /webmail to go to yourdomainnodeworx/webmail eg if a browser requested clientdomain/webmail, th erewrite goto yourdomainnodeworx/webmail
Kudos to Sysnop
Many thanks
John
I see what bear means about Siteworx. It seems we’re talking two different issues with different answers.
Since I use IPs and it never occurs to me to use domains for Siteworx, I hadn’t noticed that using a Siteworx URL without port 2443 still redirects using the port #, and that’s why the browser can’t accept the certificate using https domain/siteworx – because the port # gets inserted either way.
You’re right about editing a file and like John suggested earlier, I believe you can setup a rewrite in your virtualhost file or with an .htaccess file in the domain’s root directory. Sorry, I’m not smart enough about Apache to advise you well on this.
Webmail is different and doesn’t redirect, so you shouldn’t be seeing this same behavior with the webmail URL. If you’re still getting a browser error using https with domain/webmail minus the port #, then something is wrong.
when I go to https://domain.com/webmail/ it throws a 500 internal server error? that’s why I thought it was incorrect url
using it with the 2443 port works ok
Sorry again bear, I’m stumped by your 500 error. Something isn’t right about your virtualhost or .htaccess if one exists. If you have an .htaccess try removing it temporarily just to see if the error goes away.
Didn’t you say in a different post that you’re using intoDNS? I’m beginning to wonder if you need to bypass them while troubleshooting. You seem to have separate problems that may or may not be related to your SSL and PTR issues.
Good day to you.
Thanks for all your help, this is a newly installed server/interworx but having a few issues so will open a ticket for support guys to have a look.
I feel there are a few permissions wrong some where, no rush this side of xmas though.
webmail error resolved after support pointed me in the right direction, this module was disabled.
LoadModule proxy_http_module modules/mod_proxy_http.so
re-enabled and webmail now working without an error, strange though as my last server worked ok with that module disabled.