• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Admin Panel not working

BleBle

New Pleskian
Hello,

i tried to login into Plesk Admin Panel yesterday and got: "CONNECTION_REFUSED" from the browser. The Webserver, Mailserver, Fail2Ban, SSH are working. A few days before the login to plesk was working normal. The server is running CentOS7.

I tried "plesk repair all" and got Unknown Plesk command-line utility: "repair"

How can I fix this ?

UPDATE:
I got help by a friend and now the Plesk Admin Panel is running again. But now the webserver is down. When I login into Plesk i got the following Message:

New configuration files for the Apache web server were not created due to the errors in configuration templates: Can not restart web server: INFO: [Thu Apr 25 16:12:46 CEST 2019]: Service: httpd, Action: start Trying to start service httpd... failed Apr 25 16:12:46 iamyourshop.de systemd[1]: Starting The Apache HTTP Server... Apr 25 16:12:46 iamyourshop.de httpd[3279]: [Thu Apr 25 16:12:46.518019 2019] [pagespeed:warn] [pid 3279:tid 140130386102400] ModPagespeedInheritVHostConfig is deprecated. Please remove it from your configuration. Apr 25 16:12:46 iamyourshop.de systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE Apr 25 16:12:46 iamyourshop.de kill[3281]: kill: cannot find process "" Apr 25 16:12:46 iamyourshop.de systemd[1]: httpd.service: control process exited, code=exited status=1 Apr 25 16:12:46 iamyourshop.de systemd[1]: Failed to start The Apache HTTP Server. Apr 25 16:12:46 iamyourshop.de systemd[1]: Unit httpd.service entered failed state. Apr 25 16:12:46 iamyourshop.de systemd[1]: httpd.service failed. WARNING! Some problems are found during start service httpd(see log file: /var/log/plesk/rc_actions.log) Continue... /usr/local/psa/admin/sbin/pleskrc execution failed: Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. . Detailed error descriptions were sent to you by email. Please resolve the issues and click here to generate broken configuration files once again or here to generate all configuration files.

I then clicked "here to generate broken configuration files" but the websites are still down.
 
Last edited:
Obviously that something wrong with Apache mod_pagespeed module. Try to disable this module in Apache settings.
 
Back
Top