Maintain your own server

You control your VPS, provider account, operating system and backups. Infralane’s free management connects application operations to that server; it does not replace server maintenance.

Update Crane

Customer-owned servers use the signed BYO updater installed during setup. Run it from your server terminal:

sudo /usr/local/sbin/crane-byo-update --update

Updates are manual. The updater verifies the release signature, restarts Crane, checks local health and restores the prior binary if that health check fails. It rejects version downgrades. Keep provider-console access and backups available; reverting a binary does not reverse data changes.

Refresh the dashboard after the update and verify the server connects. Check application endpoints, logs and metrics. Some features need an application redeployment after the node update; follow the specific feature’s instructions.

Server is running but appears offline

A running service confirms local startup, not a working management connection. Check the dashboard’s last-contact time, the server’s internet connection and outbound HTTPS/WebSocket access on port 443.

Run read-only checks on the server:

sudo systemctl status crane.service --no-pager
sudo journalctl -u crane.service -n 50 --no-pager

Review the output locally. Keep node credentials and enrollment-token files private, and redact logs before sending excerpts to support. TLS, DNS, network or backend errors can interrupt the connection. Do not disconnect or delete credentials just to retry a temporary outage.

Ports and firewall

Application HTTP/HTTPS traffic needs public access to ports 80 and 443. Management uses an outbound connection; it does not require an inbound SSH integration or a public Crane API port. Keep TCP ports 6060 and 4222 private.

Open additional service ports only when you intentionally publish TCP/UDP traffic. Review provider firewall rules and trusted source addresses.

Resize or maintain the VPS

Resize CPU, memory and storage through your provider. Review its charges and downtime requirements first. Follow the provider’s operating-system maintenance process and retain a tested backup. Infralane receives capacity updates from the connected node.

Disconnect safely

Open the pool’s Settings, select Disconnect server, and type the server name as requested. Disconnection revokes Infralane management access while preserving the VPS, local applications and data. Hosting charges continue with your provider. Reconnecting needs a new installation token.

If you want to move applications to a different server, plan configuration, data backup and restore, DNS and endpoint changes before switching traffic.