• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Recent update broke legacy http/https sites

C

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.
 
You must log in or register to reply here.

Similar threads

B
Issue High latency, unreliable performance & 522 errors on a Plesk server that ran fine for 6+ months
Replies
8
Views
1K
HHawk
HHawk
Y
Issue Compatibility mod, wrong root directory
Replies
0
Views
1K
Yaniv Zahavi
Y
learning_curve
Resolved Plesk 18.0.52 System Updates / Extensions / Cron - Multiple Failures
Replies
7
Views
2K
floh
F
PeopleInside
Resolved The Plesk file plesk-ext-ruby.list broke updates and monitoring on Plesk
Replies
7
Views
3K
AYamshanov
AYamshanov
S
Question Safely update Plesk from Onyx to Obsidian
Replies
0
Views
1K
SergioP122
S
Back
Top