• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

500 errors in Apache after updating to 10.4.4.

N

NikolayA

New Pleskian
After updating to 10.4.4. site placed on personal IP (not equal to server IP) got Apache 500 error (internal server error).
Sites placed on default server IP - work fine.

I'm try use /usr/local/psa/admin/bin/httpdmng --reconfigure-all but problem is stay here.

10.4.4 update #11, installed at january 11, 2012 06:26 AM
 
Last edited:
You must log in or register to reply here.

Similar threads

P
Resolved Smart Update fails during "Analyzing the test site before updating it" at 10%
Replies
2
Views
3K
Peter van der Kleij
P
C
Resolved Error 500 after changing from temporary .plesk.page to a real domain
Replies
2
Views
4K
celebrir
C
V
Issue Webmail (Roundcube) returns 500 error due to forced OS PHP 7.4 FastCGI instead of Plesk PHP handler
Replies
10
Views
6K
Sebahat.hadzhi
Sebahat.hadzhi
O
Issue Update to 20240318.git3b128b60-0ubuntu2.17 (Ubuntu for noble-updates by Ubuntu)
Replies
4
Views
3K
nmdpa3
N
Z
Resolved Plesk updates failing: 502 Bad Gateway after installer update + “Unable to receive update information” error
Replies
1
Views
2K
zihniates
Z
Back
Top