The Storages page is where you connect and manage the machines (or cloud buckets) that will hold your backups. Each storage shows link health, OS/type, IP/port, and live (or cached) disk usage so you can see capacity at a glance.

Who can view or change this

• View: users with the view_storage_servers_page permission.
• Add: requires add_storage_servers.
• Edit / Reset link: requires edit_storage_servers.
• Delete: requires delete_storage_servers.

What you’ll see

• A counter tile (e.g., 1 storage servers).
• A Clear Disk usage cached information action — usage is cached to keep the page fast; clear it to recalc now.
• An Add a new storage server button (modal).
• One card per storage with badges: LINK (green = connected, red = down), name, fetching method (SSH or SSL Tunnel), IP, port, OS/provider, and a gear icon to open the storage settings. Below each card, partitions (Linux) or overall quota (Drive/Dropbox) with a progress bar are shown.

Adding a Linux storage server

1) Click Add a new storage server and fill in Name, IP, SSH port.
2) On the storage host, log in as root and authorize bootstrap in one of two ways:

• Automatic access — run the one-liner shown in the modal: it downloads access.php and securely installs prerequisites.
• Manual access — paste the provided public key into /root/.ssh/authorized_keys (permissions 700 for .ssh, 600 for the file).

3) Submit the form. The panel will connect once as root to bootstrap, then create its own system user synconix with sudo NOPASSWD, deploy passphrase-protected SSH keys, and install the panel’s rsync under /opt/synconix/bin/rsync. After that, jobs run under the synconix user.

Fetching method (how the panel talks to storage)

• SSH (Slow) — standard SSH session per request. Easiest to allow, adds shell overhead per call.
• SSL Tunnel (Fast) — a persistent TLS tunnel (socat) that streams commands/data with lower latency. The panel generates a per-storage CA and client certs, installs the service, and restricts access by IP and certificate. Switch between methods from the storage settings.

Cloud storages (optional)

The panel can also use cloud providers via rclone configs: Google Drive, DigitalOcean Spaces (S3), Wasabi (S3), and Dropbox. The add flow asks for a storage name and provider, then guides you through OAuth or key entry.

• Google Drive — you’ll be shown a consent URL, paste back the verification code, and the panel writes the token to the rclone config.
• Dropbox — create an app (Scoped access), enter App key/secret, then paste the authorization code; the panel validates and saves a refreshable token.
• DigitalOcean / Wasabi (S3) — enter Access/Secret keys and the endpoint; the panel validates the remote.

Notes:
• Drive/Dropbox show Total / Used / Free and a usage bar.
• S3 endpoints usually don’t expose account-level usage; the card will say so.
• Cloud data itself is never deleted when you remove the storage from the panel (only the connection).

Reading the storage card

• LINK badge — green = reachable; red = click to open the storage page and repair.
• Fetching data over … — shows whether the card uses SSH or the SSL Tunnel.
• Usage — Linux lists each mounted partition with Size/Used/Free and a color bar (green < 50%, yellow 50–90%, red > 90%, dark > 98%). Data is cached; use Clear cache to refresh now.

Editing a storage

Open the gear icon on a card to:

• Change name, IP, SSH port (Linux storages).
• Switch the fetching method between SSH and SSL Tunnel (the panel installs/updates the service as needed).
• Reset link (Linux only) — if the link is down, you can re-bootstrap access via the same automatic/manual steps; this redeploys keys and utilities and flips the storage back to “linked”.
• Delete — remove the storage from the panel. If you check “Remove all associated backup schedules”, the schedules are deleted; otherwise they are disabled. (Cloud content is not removed.)

Security details (what happens under the hood)

• The panel uses a unique RSA keypair per server, stored in /home/synconixm/.synconix/private_keys/, with a salt-derived passphrase and 0600 permissions.
• Linux storages get a dedicated user synconix (sudo NOPASSWD) and tools under /opt/synconix/.
• The SSL Tunnel option sets up a TLS service that accepts only the panel’s client certificate and only from allowed IPs.
• Disk usage reads are cached locally (files under ~/.synconix/cache/) to keep the page snappy.

Troubleshooting

• LINK is red — open the storage page and use Reset link. If firewall blocks SSH, allow the panel’s IP and the configured port.
• Usage bars don’t update — click Clear Disk usage cached information to force a refresh.
• Cloud auth fails — repeat the OAuth/code step, verify keys/endpoint for S3 providers, and ensure outbound HTTPS from the panel.
• Switching to SSL Tunnel — if it fails to start, check that socat is installed on the storage and ports are open.