• 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.

Internal Server errors after update 33

Status
Not open for further replies.

LouisXLPA

New Pleskian
Since the 20th of februari I experience problems with a couple of PHP-based websites. They are hosted on Windows 2012 server with Plesk 11.5.30, and the sites are installations of Feng Office.

After troubleshooting this problem, I noticed that the only change during the period since last logon-without-problem is the Plesk update 33.

Also clean installations of Feng Office aren't working, while I used the installation-/rebuild-procedure on the 16th of februari without problems. (No other updates or configuration-changed were made since that time, only update 33.

Does anyone experience the same Internal Server (500) errors since update 33?
 
May be a problem with changes in the php.ini, most 500 errors derive from that.

As far as I see in the release info about MU #33 nothing php-related was changed. So this may be some mumbo jumbo mess-up with IIS as Plesk sometimes does.

Have a look at the IIS snap-in at the Server Manager and check out the Handlers of your domain, verfiy it is set to the correct php.ini and php engine.

That would be my shot without any additional details given by you... ;)
 
MaximilianW, thanks for your reply.

Eventually the problem was solved by recover the machine from a backup, and ïnstall the update.

Probably the update wasn't the cause. (The only relation with the update was the moment the problem occured.)
 
Status
Not open for further replies.
Back
Top