drewwales

Initiate
ServUO Version
Publish 57
Ultima Expansion
Endless Journey
So I'm setting up my server for external connections, but it gets stuck on verifying account and nothing shows in the console

I know the port forwarding is working as port is closed I open servUO and boom port shows as open
My console shows its listening to the following

Console:
19:56:01 Listening: 192.168.1.5:2593
19:56:01 Listening: 169.254.107.70:2593
19:56:01 Listening: 169.254.250.221:2593
19:56:01 Listening: 169.254.228.100:2593
19:56:01 Listening: 127.0.0.1:2593

my server.cfg shows the following


xxx to hide IP:
# The displayed name of the shard
Name=ServUO

# The internal IP address to listen on.
# You can leave this value as default to listen to all available IP's.
@Listen=185.8.94.xxx

# The public IP address to broadcast with the server list packet.
# If running from home, you can leave this value as default and connect locally.
# If your server is behind a DDoS shield provider, use the IP they assigned to you.
@Address=185.8.94.xxx //also tried keeping this at 127.0.0.1

# The Port to bind the Listener to.
# Default: 2593
@Port=2593

tried with windows firewall on and off. still no luck... am I missing something?
 
Remove the @ symbol from those lines. It's not setting up Address when @ is there :)

did that.

says
20:42:08 Listener Failed: 185.8.94.102:2593 (Unavailable)

tried with my 192.168.1.5 as well and still nothing

php test environment will connect to the server and show its online. So stumped why people cant connect.
 
Last edited:
Only Address needs to be public ip that fails too?
So you leave the the @Listen= on default and set Address to public.
 
Only Address needs to be public ip that fails too?
So you leave the the @Listen= on default and set Address to public.
so server.cfg is now

server.cfg:
# The displayed name of the shard
Name=ServUO

# The internal IP address to listen on.
# You can leave this value as default to listen to all available IP's.
@Listen=0.0.0.0

# The public IP address to broadcast with the server list packet.
# If running from home, you can leave this value as default and connect locally.
# If your server is behind a DDoS shield provider, use the IP they assigned to you.
Address=185.8.94.102

# The Port to bind the Listener to.
# Default: 2593
Port=2593

still no luck.

But with a php test enviroment (web based status page) it shows in the console. but my brother can not login just hangs on verifying account and nothing shows in console for it.

PHP test enviroment:
21:06:26 Listening: 192.168.1.5:2593
21:06:26 Listening: 169.254.107.70:2593
21:06:26 Listening: 169.254.250.221:2593
21:06:26 Listening: 169.254.228.100:2593
21:06:26 Listening: 127.0.0.1:2593
21:06:26 ----------------------------------------------------------------------
21:06:50 Client: 3.66.233.20: Connected. [1 Online]
21:06:50 Client: 3.66.233.20: Disconnected. [0 Online]

 
and you forward TCP connections to your servuo computer on port 2593? Firewall is allowing this?
Hmm... ok so PHP connects so this part is probably correct.
 
I am having the same issue. I can connect locally but outside if my internet it connects says connected, I select the server, the credentials are valid then kicks me. Port forwarding is setup because ModernUO has no issues. I was told once that ServUO is outdated and doesn't support the current clients so I downloaded and old one and pointed the data path to it but it still has the same issue.
 
I'm wondering if this is a servUO setup error?

as canyouseeme.org shows

Success: I can see your service on 185.8.94.102 on port (2593)

and when you run the code in the following link it shows in the servUO console

ServUO server status Sandbox PHP

sevUO:
14:45:48 Client: 3.66.233.20: Connected. [1 Online]
14:45:49 Client: 3.66.233.20: Disconnected. [0 Online]
 
Nmap shows the state as filtered and not open. Filtered usually means firewall. Firewall could be the firewall on your router or the built in firewall on on the OS hosting ServUO. All that said, it could be ServUO 57.4. There were a lot of changes made in 57.4 to prevent DDOS attacks. I experienced the same issue of not being able to connect over the network on 57.4 and reverted back to 57.3. I tried attaching a copy of 57.3 for you to test, but the attachment was too large to upload.

nmap results:

C:\Windows\System32>nmap -sS -P0 -p2593 185.8.94.102
Starting Nmap 7.95 ( Nmap: the Network Mapper - Free Security Scanner ) at 2025-06-12 03:09 Central Daylight Time
Nmap scan report for 185.8.94.102
Host is up.

PORT STATE SERVICE
2593/tcp filtered mns-mail

Nmap done: 1 IP address (1 host up) scanned in 2.14 seconds
 
Nmap shows the state as filtered and not open. Filtered usually means firewall. Firewall could be the firewall on your router or the built in firewall on on the OS hosting ServUO. All that said, it could be ServUO 57.4. There were a lot of changes made in 57.4 to prevent DDOS attacks. I experienced the same issue of not being able to connect over the network on 57.4 and reverted back to 57.3. I tried attaching a copy of 57.3 for you to test, but the attachment was too large to upload.

nmap results:

C:\Windows\System32>nmap -sS -P0 -p2593 185.8.94.102
Starting Nmap 7.95 ( Nmap: the Network Mapper - Free Security Scanner ) at 2025-06-12 03:09 Central Daylight Time
Nmap scan report for 185.8.94.102
Host is up.

PORT STATE SERVICE
2593/tcp filtered mns-mail

Nmap done: 1 IP address (1 host up) scanned in 2.14 seconds


I've got the ports open in the router firewall and on windows firewall. Canyouseeme.org shows them as open.

Would there be anything else on the router I need to lookout for?
 

Active Shards

Donations

Total amount
$5.00
Goal
$500.00
Back