• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Loopback HTTP connections going to wrong vhost

dtbaker

Basic Pleskian
Hello,

I just upgraded from 11 to 12.

In /var/log/httpd/access_log it is now full of requests like this from all the different WordPress installs on this box:

[25/Nov/2014:22:17:40 -0500] "POST /wp-cron.php?doing_wp_cron=1416971860.40590500831604003906 HTTP/1.0" 404 293 "-" "WordPress/4.0.1; http://xxxxxxxxx"
[25/Nov/2014:22:17:49 -0500] "POST /wp-cron.php?doing_wp_cron=1416971869.76135206222534179687 HTTP/1.0" 404 275 "-" "WordPress/4.0.1; http://xxxxxxxxx"
[25/Nov/2014:22:18:24 -0500] "POST /wp-cron.php?doing_wp_cron=1416971904.39924407005310058593 HTTP/1.0" 404 284 "-" "WordPress/4.0.1; http://xxxxxxxxx"


Along with some other requests generated by server side scripting trying to "hit" the local HTTP server.

If I ssh into the server and try a loopback http connection, something like this:

myserver# telnet mywebsite.com 80
Trying 54.x.x.x...
Connected to mywebsite.com.
Escape character is '^]'.
GET /images/logo.png HTTP/1.0
Host: mywebsite.com


The response is HTTP/1.1 404 Not Found and a new entry in /var/log/httpd/access_log is added, no entry in /var/www/vhosts/mywebsite.com/statistics/logs/access_log for local connections.

So it seems connections from "local" are hitting the default plesk site, and not going to the correct vhost.

Does anybody know how to solve this? Lots of things have ground to a hault.

(edit: I tried disabling mod_security/restart httpd and that didn't fix it)

(edit2: this is plesk on AWS with eth0 on a private IP and eth0:1 running an elastic IP address. The problem here is mywebsite.com resolves to the elastic ip address, but nginx is set to listen on the internal private ip address. adding a local /etc/hosts to resolve mywebsite.com to the internal ip address fixes the issue, but that means I have to do it for EVERY vhost on this box! )

Thanks heaps,
Dave
 
Last edited:
Back
Top