Many Pulsed Media plans let you run your own containerised applications with Docker. Our wiki has the full setup:
- Docker on PMSS — how Docker works on your seedbox and how to get started.
- Docker — general Docker reference.
- Rootless DOCKER — running containers safely under your own account.
Ports and TLS for your own containers
When you expose a container’s web interface, two questions come up: which port, and what to do about HTTPS.
- Ports — there is no pre-assigned port for you. Pick a free, high, uncommon one and publish it with Docker’s
-p HOST:CONTAINER, avoiding the common web ports (those belong to the front proxy). If the port is already taken, Docker refuses immediately and you simply pick another. Whether a directly-published port is reachable from the public internet depends on host firewalling — so if you plan to expose something directly, confirm it is actually reachable from an outside network before relying on it. - TLS — the cleanest pattern on a shared box sidesteps both questions at once: bind the app to
127.0.0.1inside the container and reach it over an SSH tunnel or over WireGuard. The transport is already encrypted, so the app needs no certificate of its own, and there is no port to negotiate with other tenants. If you would rather expose an app directly, let it handle its own certificates.
Common questions
Can I reach my app on a custom address? — apps you run are reached through your seedbox’s existing web access. The Docker guides show how to expose a container’s web interface. If you want a specific path or sub-address for an app, open a ticket describing what you’re running and we’ll advise what’s possible on your plan.
My container won’t start or isn’t reachable — check the container’s own logs first (the Docker guide shows how). If it starts but you can’t reach it from a browser, it’s usually the port/address mapping — the guides cover this.
If you’re unsure whether a particular app is supported on your plan, just ask — open a ticket and tell us what you’d like to run.
