Services

In Server › Services you see the services the panel manages on this server and their state, and you can restart, start or stop them one by one. You also get there from the Services box of the Server page, with Manage.

What is in the list

Only the services installed appear, by group:

• Web: the nginx web server and, if you use it, the Apache compatibility for .htaccess files.
• PHP: one service for each PHP version installed.
• Databases: MariaDB and, if you turned it on, PostgreSQL.
• Mail: sending (Postfix), mailboxes (Dovecot), antispam (Rspamd) and its Redis, when the mail service is on.
• DNS, FTP, Security (antivirus, antivirus updates, fail2ban) and System (scheduled tasks, SSH access).

The state is Running, Stopped or Error. Stopped (Savings) is a PHP version without websites that the panel stopped on purpose with Savings: it starts again by itself as soon as a website needs it.

Restart, start, stop

Every running service has Restart and Stop; a stopped service has Start. The panel always asks for confirmation and tells you what happens: stopping nginx or PHP makes the websites unreachable, stopping MariaDB stops the websites that use it, stopping mail means messages are neither sent nor received (senders keep them in their queue and try again).

Before restarting or starting nginx, PHP, Apache, Postfix and Dovecot the panel checks their configuration. If there is an error the service is left as it is and you see the line of the error, for example the nginx file and line to fix: a restart can never take down a service that is working.

Good to know

• The panel itself is not in the list: it is updated and restarted from Updates.
• SSH access can be restarted but not stopped: stopping it could lock you out of the server.
• A stopped service stays stopped until you start it again or the server restarts.
• Every restart, start and stop is in the activity log, with who did it.
• The page is for administrators only.

Processes

The Processes page (from 0.76.0) shows the programs running, the busiest first, with user, site, CPU, memory and how long they've been running. Administrators see every process of the server; resellers and accounts see only those of their sites' users. Stop asks the process to close, Kill now ends it without waiting: it's for a stuck PHP process or a script using too much. PHP-FPM and applications start again by themselves at the next request. The system, the kernel processes and the panel are protected and can't be stopped from here. Every stop goes into the activity log.