Skip to main content
Out of the box your install lives on a Railway address like frontend-production-89ee.up.railway.app. If you own a domain, you can use something friendlier like rcon.yourclan.com instead. It takes about five minutes: one change in Railway, one at your domain provider, and two small edits so CRCON accepts the new address.
1

Add your domain in Railway

Open the frontend service, go to Settings, Networking, and click + Custom Domain. Type your domain and enter port 80, then click Add Domain.
Railway's Add Custom Domain form with a domain and port 80 filled in

Adding rcon.example.com on port 80

2

Copy the DNS records to your domain provider

Railway shows you exactly which records to create:
Railway's Configure DNS Records dialog showing a CNAME and TXT record to create

Railway tells you what to add at your domain provider

Log in wherever you manage your domain (Cloudflare, Namecheap, GoDaddy, …), find the DNS settings, and add the records exactly as shown. If your domain is on Cloudflare, the Connect button can even do it for you.That’s all for the plumbing: the secure padlock (HTTPS) is set up automatically. It usually goes live within a few minutes, sometimes up to an hour depending on your provider.
On Cloudflare with the orange cloud (proxy) turned on, also set the domain’s SSL/TLS mode to Full, or the page will loop endlessly.
3

Tell CRCON about the new address

CRCON only answers to addresses it knows. On the backend service, open the Variables tab and make two edits:
  1. Find DOMAINS and add your domain to the end of the list, after a comma. Don’t remove anything that’s already there. For example:
  2. Find RCONWEB_EXTERNAL_ADDRESS and replace its value with your domain, for example rcon.yourclan.com.
Then make the same RCONWEB_EXTERNAL_ADDRESS change on the frontend service’s Variables tab.
Add to DOMAINS, never replace it. The entries already in the list keep the install working; removing them breaks it.
4

Redeploy and log in

Redeploy the backend, frontend, and supervisor services (open each one, then the three-dot menu on its latest deployment, then Redeploy). Once they’re back online, log in at your new address. Your old Railway address keeps working too, as a backup.

​
A domain for the scoreboard too

Want stats.yourclan.com for the public scoreboard? Repeat step 1 and 2 with that domain, entering port 81 instead. Nothing else needs changing; the scoreboard has no login.

​
One login across several game servers

Running more than one game server? Give each frontend its own subdomain of the same domain (rcon1.yourclan.com, rcon2.yourclan.com), then add two variables on every backend: Also add each subdomain to its own backend’s DOMAINS (step 3 above). Now logging in once logs you in everywhere. This only works with your own domain, which is one of the best reasons to set one up.