Panel not reachable

1. Check that txAdmin startedCopy Anchor Link

Read the FXServer startup console. Start the artifact without +exec server.cfg; that argument bypasses the txAdmin startup path. Find the actual panel URL and port printed by the process.

2. Use the correct addressCopy Anchor Link

localhost only works from the machine running the process. From your laptop, use the remote host address or provider URL. The default panel port is TCP 40120; the game port is normally 30120.

If the port was changed, use the configured TXHOST_TXA_PORT. Set it before FXServer starts, not inside server.cfg.

3. Check binding and exposureCopy Anchor Link

On the server, check that the process is listening on the intended port. For Linux, a typical diagnostic is:

ss -ltnp | grep 40120

Use your configured port in place of 40120. Check the host firewall, provider firewall, and router forwarding where applicable. With containers, check both the internal listener and published host port.

4. Check host variablesCopy Anchor Link

A loopback-only TXHOST_INTERFACE is not reachable directly from another machine. An interface or port conflict can stop startup. TXHOST_TXA_URL changes the displayed URL; it does not create DNS, a reverse proxy, or a port mapping.

5. Separate proxy and origin failuresCopy Anchor Link

If using a custom hostname, compare the private/origin access path with the proxied one. Check DNS, TLS, and proxy routing without exposing the panel more widely than intended. Some CDNs do not proxy arbitrary panel ports.

If your game host owns those controls, send them the printed panel address and exact connection error.

Source: txAdmin upstream documentation.