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

Apache Template error after Update

S

Shoto11

Guest
Plesk 10.4.4#4 Debian 6 x86_64

Hello,

after update from Plesk 10.3.3 I recognized another error in Plesk Backend Panel. If I do any changes in backend an error appears like "apache could not restart" - I can restart apache manual - works fine. But when I go to the backend this error appears:

"Fehler: Es wurden keine neuen Konfigurationsdateien für den Apache-Webserver erstellt, da Fehler in den Konfiguration-Templates vorhanden sind. Die detaillierte Fehlermeldung wurde Ihnen per E-Mail zugesandt. Bitte überprüfen Sie Ihre E-Mails, beheben Sie die Fehler und klicken Sie auf hier, um die Konfiguration erneut zu starten. "

(means no Apache-Configure-Data-File found) in E-Mail appears the error that "apache could not restart".

So I makes new one with
/usr/local/psa/admin/bin/httpdmng --reconfigure-all

All works fine, no error in Backend

But any time I do some changes in backend the same error appears.

I don't understand whats wrong. Perhaps the apache restart took to long time for Plesk-Backend?
 
no one any idea? perhaps a problem with the number of domains? hosting 738 domains
 
You must log in or register to reply here.

Similar threads

E
Resolved Service apache down after update yum / Origin Modsecurity
Replies
3
Views
3K
Erwan
E
W
Resolved 421 Misdirected Request on IP address after Apache update
Replies
3
Views
10K
WiseWill
W
N
Issue 421 Misdirected Request on Apache-only Plesk server after recent Apache update (CVE-2025-23048)
Replies
2
Views
12K
NatuurlijkHosting
N
M
Issue Backup to FTPS server fails after upgrade to Plesk 18.0.64
Replies
1
Views
3K
mjehlenz
M
S
Issue no installation of components possible anymore
Replies
6
Views
5K
shopuser
S
Back
Top