• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

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
2K
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