• 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.

/vhosts/default directory is not behaving as expected

MatejM

New Pleskian
I have a really strange problem with the default vhost directory.

From what I understand the directory "/var/www/vhosts/default/htpdocs" should be used when there is no hosting setup for the domain (and the domain has valid DNS records pointing to the server) or if the domain is suspended in the panel.

The problem is when I type such domain in a browser or type in the IP address directly I get automatically redirected from http to https (which is also a problem) then one of the 3 things happen:
a.) if the directory "/var/www/vhosts/default/htpdocs" is empty I get the default apache page (that's expected).
b.) if there is an index.html file with only plain text inside, it loads and displays as expected
c.) if there is an index.html file with actual valid html inside it, the server loads content from the first still active domain on that IP (but without any images, css and other linked files)

The questions I have are:
Why is redirection from http to https happening?
How is it even possible to have such a strange behevior with "vhosts/default/htpdocs" directory?

Additional info:
- Plesk Panel for linux v11.0.9 Update #60
- CentOS 6.4 with default centos repositories
- "/var/www/vhosts/default/htpsdocs" directory has no impact whatsoever
- The setting in the Plesk panel for the IPs, have "none" as the default website and "default plesk certificate"

I have no idea where to even begin searching for this strange behavior. The apache and nginx config files (the global ones and the plesk autogenerated ones) seem to be ok, there are no signs that http to https redirection should be even happening.
 
Back
Top