“FXServer is not responding” means txAdmin’s monitor cannot obtain the expected response from the game server. Check whether FXServer is running, listening at the configured endpoint and able to finish startup before changing firewall or resource settings.
Preserve the first failure
Save the monitor message, timestamp and the first FXServer error. Back up the active profile and server.cfg. Avoid repeated restarts that overwrite useful evidence or repeatedly interrupt database work.
1. Check the process and startup context
Confirm that the intended FXServer process is running and that txAdmin uses the correct server-data path and configuration. For txAdmin setup, follow the official bundled txAdmin procedure. It is not enabled by adding start txAdmin as an ordinary resource.
If the process exits, investigate its startup error, runtime dependencies or crash record. If it stays running but stops progressing at a resource, reproduce with that resource and its dependencies on staging.
2. Compare actual endpoints
Check the TCP and UDP bindings in server.cfg against the host’s allocated ports and the monitored endpoint. This common example uses one game port for both protocols:
endpoint_add_tcp "0.0.0.0:30120"
endpoint_add_udp "0.0.0.0:30120"Use your real allocation. Keep the txAdmin web-management port distinct from the game endpoint. Check the operating system’s listening sockets and whether another process already owns the port.
3. Test the appropriate network path
A monitor connection refused error suggests no listener at the requested address/port. A timeout can involve blocked access or a stalled process. An HTTP 404 can indicate that the request reached the wrong service or path.
Check local reachability before changing public NAT or DDoS settings. Then verify the game’s required TCP/UDP traffic from a real client. A successful TCP-only probe does not establish that UDP game traffic works.
4. Isolate startup work safely
On staging, restore the last known working configuration and add changed resources one at a time with their dependencies. Use logs and the profiler to investigate a resource that stalls startup. Do not disable every dependency on the live server.
If security software reports a block, inspect that specific detection and follow the official vendor/support procedure. A blanket FXServer antivirus exclusion is not a normal troubleshooting step.
Confirm recovery
Restart once with the corrected configuration, confirm healthy monitoring and join with a client. Check resource errors, persistence and management access. Restore the previous configuration if the change creates a new failure.