Machine settings › Address (on a phone: More › your machine › Address) gives the dashboard's machine a free yourname.playkeeper.me name or your own domain, and the dashboard a Let's Encrypt certificate that renews by itself. With your own domain, add the records Playkeeper lists where you manage the domain (an A record, and an SRV record for each server not on port 25565) and open port 80 for Let's Encrypt's checks; each server then joins at its own address, without a port. Under your own domain, Servers' own addresses can give a server an address of its own, like alex.example.com next to the machine's mc.example.com: add its A and SRV records, and players join it there without a port, a browser opening it gets that server's own public page, and Playkeeper gets its certificate, at most a few new ones a day. Or turn on An address for each server there and add one record, *.mc.example.com: every server then gets an address like survival.mc.example.com by itself, with its own page and certificate, and players type the server's port with it. A free name comes from Playkeeper's names service: three days after the claim, once the service has reached the dashboard on port 8443, the first five servers get their own address, and until then (and for any further servers) players add the server's port to the name. Servers on connected machines join at that machine's IP address and each server's port. The IP address and its self-signed certificate keep working. Invite, map and pack links use the name once there is one. Opening the name in a browser, without a port, shows a public page for your servers: their status, how to join and the shared map's link, with player names only if you show them (Settings › Public page on each server). There you can add your own words, like the server's rules, and a Twitch or YouTube channel that visitors can watch, and your tools can post a status board to it through the API or MCP: a headline, whether you're live and when the next session starts, a few numbers and a checklist. A link to the page shows a picture of the server where it's shared. It uses ports 443 and 80 only while nothing else on the VPS uses or claims them.
The dashboard without a port: with Serve the dashboard on the standard HTTPS port (443) on, in Machine settings below the address, the dashboard opens at https://yourname.playkeeper.me or your own domain instead of …:8443. A new install turns it on when nothing uses port 443; an update leaves it off until you turn it on, and it can't be turned on while another program, a Docker container or a web server set to start with the VPS has port 443, which it names. Allow TCP 443 in your provider's firewall first. The address loses its port once a browser from outside the VPS has opened it there, which Machine settings checks from your browser (or asks you to open it once), so a firewall that drops port 443 never leaves you with an address that doesn't open. Signed in, the name opens the dashboard; for anyone else it shows your servers' public page with Sign in, or the sign-in page where customers sign in with Whop. Port 8443 keeps answering: it sends browsers that open a page there to the address without a port, and keeps serving the API, /mcp, Whop's webhook, the free address check and connected machines, so old links, bookmarks and tools keep working. Invite, map and pack links, AI agents' address, Discord's links, Whop's webhook and the messages customers get use the address without a port. Machine settings lists what outside Playkeeper keeps the old one, with the change each needs: with Sign in with Whop, add the new redirect URL on the Whop app's OAuth tab, beside the old one, which customers come back through until you do. The panel still runs without the right to open ports below 1024: the agent opens port 443 and hands it over, as for the public page. Free names used to end in .playkeeper.io: an install from before the move gets the same name under .playkeeper.me when it updates, and the old address keeps reaching it for two months.