• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Vhosts ignored depending on request origin

Stutonk

New Pleskian
CentOS 6.8, Plesk 12.5.30, Apache 2.2.15, no Nginx.

I have a server configured with multiple domains, everything created through the Plesk interface following the relevant documentation and otherwise there has been no hanky-panky or hand-editing of configs. Everything was working great until a recent `yum upgrade` (unfortunately rollback is not an option) and update to the most recent version of Plesk.

Now, depending on the origin of the request, the server either works totally fine (vhosts serve from their respective document roots) or it only serves from the default document root. That is, it someone from ISP A requests any page from any domain on the server, they get it just fine. If someone from ISP B requests that exact same page, they get /var/www/vhosts/default/htdocs/index.html (the DocumentRoot as listed in /etc/httpd/conf/plesk.conf.d/server.conf) or the default 404 page.

- I've tried with several ISPs; some work, some don't. I don't exactly know what to look for to determine what the some that work do differently than the others.

- Changing browsers, generating requests with curl, etc, doesn't affect everything. Only changing the origin of the request seems to make a difference.

- The ISPs that work ALWAYS work. The ISPs that don't ALWAYS fail.

- I've observed work/fail from within the same ISP (Comcast) depending on the connection method (either regular router SSID or Xfinity hotspot SSID on the same router. One works, one doesn't).

- Every DNS server I've tried resolves all requests to the correct IP.

- There's only a single IP for the server itself. Everything else is behind a NameVirtualHost

- httpd.conf contains the correct `Include conf.d/*.conf` line

- zz010_psa_httpd.conf is in the aforementioned conf.d directory and is the one autogenerated by Plesk and correctly includes all vhost configs, etc.

- All other configs are the ones autogenerated by Plesk

- Confirmed that all that NameVirtualHost jazz and other vhost stuff in the various configs IS present and correct

- The problem persists across invocations of `/usr/local/psa/admin/bin/httpdmng --reconfigure-all`

- The problem persists across restarts of httpd and full system restarts

- The output of httpd -S appears correct

- Everything works fine for requests originating from some ISPs so the configs must, in some general way, be correct.

- I've tried creating a new domain and seeing how it behaves. It works for the ISPs that work and fails for the ISPs that fail further reinforcing the idea of general config correctness.

Anyone have any idea what's going on here or what I can try to fix this problem?
 
Back
Top