Facebook
TwitterHi, I've got a problem and I've been trying to work it out for a few days.
I run Plesk 10.4.4, CentOS5 - 2.6.18-028stab095.1 #1 SMP Mon Oct 24 20:15:15 MSD 2011 x86_64 x86_64 x86_64 GNU/Linux
At the weekend I was making a number of small changes to configuration files - stuff that didn't seem to be covered by Plesk. They *seemed* harmless enough.
For example, I changed some logging parameters, installed logwatch, changed httpd.conf to use my email as the admin email.
Everything seemed fine - I was restarting various services as I went along, and the panel was still working. I really was just making what I thought were small changes. I know my way around.
I then chose to get a StartSSL certificate. I followed instructions from here http://stevejenkins.com/blog/2011/09/how-to-use-a-free-startssl-certificate-in-postfix-for-ssltls/
I got as far as making a directory and running openssl req -new -newkey rsa:32768 -nodes -keyout hostname.domain.key -out hostname.domain.csr (with my domain of course).
As you'd expect with a 32768 bit key, this took a few hours.
While it was generating the key, the panel stopped working. Of course, that is a coincidence - but this is why it's hard - I'd restarted various things and the panel had still worked; I have no idea why it would stop working when I was leaving the machine alone to generate the key.
When I go to mydomain:8443, first I get a "the connection was reset", and if I reload the page, I get a "Firefox can't establish a connection to the server".
I've checked my core access_log, error_log, httpsd_access_log, messages, secure, every log file I can think of.
The only damaging thing I can think of is that I got annoyed at the little bug that generates new *.include files for every virtual host every day, and I deleted the oldest in each directory. Seems harmless cos I left 2 versions in each directory (I know psa cleans it up to the 5 most recent, but it was annoying me!)
So it's possible that the Plesk server is not getting configuration to listen on 8443. It would explain why I'm not getting any error logs - the thing starts up, doesn't find a config file, and maybe stops.
But, these files exist (yep, Plesk generates a new version of these as well every time any changes are made)
I can't think which of the changes I made might've caused this. I know, this is that typical user thing - but I honestly did try to be methodical! I did reverse changes, and I even include my name in most config files if I change things, so I can do a text search and reverse any changes that don't work.
For example, I noticed a lot of attacks against the default web server, so I tried putting in an .htaccess file. There was none there so I created one. It didn't have any effect, so I removed it. Those were the sort of changes I was making.
Please can someone guide me through how to diagnose this problem?
I have been trying to work it out through constant googling. It's hard - "panel not working" or even "plesk 8443 configuration" or any number of combinations aren't helping me. Every other forum posting has some other error with it - but my psa is starting fine, all my webservers are running fine, my email is fine, everything is lovely.
Therefore I'm fairly sure it's just one small thing, one simple config change, that I made. Generally, I reversed every change I could remember - even changing "serveradmin" back to its default setting.
I also tried 2 other things: 1) bootstrapper repair (but that is v10.13.4 and I'm on 10.4.4), which reported success, and 2) restoring configuration files from backup. I take a remote backup every hour - but I guess this is the downside of a great bit of software like Plesk: So much config is in databases and different parts of the file system.
Please let me know what you'd like me to post here and I'll happily comply
I run Plesk 10.4.4, CentOS5 - 2.6.18-028stab095.1 #1 SMP Mon Oct 24 20:15:15 MSD 2011 x86_64 x86_64 x86_64 GNU/Linux
At the weekend I was making a number of small changes to configuration files - stuff that didn't seem to be covered by Plesk. They *seemed* harmless enough.
For example, I changed some logging parameters, installed logwatch, changed httpd.conf to use my email as the admin email.
Everything seemed fine - I was restarting various services as I went along, and the panel was still working. I really was just making what I thought were small changes. I know my way around.
I then chose to get a StartSSL certificate. I followed instructions from here http://stevejenkins.com/blog/2011/09/how-to-use-a-free-startssl-certificate-in-postfix-for-ssltls/
I got as far as making a directory and running openssl req -new -newkey rsa:32768 -nodes -keyout hostname.domain.key -out hostname.domain.csr (with my domain of course).
As you'd expect with a 32768 bit key, this took a few hours.
While it was generating the key, the panel stopped working. Of course, that is a coincidence - but this is why it's hard - I'd restarted various things and the panel had still worked; I have no idea why it would stop working when I was leaving the machine alone to generate the key.
When I go to mydomain:8443, first I get a "the connection was reset", and if I reload the page, I get a "Firefox can't establish a connection to the server".
I've checked my core access_log, error_log, httpsd_access_log, messages, secure, every log file I can think of.
The only damaging thing I can think of is that I got annoyed at the little bug that generates new *.include files for every virtual host every day, and I deleted the oldest in each directory. Seems harmless cos I left 2 versions in each directory (I know psa cleans it up to the 5 most recent, but it was annoying me!)
So it's possible that the Plesk server is not getting configuration to listen on 8443. It would explain why I'm not getting any error logs - the thing starts up, doesn't find a config file, and maybe stops.
But, these files exist (yep, Plesk generates a new version of these as well every time any changes are made)
I can't think which of the changes I made might've caused this. I know, this is that typical user thing - but I honestly did try to be methodical! I did reverse changes, and I even include my name in most config files if I change things, so I can do a text search and reverse any changes that don't work.
For example, I noticed a lot of attacks against the default web server, so I tried putting in an .htaccess file. There was none there so I created one. It didn't have any effect, so I removed it. Those were the sort of changes I was making.
Please can someone guide me through how to diagnose this problem?
I have been trying to work it out through constant googling. It's hard - "panel not working" or even "plesk 8443 configuration" or any number of combinations aren't helping me. Every other forum posting has some other error with it - but my psa is starting fine, all my webservers are running fine, my email is fine, everything is lovely.
Therefore I'm fairly sure it's just one small thing, one simple config change, that I made. Generally, I reversed every change I could remember - even changing "serveradmin" back to its default setting.
I also tried 2 other things: 1) bootstrapper repair (but that is v10.13.4 and I'm on 10.4.4), which reported success, and 2) restoring configuration files from backup. I take a remote backup every hour - but I guess this is the downside of a great bit of software like Plesk: So much config is in databases and different parts of the file system.
Please let me know what you'd like me to post here and I'll happily comply
