The Servers section lists every production server you back up and lets you add, edit, repair the SSH link, or remove a server. From here you can see OS/panel detection, SQL client, rsync version, whether the server has any schedules, and the live link status.

Who can view or change this

• View: view_production_servers_page
• Add: add_production_servers
• Edit / Reset link: edit_production_servers
• Delete: delete_production_servers

Top overview

A counter shows how many servers are added (X of Y) where Y is your license limit.

Server table (what each column means)

• ID — internal numeric ID.
• Server name — the label you set (FQDN or any name).
• IP / Port — SSH endpoint used by the panel.
• OS — distribution family detected on first contact.
• Web Panel — auto-detected: cPanel, Plesk, DirectAdmin, or none.
• SQL — SQL client found (mysql/mariadb/none).
• Rsync — the rsync version under /opt/synconix/bin/rsync.
• Scheduled — whether any backup schedules target this server.
• Link — Up if reachable; Down (click to repair).
• ⚙ — open the server settings page.

Adding a production server

1) Click Add a new production server and fill: Name, IP, SSH Port.
2) On the server (as root), authorize bootstrap:

• Automatic access: run the one-liner shown in the modal to download and execute access.php.
cd /root && curl -o access -s -k -L https://<panel-host>/access.php && bash access
• Manual access: temporarily set PermitRootLogin yes, then paste the provided public key into
/root/.ssh/authorized_keys (permissions 700 for .ssh, 600 for the file).

3) Submit. The panel logs in once as root to bootstrap, then:

• Creates system user synconix with sudo NOPASSWD and home /opt/synconix/home.
• Generates a unique RSA keypair (passphrase-protected), installs the public key on the server, and stores the encrypted private key under /home/synconixm/.synconix/private_keys/<ip>.prv (0600).
• Installs the panel’s rsync in /opt/synconix/bin/rsync and helper scripts in /opt/synconix/scripts.
• Detects OS, control panel, SQL client, and records reachable IPs. The temporary root key used for bootstrap is removed.

Server settings (edit page)

• Change Name, IP, SSH Port. The panel verifies SSH and keeps the link status updated.
• Reset Link (only when link is down): re-bootstrap access. You can use the same automatic or manual steps; the panel redeploys keys/utilities and flips status back to Up if successful.
• Delete Server: removes the server from the panel. Options:

• Delete all associated data — removes this server’s data from storage nodes (Linux storages; cloud content remains attached to the bucket).
• Force remove — skip remote cleanups if the server is unresponsive.
• Schedules and logs tied to this server are removed; otherwise, if you don’t delete data, schedules are disabled.

Security notes

• Per-server RSA keys are passphrase-encrypted (salt derived at deploy time) and only unlocked by the panel agent when needed.
• The synconix user isolates backup operations. Root is only used for first-time provisioning and key resets.
• All transfers run over SSH (or, for some advanced setups, a locked rsync daemon/tunnel started by storage during jobs).

Troubleshooting

• Link: Down — open the server row (⚙), use Reset Link. Ensure firewall allows the panel’s IP to the SSH port and that authorized_keys hasn’t been wiped.
• Panel can’t detect rsync/SQL — run the repair (Reset Link) so the panel reinstalls utilities and refreshes detection.
• License limit reached — the “Add server” modal will warn; remove unused servers or upgrade your license.

Typical next step

After the server shows Up, go to Schedules → Create, select this server and a storage, define include/exclude paths (and SQL options), then run the first backup.