• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue No access to control panel after removing mail components (404)

MikeSkril

New Pleskian
Hi,

I removed the mailserver and webmail components within the control panel and this was finished at 100% (there was a mention of errors but I cannot recall).
After going back to the control panel, I got a 404 error. Now I cannot reach the control panel anymore.

I tried to repair thru the terminal but the plesk commands are not working. I have not much terminal experience and would appreciate some help.

Plesk 18.0 on
Ubuntu 18.04.5 LTS


Code:
root@foobar:~# plesk
Usage: plesk [command]

Commands:
  bin - Run the specified Plesk command-line utility (e.g., domain, client)
  checkupgrade - Download the preupgrade checker for the latest, or specific Plesk version
  conf - Open the specified Plesk configuration file in the editor
  daily - Run daily maintenance script
  db - Database related commands. Open MySQL console by default.
  ext - Call a command-line interface of the specified Plesk extension
  help - Show help and exit
  installer - Plesk Installer shortcuts and command completion
  listupgrade - List versions current instance can upgrade to
  log - Follow Plesk logs
  login - Generate login link for specified user
  php - Run a PHP script using the Plesk PHP interpreter
  repair - Check and repair Plesk
  sbin - Run the specified Plesk internal utility
  version - Show product version information
root@foobar~# plesk version
open /usr/local/psa/version: no such file or directory

Code:
root@foobar:~# plesk repair all -y
Unknown Plesk command-line utility: "repair"

I followed these steps so far but that did not change anything:

Here some stuff from my syslog:
Code:
Jun  7 19:05:03 foobar systemd[1]: Failed to start Startup script for Panel sw-engine.
Jun  7 19:05:03 foobar systemd[1]: plesk-task-manager.service: Service hold-off time over, scheduling restart.
Jun  7 19:05:03 foobar systemd[1]: plesk-task-manager.service: Scheduled restart job, restart counter is at 12283.
Jun  7 19:05:03 foobar systemd[1]: Stopped Plesk Task Manager Service.
Jun  7 19:05:03 foobar systemd[1]: Starting Plesk Task Manager Service...
Jun  7 19:05:03 foobar systemd[1]: plesk-task-manager.service: Failed to parse PID from file /run/plesk-task-manager/task-manager.pid: Invalid argument
 
Last edited:
Back
Top