Networking, firewall and ports
Every request to your server passes the same checkpoints in the same order: DNS resolves the name to your IP, the firewall decides whether the port is open at all, and Front Door decides which application answers. This page covers the firewall and the ports. Routing, domains and SSL are Front Door’s job and live on that page.
The path a request takes
- DNS — your domain’s A record resolves to the server’s IPv4 address.
- Firewall (UFW) — the packet is dropped unless its port is explicitly allowed.
- Front Door (nginx) — terminates TLS and routes by hostname to the right app.
- Your application — receives plain HTTP on a loopback port.
When something is unreachable, work down this list rather than guessing. A domain that resolves correctly but times out is almost always the firewall; a domain that returns nginx’s default page instead of your app is a routing problem, not a firewall one.
The firewall
Every Simplewala server runs UFW with a default-deny policy on incoming traffic. Nothing is reachable from the internet unless a rule allows it. Outgoing traffic is allowed, so your applications can reach package registries, APIs and SMTP relays without configuration.
Manage rules from Server → Networking → Firewall & Ports in the dashboard. Changes are applied to UFW on the server itself — the dashboard is not keeping a separate list, it is reading and writing the real ruleset.
Open by default
| Port | Purpose |
|---|---|
22 | SSH — server access and platform automation |
80 | HTTP — required for Let’s Encrypt certificate validation |
443 | HTTPS — where your sites and apps are actually served |
Port 80 stays open even on a site that redirects everything to HTTPS. Certificate renewal uses an HTTP-01 challenge, so closing it means your certificates stop renewing about sixty days later — a failure that arrives long after the change that caused it.
Opened when you enable a feature
| Ports | Opened by |
|---|---|
25, 465, 587 | Installing email hosting — see Email |
993 | IMAP over TLS, for mail clients |
30000–59999 | External database access, one port per database — see Databases |
These are opened for you when you turn the feature on, and closed again when you remove it. You do not need to add them by hand.
Ports to leave closed
Database engines listen on their standard ports inside Docker — 3306 (MySQL),
5432 (PostgreSQL), 6379 (Valkey), 5672 (RabbitMQ). Do not
open those to the internet. An exposed database port is found by automated scanners within
hours, and in-memory stores in particular have historically shipped with no authentication at
all.
When you need to reach a database from your laptop, enable external access on the database
itself. That allocates a high port in the 30000–59999 range,
proxies it to the container, and leaves the standard port closed.
Opening a port yourself
- Go to Server → Networking → Firewall & Ports.
- Click Add rule and enter the port number and protocol.
- Save. The rule is applied to UFW immediately.
Before adding one, check whether you need it. An application that is reached through a domain does not need its own port open — Front Door proxies to it on loopback, and adding a public port bypasses TLS termination and any rate limiting you have configured.
Domains and SSL
Pointing a domain at your server and issuing a certificate are covered on the Front Door page:
- Adding a route — pointing a domain at an app
- SSL certificates — issuing and renewing
- Path-based routing — several apps on one domain
- TCP tunnels — reaching databases through Front Door
Troubleshooting
The domain resolves but the page never loads
A connection that hangs rather than refusing is the signature of a dropped packet, which means
the firewall. Check that 443 is open on the Firewall & Ports page. If you are
testing a non-standard port, check that one too.
Certificate renewal started failing
Check port 80. Renewal uses an HTTP-01 challenge and it is the most common port to
close on the reasoning that the site is HTTPS-only.
I cannot connect to my database from my machine
External access is off by default and the standard engine port is deliberately closed. Enable
external access on the database, then connect to the high port it reports — not to
3306 or 5432.
Email is not being delivered
Outbound port 25 is blocked by most cloud providers, including on new accounts
where the rest of the firewall is fine. That is a provider policy rather than a rule on your
server, and the fix is an SMTP relay — see
SMTP relay when port 25 is blocked.