• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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