- Server operating system version
- Debian 12
- Plesk version and microupdate number
- 18.0.62 Update #1
Hi folks,
I just went to Debian 12 (formerly Debian 10) by restoring a plesk update in my new server. It appears like there's a problem with sites proxying to apache2. This results in http-500 for end-users
nginx logs
This makes hardly any sense to me.
Of course, it is fine to bind apache2 to localhost - due to proxying it makes no sense to expose it. However, it looks weired that nginx tries an encrypted connection to apache2 on the same host using TLS and its external ip-address - non-tls on 127.0.0.1 would be more appropiate, I think.
I don't really understand how this is meant to be - but - how can I make plesk to align these ports?
Regenerating the config files using plesk repair web doesn't help. I haven't changed anything here.
Thanks, Jan
I just went to Debian 12 (formerly Debian 10) by restoring a plesk update in my new server. It appears like there's a problem with sites proxying to apache2. This results in http-500 for end-users
nginx logs
Code:
jluehr.de, request: "GET /favicon.ico HTTP/2.0", upstream: "https://82.165.242.31:7081/favicon.ico", host: "plesk.jluehr.de", referrer: "https://plesk.jluehr.de/"[/CODE
But apache is on localhost:
[CODE]
# netstat -tulpen | grep apache2
tcp 0 0 127.0.0.1:7082 0.0.0.0:* LISTEN 0 22655 1025/apache2
tcp 0 0 127.0.0.1:7081 0.0.0.0:* LISTEN 0 22634 1025/apache2
tcp 0 0 127.0.0.1:7080 0.0.0.0:* LISTEN 0 22632 1025/apache2
This makes hardly any sense to me.
Of course, it is fine to bind apache2 to localhost - due to proxying it makes no sense to expose it. However, it looks weired that nginx tries an encrypted connection to apache2 on the same host using TLS and its external ip-address - non-tls on 127.0.0.1 would be more appropiate, I think.
I don't really understand how this is meant to be - but - how can I make plesk to align these ports?
Regenerating the config files using plesk repair web doesn't help. I haven't changed anything here.
Thanks, Jan