503 ERROR for just few users

[lucaDF]

Hi everyone,

we're facing a really bad problem with our dedicated server wiht Plesk11 (updated to the last version) + php fastgi installed.

Many of our users see quite often a 503 Error message and can't see many images, that are phisically present on the server and that are visible my the other users.

Deactivating nginx with the command:

/usr/local/psa/admin/bin/nginxmng --disable

those users don't see anymore the 503 and they can also see the images. BUT, deactivating nginx the secure version gives an error to the users. It seems that Apache can't see the certificate ( regularly bought and installed through plesk)

Reactivating nginx https starts to work again but the 503 problem comes back again.

Please help us understand how to solve the 503 problem affecting only few users, or at least how to deactivate nginx without the invalid certificate issue

Thanks

 

[paulieG]

Hi,

The 503 error ought to result in something being logged to the nginx error logs (look for something mentioning "upstream" which means apache).

With regard to the other issue, does this fix it :

/usr/local/psa/admin/bin/nginxmng --disable 
/usr/local/psa/admin/bin/httpdmng --reconfigure-all

If not, any chance you could drop back to Apache and point me to the URL?

Paul.

 

[lucaDF]

Thanks for your help!

Before reading your reply we tried another procedure, that is working at the moment... anyway we are worried that some automatical plesk update or even a simple operation like the creation of a new domain, could bring the situation back to start. This is the list of our actions to make apache be able to see the certificate:

1) We disabled nginx as described in the first post.
2) Overwritten the file /etc/pki/tls/certs/localhost.crt with the correct certificate
3) Overwritten the file file /etc/pki/tls/private/localhost.key with the correct private key
4) Created the file /etc/pki/tls/certs/ca-bundle.crt with the CA certificate
4) Enabled the directive "SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt" in the file /etc/httpd/conf.d/ssl.conf

In this way it all seems to work for now. But we want to understand as soon as possible what's the bug affecting this version of plesk, because otherwise we could find ourselves, at any moment, back to the first situation. We want to find a definitive solution. Could you help us?

Thanks

 

[abdi]

You could lock those files from being updated by any of the processes to avoid going back to square 1 by:

chattr +i <configuration file>

and Unlock by

chattr -i <configuration file>

while you dig or wait for a permanent solution!