Facebook
Twitter- Server operating system version
- AlmaLinux 8.8 x86_64
- Plesk version and microupdate number
- Plesk Obsidian 18.0.54.4
Just had our VPS upgraded to 4GB RAM and two cores. The OS is Alma Linux. So expected things to start working more soothingly. Accessing the server via Dutch VPN so one close to server from a location abroad. I got this error multiple times now opening WordPress Dashboard main page:
and in the browser you can see
This seems to be related to the upstream. We use PHP FM and Apache as a proxy server for Nginx. This seems to be the standard Plesk setup or the one done by TransIP.nl for our VPS.
Nginx config shows
Nginx is in proxy mode and uses Apache in front. But now I need to see how I can debug and fix this issue. Any ideas how?
1692#0: *1900 upstream timed out (110: Connection timed out) while connecting to upstream
and in the browser you can see
504 Gateway Time-out
I also read Issue - NGNIX ERROR "upstream timed out (110: Connection timed out)" but already had set these settings to deal with time-outs:
FcgidIdleTimeout 120
FcgidProcessLifeTime 120
FcgidConnectTimeout 120
FcgidIOTimeout 120
Timeout 120
ProxyTimeout 120
FcgidIdleTimeout 80
FcgidProcessLifeTime 60
FcgidConnectTimeout 60
FcgidIOTimeout 90
This seems to be related to the upstream. We use PHP FM and Apache as a proxy server for Nginx. This seems to be the standard Plesk setup or the one done by TransIP.nl for our VPS.
Nginx config shows
location / {
proxy_pass http://xx.xx.xxx.xxx:7081;
proxy_hide_header upgrade;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;
}
Nginx is in proxy mode and uses Apache in front. But now I need to see how I can debug and fix this issue. Any ideas how?
arams:acme:error:rejectedIdentifier