Which port does a Hytale server use?
The dedicated server uses UDP port 5520 by default. A custom port can be selected with the server bind option, but the server, firewall and router must use matching values.
Configure the Hytale UDP port in your firewall and router with instructions adapted to where the server runs. Generate the exact commands, values and verification checklist without changing anything automatically.
The assistant can generate firewall commands, router notes, and diagnostic steps, but a web page cannot reliably test whether a UDP game port is reachable from the public internet. A successful local command only proves that the rule exists or that a process is listening on that machine.
Public reachability also depends on router forwarding, the correct private IP, hosting-panel rules, upstream firewalls, CGNAT, double NAT, and whether the server process is actually running.
Open only the protocol and port your server needs. Avoid broad rules that expose every port or trust every service when a specific UDP rule is enough. Keep remote administration ports separate from the game port.
After changing network rules, document what changed and how to remove it. If you use a VPS or managed host, check both the operating-system firewall and the provider firewall because either layer can block traffic.
The default dedicated server port is UDP 5520. If the server uses a custom bind port, use that same internal port in the operating-system firewall and router rule.
Hytale game traffic uses QUIC over UDP. The official server manual states that TCP forwarding is not required for the dedicated server port.
Usually no home-router forwarding is needed. You may still need an operating-system firewall rule and a second UDP rule in the VPS provider firewall or security group.
Run ipconfig on Windows or ip route on Linux. You can paste the output into the helper and HyTools will try to extract the likely private IPv4 and gateway locally in your browser.
Common causes include a router rule pointing to an old local IP, UDP being configured as TCP, another firewall at the provider, NAT loopback during testing, double NAT or CGNAT from the internet provider.
Not reliably. Browsers cannot make an arbitrary QUIC or UDP connection to your server, and many public port checkers test TCP only. Keep the server running and test from another network.
No. HyTools only generates commands, router values and a checklist. You decide what to apply, and all network data entered in the assistant stays in the browser.
Ask the internet provider for a public IPv4 address, resolve double NAT, use a supported virtual network for a private group, or move a persistent public server to a VPS or managed host.