• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Recent update broke legacy http/https sites

CruzMark

Regular Pleskian
Server operating system version
Centos 7.9.2009
Plesk version and microupdate number
Plesk Obsidian v18.0.56_build1800231106.15 os_CentOS 7
Something recently changed. We host up to 128 clients on a web server, each with their own IP. Starting recently, folks with compatibility mode turned on started seeing this issue with content no showing up or the wrong content showing up. I can't run the global reset for combining ssl and non-ssl, as some of these may still be using both. Can we just get the compatibility mode checkbox re-enabled in the plesk interface? At least that way my support folks can fix the issue. Running on Centos 7 with latest updates.
 
I found a work flow for this, but it is really stupid complicated for the majority of our support folks. This isn't really a great 'fix', but it does work.

Procedure:

Log into Plesk server and go to 'Tools and Settings' then "Database Servers". Launch the webadmin for the MariaDB database.
In database 'PSA' find the table 'hosting'
Find the domain you need to work on in the 'www_root' field.
Edit the entry and change 'same_ssl' from 'false' to 'true'.
Save the entry.

Then, go back to "Tools and Settings" then "Webserver Configuration Troubleshooter" in the troubleshooting section.
Use the search function to search for the domain.
Rebuild the httpd.conf config file. This should actually empty it out.
Now from that Configuration Troubleshooter screen, click on Apache to get the dropdown to restart the server.

Once server restarts, this should be resolved. Watch out for cached entries in your browser.

Uggghhhh.
 
Back
Top