Most Likely Causes (and Fixes)
1. ❗ Encryption Mismatch (Most Common)
ClassicUO often expects
no encryption, while ServUO may still have it enabled.
✅ Fix (ServUO side)
In your Scripts/Misc/Encryption.cs (or config depending on your fork):
public static bool LoginEncryption = false;
public static bool GameEncryption = false;
Or in server.cfg:
Encryption=false
Then restart the server.
2. ❗ Wrong Client Version Handling
ServUO might not recognize or properly handle
7.0.114.2.
✅ Fix options:
- Enable client version ignoring
- Or explicitly allow your version
Check:
ClientVersion = new ClientVersion("7.0.114.2");
Or in config:
ClientVersion=7.0.114.2
Or temporarily:
IgnoreClientVersion=true
3. ❗ IP / Binding Issue (VERY Common on Windows Server)
You log in fine, but when switching to the game server, it tries to connect to a
bad internal IP.
This EXACT symptom usually = wrong IP in server config
✅ Fix:
Check server.cfg:
Address=YOUR_PUBLIC_IP
OR for local testing:
Address=127.0.0.1
Also check:
GameServerPort=2593
4. ❗ Firewall / Port Block
Login works (2593), but game port might be blocked or misrouted.
✅ Fix:
- Open port 2593 TCP
- Ensure Windows Server firewall allows it
- If using NAT/VPS → port forward correctly
5. ❗ ClassicUO Profile Config
ClassicUO might be overriding something.
✅ Check:
- client.exe path is correct
- IP matches your server
- Try disabling plugins
6. ❗ Packet/Expansion Mismatch
If ServUO is set to a different expansion than the client expects:
✅ Fix:
Match expansion in ServUO:
Core.AOS = true;
Core.SE = true;
Core.ML = true;
Core.SA = true;
Core.TOL = true;
Quick Isolation Test (Do This First)
- Set:
Address=127.0.0.1
Encryption=false
IgnoreClientVersion=true
- Connect locally with ClassicUO
If it works → problem is
network/IP
If it still fails → problem is
encryption/version
Bonus: Known ClassicUO + ServUO Quirk
Some builds of ClassicUO expect:
- no encryption
- proper seed handling
If still broken, try a slightly older client:
- 7.0.86.x (very stable with ServUO)
