• 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 Aliases showing website fine, actual website not working...

MarcoB

New Pleskian
I have a strange problem, which doesn't make any kind of sense to me..

I have 3 domains, one website and two aliases.

When you go to the website, it wil show one page. And after that it will provide a 500 error.
When you to to one of the aliases of the site, the site will work just fine.

Tried disabling/re-enabling, restarting httpd etc. etc. All no result.

What I have found out.
- When I disable cookies on the browser, the main site will start working correctly again. However, why are the aliases working fine?

Running
‪CentOS 6.7 (Final)‬
12.5.30 Update #70, last updated at Sept 23, 2017 03:56 AM

This error started on September 22 out of nowhere. Could this be related to an update on Plesk?
Any suggestions are very welcome!
 
I suppose the aliases are working, because they don't match the cookie set by the the website, and the browser with cookies enabled let's the site do some actions that crash it. It's not a web server or Plesk issue, but an issue of the website or a plugin that is being used. My suggestion is to disable all plugins and test again, then enable the plugins step by step until the test fails. Then you know which plugin is causing it.
 
Back
Top