The Network page, end to end

Your server's whole address book in one place — Ports, Subdomains, Internal Network, and Reverse Proxy — what each tab does and when to reach for it.

Every way in and out of your server lives on one page: Network. It has four tabs, and each answers a different question — what's my raw address? can I get a friendly name? how do my servers talk to each other privately? how do I put a real domain with HTTPS in front of a website? This guide is the map of all four and when to use which. Open Network from your server menu.

At a glance
You need Any Falix server
Plan All plans — every tab here works on free and premium
Time Ten minutes to read; each tab is a few clicks

The four tabs at a glance

Tab Answers SSL Deep guide
Ports "What's my public address?" No this page
Subdomains "Can people type a name instead of an IP?" No (name only) this page
Internal Network "How do my own servers talk privately?" n/a (private) Internal Network
Reverse Proxy "How do I get https://mysite.com with no port?" Yes, automatic Domains and HTTPS

🎯 Good to know: These are four different tools, not four steps. A Minecraft server usually needs only Subdomains; a website usually wants Reverse Proxy; a bot talking to its database wants Internal Network. Pick the one that fits the job.

Ports — your raw public address

The Ports tab lists your allocations: a public address and port that work the moment your app is listening, with zero setup (http://address:port, or address:port in a game client). One of them is your primary port, marked with a crown.

  • Add a port. Free servers get a small handful of allocations; premium gets many more. Adding one assigns the next available port automatically — there's no number to pick.
  • Label them. Each port takes a note and an icon so a four-port server doesn't become a guessing game. The panel even recognises common ones — Votifier, GeyserMC, Simple Voice Chat, Floodgate — and suggests the matching icon.
  • Make primary / delete. Any extra port can be promoted to primary or removed.

A usage bar shows how many of your allocations are in use, turning amber as you approach the limit.

💡 Tip: Whatever listens must bind host 0.0.0.0 on your SERVER_PORT, not localhost. If the raw address:port doesn't respond, the problem is almost always the bind address — see I can't reach my app.

Subdomains — a name people can type

The Subdomains tab turns 198.51.100.20 into words. There are two kinds:

Falix subdomains (free DNS). Pick a label and a suffix — falixsrv.me, falix.gg, falix.me, falix.dev, falix.app, or falix.pro — to get something like yourname.falixsrv.me. Free servers get a few, premium more; a usage bar tracks it. One is your primary, and you can Make primary, Edit, or Delete any of them.

  • Naming rules: 3–30 characters, lowercase letters, digits, and hyphens, no leading/trailing or double hyphens.
  • What it does and doesn't do: it points the name at your address. For a web app the port still shows in the URL and there's no SSL — for that, use Reverse Proxy. For Minecraft Java it's better than it sounds: a Falix subdomain gets an SRV record, so players join with just the name and no port.

Custom domains (a domain you own). Add a domain you own and the panel walks you through pointing its nameservers at Falix (ns1.falixnodes.net / ns2.falixnodes.net), with step-by-step guides for Cloudflare, Namecheap, GoDaddy, and Google. Once it verifies, Falix manages that domain's DNS for you. (This points a name at your server; to also get HTTPS with no port, put a Reverse Proxy on top.)

Internal Network — private server-to-server links

The Internal Network tab gives your server a private address like uuid.internal that only your other Falix servers can reach — nothing is exposed to the internet. It's the clean way to let a Discord bot talk to a database server, or a web app talk to a Redis cache, without opening a public port. Enable it, connect the servers as peers, and they can find each other by their internal addresses.

That's a topic of its own — the full walkthrough, including a bot ↔ Redis example, is in Internal Network deep dive.

Reverse Proxy — a real domain with automatic HTTPS

The Reverse Proxy tab is what makes a website look professional: a clean domain, no port in the URL, and HTTPS set up for you automatically. Choose a Falix domain (yourname.falix.org, instant) or your own custom domain (a quick DNS verification), point it at the port your app listens on, and the SSL status moves from pending to active on its own. Around five proxies per server.

The step-by-step — custom domains, SSL, managing proxies — lives in Domains and HTTPS, which is the proxy tutorial. This tab is where you'll do it.

Which tab do I actually need?

I want to… Use
Test a web app right now Ports (address:port)
Let Java players join by name, no port Subdomains (Falix subdomain, gets an SRV record)
Give my website a real https:// domain Reverse Proxy
Let my bot reach my database server privately Internal Network
Point a domain I own at a game server Subdomains → custom domain

Who can see and change this

The Network page needs the allocations permission. A sub-user with read can view your addresses; changing ports, subdomains, proxies, or internal networking needs the matching create/update permission. Everything here is per-server, and it all survives a reinstall — reinstalling only touches files, not your addresses. See sub-users for handing this out.

Troubleshooting

  • Subdomain or proxy name rejected — it broke the naming rules: 3–30 characters, lowercase letters, digits, hyphens, no double or edge hyphens, and it must be unique.
  • Name resolves but the app doesn't answer — the DNS is fine; your app isn't listening on that port bound to 0.0.0.0. Test the raw address:port first: I can't reach my app.
  • Custom domain stuck on pending — DNS hasn't propagated or the record is wrong. Re-check what the panel told you to add at your registrar and give it time.
  • "Internal networking not available on this node" — that server's node doesn't offer it; contact support or use a public port instead.

Next steps

Was this guide helpful?