DNS & TLS Setup

Point a domain name at your Field Day Commander server and secure it with HTTPS.

How-To Guides › DNS & TLS
Advanced · Optional

This guide is only necessary if you want to make Field Day Commander accessible over the internet. If you're running it on a LAN at your Field Day site with no outside access, you can skip this entirely. Field Day Commander works fine on a local network over plain HTTP.

Public access lets club members register equipment and sign up for shifts from home, or follow the live score during the event. The steps below configure a domain name and HTTPS for that access.

Do not skip TLS

Running over plain HTTP on a LAN is fine. Running over plain HTTP on the open internet means passwords and session tokens travel in cleartext, and anyone on the path can read them. If you're exposing Field Day Commander to the internet, use TLS. Let's Encrypt is free.

What You Need

  • A domain name you control. You can register one from any registrar (Namecheap, Cloudflare, Porkbun, etc.). Something like yourcallsign.com works well.
  • A public IP address at the location where Field Day Commander will run, or the ability to set one up (most home/club internet connections have one).
  • Access to your router to set up port forwarding.
  • Field Day Commander already deployed and running on your Pi or server.

How It Fits Together

When someone types fd.yourcallsign.com in their browser, three things happen in sequence:

  1. DNS translates the domain name into your public IP address.
  2. Your router forwards incoming traffic on ports 80 and 443 to the Pi on your local network.
  3. TLS encrypts the connection so passwords and session data can't be intercepted.

This guide walks through each piece.

Step 1: Get Your Public IP

From any computer on the network where Field Day Commander will run, find your public IP address:

On any computer at the siteTerminal
curl -s ifconfig.me
203.0.113.42

This is the IP address the rest of the internet uses to reach your network. Write it down. You'll enter it in your DNS settings.

Dynamic IP addresses

Most residential internet connections have a dynamic IP that can change periodically. For a weekend event this usually isn't a problem. If you want something more permanent, look into a dynamic DNS service like Duck DNS (free) that automatically updates your DNS record when your IP changes.

Step 2: Create a DNS Record

Log into your domain registrar or DNS provider and create an A record pointing your chosen subdomain to your public IP.

1 Go to the DNS management page for your domain.

2 Add a new A record:

Name / Host: the subdomain you want (e.g., fd for fd.yourcallsign.com)

Value / Points to: your public IP address (e.g., 203.0.113.42)

TTL: leave the default, or set to 300 (5 minutes) if available.

3 Save the record. DNS changes can take a few minutes to propagate, though most providers are nearly instant.

Verify DNS

After a few minutes, confirm the record is working:

On any computerTerminal
nslookup fd.yourcallsign.com
Name:    fd.yourcallsign.com
Address: 203.0.113.42

If it returns your public IP, DNS is set up correctly.

Step 3: Port Forwarding

Your router needs to know that incoming web traffic should go to the Pi. Log into your router's admin page (usually 192.168.1.1 or 192.168.0.1) and set up port forwarding rules:

  • Forward port 80 (HTTP) to your Pi's local IP address, port 80.
  • Forward port 443 (HTTPS) to your Pi's local IP address, port 443.

Port 80 lets Let's Encrypt verify you own the domain, and it lets Caddy send anyone who types http:// over to HTTPS. All real traffic goes through port 443, including the live updates that keep dashboards current. Those ride the same connection as the web pages, so you don't need to forward port 8080 or any other port.

Finding the Pi's local IP

SSH into the Pi and run hostname -I. It'll return something like 192.168.1.42. That's the address you forward to.

Every router is different

The exact steps depend on your router's make and model. Look for "Port Forwarding," "Virtual Server," or "NAT" in your router's settings. If you're not sure, search for your router model followed by "port forwarding" and you'll find step-by-step instructions.

Step 4: Deploy with TLS Enabled

Field Day Commander uses Caddy as its built-in web server. Caddy’s automatic HTTPS obtains and renews certificates using ACME certificate authorities such as Let's Encrypt. You don't need to install anything extra or manage certificates manually.

When you run the deploy script, include the --ssl and --email flags:

On the serverTerminal or SSH session
sudo ./deploy.sh --domain fd.yourcallsign.com --ssl --email you@example.com

If you've already deployed without TLS, you'll need to redeploy with these flags to enable it.

If the server runs a firewall, the deploy script opens port 443 for you but not port 80. With UFW active, open it yourself:

On the serverTerminal or SSH session
sudo ufw allow 80/tcp

On a server that uses firewalld, run sudo firewall-cmd --permanent --add-service=http and then sudo firewall-cmd --reload.

The script sets APP_URL to https://fd.yourcallsign.com, configures the Caddyfile with your domain, and starts the service on port 443. Caddy validates control of your domain, obtains a TLS certificate, and starts serving HTTPS. Its default challenge options use port 80 (HTTP-01) or port 443 (TLS-ALPN-01). Caddy handles renewal automatically while the required connectivity remains available.

Port 80 must be reachable

Keep port 80 reachable for HTTP redirects and HTTP-01 validation. Caddy can also validate over port 443 with TLS-ALPN-01; port 80 is not the only certificate-validation path. See Let’s Encrypt’s challenge documentation and Caddy’s automatic HTTPS requirements. Check the server logs if neither challenge succeeds.

Already have a certificate?

If you have your own certificate files (from your organization or another CA), you can provide them directly instead of using Let's Encrypt: sudo ./deploy.sh --domain fd.yourcallsign.com --ssl --ssl-cert /path/to/cert.pem --ssl-key /path/to/key.pem

Verify HTTPS

Open a browser and go to https://fd.yourcallsign.com. You should see Field Day Commander load with a padlock icon in the address bar. If you get a certificate warning, check the logs: sudo journalctl -u fdcommander --no-pager.

Caddy automatically redirects HTTP to HTTPS, so if someone types http://fd.yourcallsign.com they'll be sent to the secure version automatically.

Quick Reference

Once all the pieces are in place, the setup looks like this:

  1. DNS: an A record points fd.yourcallsign.com to your public IP.
  2. Router: ports 80 and 443 forward to your Pi's local IP.
  3. Deploy script: --ssl --email tells Caddy to obtain a Let's Encrypt certificate automatically.
  4. Caddy: handles HTTPS, certificate renewal, and HTTP-to-HTTPS redirects.

Club members can now visit https://fd.yourcallsign.com to register equipment, sign up for shifts, follow the live score, and sign the guestbook, all over an encrypted connection.

Back to LAN for the event?

Plan the address operators will use before moving the server to an offline site. A public hostname must resolve to the server's address on the field LAN if you want to keep using it there. Alternatively, configure the server for a local address using the --domain guidance in Set Up a LAN for Field Operations. Simply opening the server's local IP in a browser does not change its configured hostname.

Test the chosen address from the actual station devices with the internet disconnected before the event. Core event operation does not require internet access, but public DNS lookups and certificate issuance or renewal need their respective connectivity.