GoAdmio
GoAdmio Documentation

Restart Apache

From the GoAdmio knowledge base.

Restart Services

This page explains the Restart Services feature in GoAdmio. It lets you restart individual services — Apache, PHP-FPM, MySQL, mail, FTP, SSH, DNS, and the server itself — directly from the Admin Panel, without SSH.

Location: Admin Panel → Restart Services


Overview

Services occasionally need to be restarted: after a configuration change, to recover from a crash, to apply an update, or to clear a stuck state. The Restart Services page provides a simple interface for restarting each core service — no SSH required.

Each service on the page corresponds to a systemd unit on the server. Restarting via the panel runs the equivalent of systemctl restart <service>.

> Warning: Restarting a service briefly interrupts it. Websites may be unavailable for a few seconds. Restart during low-traffic hours, and never restart a service you do not understand — a wrong restart can take the server offline.


Available Services

The page lists the core services of a GoAdmio server:

| Service | What it does | Interruption |
|---|---|---|
| HTTP Server (Apache) | Serves all websites | Short — websites may be unavailable during restart |
| PHP-FPM Service for Apache | Runs PHP scripts for Apache | Short — PHP pages may show 502 during restart |
| MySQL Server | Database server | Short — database queries fail during restart |
| Mail Server (Postfix/Dovecot) | Email sending and receiving | Short — email delivery pauses during restart |
| FTP Server (VSFTPD) | File transfers | Short — active FTP sessions disconnect |
| SSH Server | Remote shell access | Short — active SSH sessions may disconnect |
| DNS Server | Authoritative DNS | Short — DNS lookups may fail during restart |
| Reboot | Restart the entire server | Long — all services stop and restart |

> Tip: Most restarts complete in a few seconds. MySQL and the full reboot are the longest.


How to Restart a Service

Restart Apache (HTTP Server)

  1. Log in to the GoAdmio Admin Panel.
  2. Navigate to Restart Services.
  3. Click HTTP Server (Apache) — or the restart icon next to it.
  4. Confirm if prompted.
  5. Wait a few seconds for Apache to restart.
  6. Verify websites load — see Apache Status.

Restart PHP-FPM

  1. Open Restart Services.
  2. Click PHP-FPM Service for Apache.
  3. Confirm.
  4. Verify PHP pages load — if they show 502, the FPM restart may still be in progress.
> Tip: If you have multiple PHP versions installed, each has its own FPM service. The panel may restart all of them, or you may need to restart the specific version — see PHP Manager.

Restart MySQL

  1. Open Restart Services.
  2. Click MySQL Server.
  3. Confirm.
  4. Wait for MySQL to come back up.
  5. Verify databases are accessible — see MySQL Databases.
> Warning: Restarting MySQL interrupts every database query on the server. Active transactions may be rolled back. Do not restart during heavy database use — it can cause data loss if a transaction is in progress.

Restart Mail Server

  1. Open Restart Services.
  2. Click Mail Server (Postfix/Dovecot).
  3. Confirm.
  4. Verify email delivery — see Email Accounts.

Restart FTP Server

  1. Open Restart Services.
  2. Click FTP Server (VSFTPD).
  3. Confirm.
  4. Verify FTP access — see FTP Accounts.
> Note: Restarting FTP disconnects any active file transfers. Wait for ongoing uploads or downloads to finish before restarting.

Restart SSH Server

  1. Open Restart Services.
  2. Click SSH Server.
  3. Confirm.
> Warning: Restarting SSH may disconnect your active SSH session. If you are connected via SSH, the restart may drop your connection — be prepared to reconnect.

Restart DNS Server

  1. Open Restart Services.
  2. Click DNS Server.
  3. Confirm.
  4. Verify DNS resolution — see DNS Manager and Track DNS.

Reboot the Server

  1. Open Restart Services.
  2. Click Reboot.
  3. Confirm.
> Warning: A reboot stops all services and restarts the server. Websites, email, FTP, and SSH are all unavailable during the reboot — typically 1–5 minutes. Only reboot when: > - A service cannot be recovered by a restart > - A kernel update requires it > - The server is unresponsive > > Notify customers before rebooting a production server.

Verifying the Restart

After restarting a service:

| Service | How to verify |
|---|---|
| Apache | Visit a website; check Apache Status |
| PHP-FPM | Visit a PHP page; check Service Status |
| MySQL | Open phpMyAdmin or run mysqladmin status |
| Mail | Send a test email; check Email Tracking |
| FTP | Connect with an FTP client — see FTP Accounts |
| SSH | Reconnect via SSH — see SSH Port |
| DNS | Run dig example.com — see Track DNS |
| Reboot | Confirm the server is up; check Service Status |


Via CLI

The same restarts from the shell:

```bash

Apache


systemctl restart httpd # RHEL-family
systemctl restart apache2 # Debian-family

PHP-FPM

systemctl restart php83-php-fpm # version-specific systemctl restart php-fpm # generic

MySQL / MariaDB

systemctl restart mariadb systemctl restart mysql

Mail

systemctl restart postfix systemctl restart dovecot

FTP

systemctl restart vsftpd

SSH

systemctl restart sshd

DNS

systemctl restart bind9 # or named systemctl restart named

Reboot

reboot
↑