mirror of
https://github.com/NATroutter/egg-hytale.git
synced 2026-03-01 11:21:13 +03:00
Unable to connect to hytale server- handshake canceled #35
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @imstillalive66 on GitHub (Jan 25, 2026).
I'm unable to connect to this hytale server once its up and running in pterodactyl.
receive error: connection handshake was canceled due to the configured timeout of 00:00:10 seconds elapsing
The auth is completed, server is running with no errors, and ports are open but it doesnt seem like traffic is even making it to this specific pterodactyl game server.
troubleshooting steps:
-nothing happens in the logs when trying to connect.
-initially used custom ports but tried opening the ports listed (5520, 5521) and assigned to hytale server with the same outcome.
-i have other games besides hytale running on this specific node that connect just fine so im certain the ports opened are working.
did I miss something in the initial setup?
@NATroutter commented on GitHub (Jan 25, 2026):
its an authentication issue check the server options and tell be what do you have on option called "Use Persistent Authentication" and "Auth Mode"
@imstillalive66 commented on GitHub (Jan 25, 2026):
current settings:
USE PERSISTENT AUTHENTICATION: DISABLED
AUTH MODE: AUTHENTICATED
@NATroutter commented on GitHub (Jan 25, 2026):
when you have "USE PERSISTENT AUTHENTICATION: DISABLED" you need to use hytales own authnetication system
run this commands on the console when server has started
@imstillalive66 commented on GitHub (Jan 25, 2026):
i had done the /auth login device previously but not the /auth persistence Encrypted.
ran that step, /auth status still shows authenticated and still receiving the same error when trying to connect to the server.
@FeedTheChunk commented on GitHub (Jan 25, 2026):
This may or may not be relevant but I had a similar issue after turning on Whitelist.
For whatever reason when I would add my username to the whitelist it didn't pull the correct UUID. I had to edit the whitelist json file and add the correct UUID for my username.
@imstillalive66 commented on GitHub (Jan 25, 2026):
my whitelist shows disabled but just for kicks i tried to enable it and set my uuid with no change in the outcome.
@imstillalive66 commented on GitHub (Jan 25, 2026):
while trying to troubleshoot I've noticed that upon fresh setup of the server, it prompts to authenticate before it'll download the server files.
Once completed and running, it prompts again for authentication using the /auth login method.
is it expected to try to authenticate twice this way? could there be a conflict?
@NATroutter commented on GitHub (Jan 25, 2026):
Yeah it prompts for authentication for the download of the server files, that's normal