- Plesk Onyx for Linux
- Plesk for Linux
While accessing Plesk or performing any actions the following error is shown:
CONFIG_TEXT: 502 Bad Gateway
The following error message appears in
CONFIG_TEXT: recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 203.0.113.2, server: , request: "POST <some url>
CONFIG_TEXT: [error] 17434#0: *4954 upstream sent too big header while reading response header from upstream, client: 203.0.113.2, server: , request: "GET /modules/xovi/index.php/log-analyzer/index/id/2 HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "example.com:8443", referrer: "https://example.com:8443/"
Low FastCGI buffer limits.
Connect to the server via SSH.
/etc/sw-cp-server/configwith a text editor:
# vi /etc/sw-cp-server/config
Increase FastCGI buffer limits using the editor:
CONFIG_TEXT: fastcgi_buffers 32 32k;
Restart sw-cp-server and sw-engine services:
# service sw-cp-server restart && service sw-engine restart
We got this problem today on a Onyx 17.5.3 machine while trying to edit emailadresses. This workaround help - perhaps it should be considered to mark this solution for Onyx, too.
Hi @Wolfgang Freudenberger!
Have you tried just restarting sw-cp-server and sw-engine before applying any changes to /etc/sw-cp-server/config?
There is a probability that the issue was fixed just by the restart.
It would be great if you check that (for example, reverting the settings back for a moment and checking whether or not the issue is still there).
In case adjusting of /etc/sw-cp-server/config is indeed required, I will definitely add this info to the article!
Hi @Alexandr Redikultsev,
Yep, tried everything, no chance of bringing the page back to life. This fix was the only way. It is kind of difficult to debug a 502 without any specific error. :D
Hi @Wolfgang Freudenberger.
Alright, I will add the note, thank you for sharing with us.
Please sign in to leave a comment.