Ports, networks, files

Everything Deplo listens on, connects over and writes to disk.

At a glance

Open 80 and 443 to the internet, on the panel's server and on every server that runs apps. Nothing else: servers connect to the panel's address by themselves. Never publish 3000, 3101, 5432 or 2375.

Ports

Prop

Type

Common mistakes

  • Port 3000 is not open, on purpose. It binds 127.0.0.1, so the way back in when the proxy is what broke is ssh -L 3000:localhost:3000 [email protected], then http://localhost:3000. Short of that, the generated address (like deplo-cb00710a.deplo.site) answers over HTTPS whatever your domain is doing.
  • No server listens for Deplo. The server agent connects out and opens no port. One installed by an older Deplo listened on 9443 and closes it for good once it connects, so a firewall rule kept for 9443 can go.
  • Behind a router that cannot open 443? A Cloudflare Tunnel carries the panel over an outgoing connection instead.

Networks

These belong to the platform. Tenant stacks never join them:

Prop

Type

Tenant networks are created per Environment, and Traefik joins each one:

Prop

Type

A stack's compose key stays deplo; Deplo points it at the right tenant network. Platform service names are reserved on these networks so no app can answer for them. Network isolation has the details.

Address pools

Docker's default pools hold about 31 networks. Both installers (not on a storage-only server or a migration source) write a larger one to /etc/docker/daemon.json:

  • A 10.x.0.0/13 that overlaps no route on the host (10.200.0.0/13 when free), cut into /24 networks.
  • Container logs on the local driver, 20 MB x 5 files, unless a log setting exists.
  • An existing pool is never clobbered. The previous file is kept as daemon.json.deplo-bak.
  • The new file is validated with dockerd --validate. Docker is not restarted while containers run, and is rolled back if it does not come back.

Files on the panel's host

/opt/deplo/.env                     generated secrets, chmod 600
/opt/deplo/docker-compose.yml       Postgres + the control plane
/opt/deplo/traefik/                 the proxy stack
/opt/deplo/traefik/certs/           the fallback certificate, created once
/opt/deplo/acme/acme.json           issued certificates, chmod 600
/opt/deplo/data/                    build and upload staging
/opt/deplo/backups/                 pre-update database dumps, the 3 newest
/opt/deplo/.install-state           ports and takeover state the installer keeps
/opt/deplo/install.sh               the copy `deplo update` runs
/usr/local/bin/deplo                the host CLI
/var/log/deplo-install.log          the installer's transcript, chmod 600

On this host /var/lib/deplo-agent/traefik is a symlink to /opt/deplo/traefik, so the agent manages the panel's proxy.

Files on every server

/usr/local/bin/deplo-agent          the agent binary
/etc/systemd/system/deplo-agent.service
/var/lib/deplo-agent/               chmod 700
  agent.crt, agent.key, ca.crt      its mutual TLS identity
  bootstrap.env                     first-run enrollment, chmod 600
  link-addresses.json               the panel's addresses, chmod 600
  traefik/                          that host's proxy stack, acme/acme.json included
/data/stacks/                       one <deploy key>.yml per stack, chmod 600
/data/stacks/files/<deploy key>/    the app's env file and File storage, chmod 700
/data/backups/                      the agent's managed backup store, chmod 700
/etc/docker/daemon.json             plus daemon.json.deplo-bak
/var/log/deplo-agent-install.log    the installer's transcript

IPv6-only servers also get /usr/local/sbin/deplo-clat and deplo-clat.service.

Certificates live in the proxy's folder

acme.json holds every issued certificate. Deleting /var/lib/deplo-agent (or /opt/deplo) takes them with it, and Let's Encrypt rate-limits reissuance.

Common container names

Prop

Type

See also

Did this page help you?

On this page