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

mod_webapp broken on apache upgrade

P

phorium

Guest
When upgrading php to 4.3.10, I also upgraded apache to 2.0.52 (from 2.0.49). However, after the upgrade, I can no longer get apache to start if the webapp module is included in httpd.conf. (if I comment out that module everything starts up fine). Since mod_webapp is software provided by Plesk, I'm not sure where to turn to for help. In fact, the version that's provided by Plesk (4.1.29) is newer than any other version I can find for download. Anyone out there know of why this could break on an RPM upgrade of apache?

I'm running SuSE 9.1.

Thanks.
 
You must log in or register to reply here.

Similar threads

Azurel
Resolved ModSecurity shown as "On" in Plesk GUI but runtime is "Disabled" and modsec_audit.log stays empty
Replies
2
Views
2K
Azurel
Azurel
Azurel
Input AlmaLinux8to9 upgrade leaves Plesk in broken state with insufficient service checks and recovery guidance
Replies
2
Views
2K
Azurel
Azurel
O
Issue MariaDB upgrade clash with SELinux
Replies
6
Views
3K
scsa20
scsa20
O
Question OpenLitespeed extension for plesk
Replies
2
Views
4K
Ohya
O
A
Problem after Plesk upgrade script
Replies
1
Views
4K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top