WAN IP (Direct Connect)

Purpose: Connects directly to your server using your router's Public IP address. This is the "raw" way to connect without any domain naming services involved.

Use Case: Ideal for temporary testing or users that don't own a domain. It's the quickest and easiest to set up but requires sharing your Public IP with other users.

Downside: If your ISP uses a dynamic Public IP address for your internet, your server connectivity will break any time the Public IP changes. Requires port forwarding.

Port Forwarding: Port numbers 28000, 28001, 28002, 28003 all need to forwarded on the Router/Firewall of the computer hosting the IRCP if you want it to be accessible over the internet.

Example One: The literal words 'location.hostname' automatically detects the Public IP address of where the control panel is served from then uses it to connect to the backend.
Backend Listener = 'http://location.hostname:28001'
Backend Logs = 'http://location.hostname:28002'
Backend Updates = 'http://location.hostname:28003'

Example Two: '172.16.10.69' Hardcoded Public IP address. Only usefull if the control panel webpage is served from a different internet connection than the backend servers.
Backend Listener = 'http://172.16.10.69:28001'
Backend Logs = 'http://172.16.10.69:28002'
Backend Updates = 'http://172.16.10.69:28003'

Base Domain

Purpose: Uses a root domain (e.g. yourcustomdomain.com) to point back to your network and server. This masks your IP address behind a memorable name.

Use Case: Best for community owners who want a professional look or group branding. It allows you to change the underlying network IP address without users ever having to change the way they connect. For users who prefer to keep their Public IP address concealed and less accessible.

Downside: Requires port forwarding, ownership of a public domain name and a moderate understanding of networking and domains.

Port Forwarding: Port numbers 28000, 28001, 28002, 28003 all need to forwarded on the Router/Firewall of the computer hosting the IRCP if you want it to be accessible over the internet.

Example: A base/root domain name is used while server port numbers are still defined.
Backend Listener = 'http://yourcustomdomain.com:28001'
Backend Logs = 'http://yourcustomdomain.com:28002'
Backend Updates = 'http://yourcustomdomain.com:28003'

Fully Qualified Domain Name (FQDN)

Purpose: Uses sub-domain prefixes (e.g. controlpanel.yourcustomdomain.com) combined with a reverse proxy like NGINX or Cloudflare to point traffic directly to your server.

Use Case: The industry standard. For users who wish to have their control panel fully accessible through domain resolution and bypass port configuration. For users who prefer to keep their Public IP address concealed and less accessible.

Downside: Requires the use of a locally or externally hosted proxy. A slightly advanced level of networking knowledge is advantageous.

Benefit: Essential for SSL certificates, encrypted protocols, professional branding, and a better secured networking ecosystem.

Example: Unique sub-domains are used to define the location of each backend server. No port numbers need to be forwarded with this method.
Backend Listener = 'https://listener.yourcustomdomain.com'
Backend Logs = 'https://logs.yourcustomdomain.com'
Backend Updates = 'https://updates.yourcustomdomain.com'