Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: cirkit on July 14, 2011, 10:19:48 PM

Title: [solved] Disaster struck my server, server manger, webserver, mail server down
Post by: cirkit on July 14, 2011, 10:19:48 PM
After 3 complete years of running , my certifacte expired today, so i followed the instructions to extend the certificate duration from contribs upto 1826 days, After reboot i lost access to server manager, http server (with 5 virtual domains) is not responding, email--pop3s and smtps is not responding, the only services which are working are FTP,SSH, I managed to log into server manger via tunneling (localhost:980) all the settings seem well, I issued reconfigue but then too no change, when i log into ssh (via putty, try to access server manager text version..it says connection refused) pl help all my domains and services are down..
Title: Broken SSL certificates (was Re: Disaster struck my server)
Post by: CharlieBrady on July 14, 2011, 10:47:39 PM
This should remove all your "customised" certificates, and start afresh with a standard self-signed certificates:

Code: [Select]
rm -f /home/e-smith/ssl*/*
signal-event post-upgrade
signal-event reboot
Title: Re: [solved] Disaster struck my server, server manger, webserver, mail server down
Post by: cirkit on July 14, 2011, 10:58:06 PM
Done! Thanks a million
I just want to know how does a certificate problem affect all these functionalities?
Title: Re: [solved] Disaster struck my server, server manger, webserver, mail server down
Post by: CharlieBrady on July 15, 2011, 03:31:22 AM
I just want to know how does a certificate problem affect all these functionalities?

https, pop3s, imaps, smtps - notice anything in common?
Title: Re: [solved] Disaster struck my server, server manger, webserver, mail server down
Post by: cirkit on July 15, 2011, 03:46:16 AM
Yes!...The "S"--Understood
Title: Re: [solved] Disaster struck my server, server manger, webserver, mail server down
Post by: CharlieBrady on July 15, 2011, 04:47:19 AM
Yes!...The "S"--Understood

The only mystery should have been http access to your websites. They were likely down because httpd (apache) failed to start because of an SSL certificate issue. Your httpd/error_log file is probably full of errors related to that. If httpd fails to start, http (port 80) and https (port 443) would both be unavailable. pop3s and smtps (annd imaps) being down should be obvious.