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

Smart Update - wp-admin not working after update

Server operating system version
AlmaLinux 9.8 (Olive Jaguar)
Plesk version and microupdate number
Plesk Obsidian 18.0.80 #6
wp-admin gave error after Smart Update had run. (as far as i can see)

%domain%/wp-admin gave the following error page:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.

After turning off Plugin "Burst Statistics - Privacy-Friendly Analytics for WordPress 3.6.3" %domain%/wp-admin worked again.
3.7 is released 2 days ago, but update not available in Plesk, (Fixed some styling issues in Dashboard, maybe causing this issue?)

This plugin wasn't updated, a theme (Twenty Twenty 3.2, that isnt even active) was updated this morning 'manaully' through the Smart Update function.

Or the issue was caused by something else...

Is there another way, to automaticaly check if WP-admin is still working?
 
Based on the provided details, this is very unlikely to be a Smart Update bug but rather an incompatibility issue introduced by the new version of the plugin that Smart Updates didn't detect. I would suggest checking the domain logs for further details on what exactly is causing the issue leading to the Internal Server Error.
 
Back
Top