UO Server Troubleshooting Guide

Having trouble with your UO server status or connection? This comprehensive guide covers everything from TCP networking basics to emulator-specific configurations.

How Server Status Checking Works

Our system checks your UO server status using TCP socket connections on your specified port. Here's what happens:

  1. TCP Connection: We attempt to establish a socket connection to your server's IP and port
  2. Status Request: We send a lightweight status packet to request basic server information
  3. Response Processing: Your server responds with player count, server name, and status data
  4. Connection Close: The connection is immediately closed to minimize server load
Frequency: Status checks occur approximately once per hour to provide accurate data while being respectful of your server resources.

Whitelist Our Monitoring IP

Add our monitoring server IP to your firewall whitelist:

Status Check IP: 130.162.162.237

This ensures our lightweight status checks can reach your server.

Proxy Server Considerations

If you're using a proxy or DDoS protection service:

  • Add our monitoring IP to bypass rules
  • Check that status packet forwarding is enabled
Query Frequency & Debug Mode

Our system performs one lightweight query per hour to check your server status. However, during debugging sessions or troubleshooting periods, you might notice slightly more frequent queries as we verify connectivity issues. Don't worry - we're not hammering your server! 🔧

Debug Mode: When investigating connection issues, we may perform up to 3-5 additional queries within a 10-minute window to pinpoint the problem.

Default Status: ENABLED - RunUO works automatically unless manually disabled.
If showing "No Data", check these files:
  1. Server/Network/PacketHandlers.cs - Ensure 0x7F handler isn't commented out
  2. Scripts/ folder - Check if you have any custom admin scripts that might block monitoring
  3. Scripts/Misc/ServerList.cs - Verify external IP configuration
Quick Fix: If files look correct, just restart server and whitelist 130.162.162.237

Same Core as RunUO - Plus additional anti-cheat features that may affect monitoring.
Check same files as RunUO, plus:
  1. Server/Network/PacketHandlers.cs - 0x7F handler enabled
  2. Scripts/ folder - Check for custom admin scripts that might block queries
  3. Enhanced Security Settings - Version-specific anti-cheat might block external monitoring
ServUO Tip: Check for additional security scripts that might block 130.162.162.237

Default Status: ENABLED - ModernUO is a RunUO fork, so status polling works by default.
Different file structure - check JSON configs:
  1. Data/Configuration/network.json - EnableStatusQueries: true
  2. Data/Configuration/server.json - Check security settings
  3. Enhanced Security - Modern security features might block external monitoring
JSON Example: {"NetworkSettings": {"EnableStatusQueries": true, "BlockExternalMonitoring": false}}

sphere.ini Configuration

To enable status polling on Sphere servers, you need to modify your sphere.ini file:

Required Settings:
CUOStatus=1
 UOGStatus=1
Step-by-Step Instructions:
  1. Open your sphere.ini file
  2. Locate the status settings section
  3. Set CUOStatus=1
  4. Set UOGStatus=1
  5. Save the file and restart your server
What These Settings Do:
  • CUOStatus: Enables ClassicUO client status reporting
  • UOGStatus: Enables UO Gateway status reporting
  • Both settings allow external status queries
Pro Tip: After enabling these settings, restart your Sphere server completely to ensure the changes take effect.

uox.ini Configuration

To enable status polling on UOX3 servers, you need to modify your uox.ini file:

Required Settings:
UOGENABLED=1
 FREESHARDSERVERPOLL=1
Step-by-Step Instructions:
  1. Open your uox.ini file
  2. Find the server settings section
  3. Set UOGENABLED=1
  4. Set FREESHARDSERVERPOLL=1
  5. Save and restart your UOX3 server
What These Settings Enable:
  • UOGENABLED: Activates UO Gateway functionality
  • FREESHARDSERVERPOLL: Allows external server polling
  • Enables real-time status reporting
Important: UOX3 requires both settings to be enabled for proper status reporting functionality.

Default Status: DISABLED - POL core doesn't include status polling. You need to add scripts manually.
Required Script Package

POL requires the ModernDistro serverlist hook package for status monitoring:

Installation Steps:
  1. Download the serverlist_hook package
  2. Copy to your POL packages directory
  3. Restart POL server
  4. Test with external polling
Requirements:
  • POL Version: 100.0.0 or newer recommended
  • Script Support: ModernDistro package required
  • Manual Setup: Not enabled by default
Pro Tip: Once installed, the script handles 0xF1 status packets automatically - no additional configuration needed!

Quick Diagnostic Checklist
  • Server is running and accessible
  • Correct IP address and port configured
  • Firewall allows incoming connections
  • Status polling enabled in emulator
  • No network proxy blocking TCP traffic
Get Help

If you've followed all the steps above and still can't get your server status working, we're here to help!

Contact Support

Include your server IP, port, and emulator type for faster assistance.