I’ve 2 ip-s assigned to my server. The second ip is dedicated, has 4 domain names on it, but only 1 domain use SSL.cert. : secure.mydomain.com
In the settings the SNI is enabled. I tried now to disable it, restart web server, nothing has changed :S
Before the update was working everything well with SSL-s… I don’t know, what another thing was happened with my server, to do this…
So I think, this is not SNI related thing… What do you think?
I’m sorry it was not SNI, but to be honest, the update should not have affected your SSL I don’t think. Have you checked your siteworx accounts to see if anyone has installed a SSL without you knowing, as that is what happened to me.
Did the update install correctly, if you check your logs it should be listed, if not, I’ll need to look up the commands to clean update interworx.
It is hard to fully know without first running some external tests on the domain, ie SSL check from qualssl, and to see what is shown in a browser when trying to access it. If you want to pm me the domain I’ll check for you externally or you can.
I’m thinking though, you may want to try to reinstall the SSL to see if that corrects the issue or you maybe best advised to open a support ticket with interworx.
I’m sorry I cannot be more helpful, but I hope it helps a little
xxx.xxx.xxx.210 “Master” ip, Shared, eth0, has a lot of Siteworx account on it, has self signed SSL.
xxx.xxx.xxx.212 Dedicated, eth0:0, has 1 siteworx account, 1 master domain (has SSL on secure.masterdomain.com) and 3 secondary domain (no SSL)
In the Interworx logs/upgrade.log there is nothing…
I’m sorry, I have to go for now, but please see pic showing SSL not enabled, which is the reason for your issue (most likely).
I have seen this before, and stop/start service usually clears it, so you may want to ssh and do the following commands just in case
service httpd stop - all apache should stop
service httpd start - please note if there any errors as it starts
test your website in a browser
Also, the log extract you posted is not an error, it is a warn, which will not cause https to not start, and is a common warn message I believe
If the above does not resolve your issue, and you have checked your https ports in firewall and on webserver, you would be best advised ot open a support a ticket with interworx (interworx.com/support I think it is)
I hope that helps a little, and the https is not enabled on both your domains/ip’s
Hi, after the upgrade the system has restarted… maybe then the ssl not started…?
Now I’ve done the restart in ssh, and everything is fine with it! Thank you!
I’ve restarted the web server through Nodeworx panel 3 times today, but nothing has changed… next time, I do this with ssh of course
I’m so pleased it’s now resolved and you should only use ssh to stop/start if there’s an issue. In general, it works lovely, it’s just occassionally you may need to do it, particularly if it involves SSL , but as I said, mostly it works lovely.
I hope you don’t mind but I’m not seeing what your issue is sorry.
Do you mean SSL does but match server name. This is common and to correct you need to rename server name to match SSL domain, but your on vps so I don’t think you can but in any event it has no issue with your SSL cert.
If you could post your actual issue it would help.
I hope you don’t mind and I know it is off topic slightly, but I have just run a quick test and your SSL looks fine, but your keys and ciphers are low, you may want to change them to stronger ones, and stop weaker protocols.
