Hytale server download fails with OAuth device flow – context deadline exceeded #25

New Issue

OVERLORD · 2026-02-05T16:39:33+03:00

OVERLORD commented

2026-02-05 16:39:33 +03:00

Originally created by @needkg on GitHub (Jan 17, 2026).

When starting the Hytale server using Pelican, the server fails during the download of server files after OAuth device authentication. Even after successful authentication, the downloader times out when trying to fetch the manifest from account-data.hytale.com.

Platform: x86_64
Copying start.sh template to /home/container...
Backup directory already exists.
Credentials file not found, running initial setup...
Downloading server files...
hytale-downloader is up to date (2026.01.09-49e5904)
 
════════════════════════════════════════════════════════════════
  NOTE: You must have purchased Hytale on the account you are using to authenticate.
════════════════════════════════════════════════════════════════
 
Please visit the following URL to authenticate:
https://oauth.accounts.hytale.com/oauth2/device/verify?user_code=xxxxxx
Or visit the following URL and enter the code:
https://oauth.accounts.hytale.com/oauth2/device/verify
Authorization code: xxxxxx
2026/01/17 05:12:55 deprecated: golang.org/x/oauth2: Transport.CancelRequest no longer does anything; use contexts
2026/01/17 05:12:55 error fetching manifest: could not get signed URL for manifest: could not get signed URL: Get "https://account-data.hytale.com/game-assets/version/release.json": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Error: Failed to download Hytale server files.
This may indicate:
  - You haven't purchased Hytale
  - Authentication credentials are invalid or expired
Removing invalid credential file...
pelican@Hytale ~ Server marked as offline...
[pelican Daemon]: ---------- Detected server process in a crashed state! ----------
[pelican Daemon]: Exit code: 1
[pelican Daemon]: Out of memory: false
[pelican Daemon]: Updating process configuration files...
[pelican Daemon]: Ensuring file permissions are set correctly, this could take a few seconds...```

Originally created by @needkg on GitHub (Jan 17, 2026). When starting the Hytale server using Pelican, the server fails during the download of server files after OAuth device authentication. Even after successful authentication, the downloader times out when trying to fetch the manifest from account-data.hytale.com. ``` [pelican Daemon]: Finished pulling Docker container image Platform: x86_64 Copying start.sh template to /home/container... Backup directory already exists. Credentials file not found, running initial setup... Downloading server files... hytale-downloader is up to date (2026.01.09-49e5904) ════════════════════════════════════════════════════════════════ NOTE: You must have purchased Hytale on the account you are using to authenticate. ════════════════════════════════════════════════════════════════ Please visit the following URL to authenticate: https://oauth.accounts.hytale.com/oauth2/device/verify?user_code=xxxxxx Or visit the following URL and enter the code: https://oauth.accounts.hytale.com/oauth2/device/verify Authorization code: xxxxxx 2026/01/17 05:12:55 deprecated: golang.org/x/oauth2: Transport.CancelRequest no longer does anything; use contexts 2026/01/17 05:12:55 error fetching manifest: could not get signed URL for manifest: could not get signed URL: Get "https://account-data.hytale.com/game-assets/version/release.json": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Error: Failed to download Hytale server files. This may indicate: - You haven't purchased Hytale - Authentication credentials are invalid or expired Removing invalid credential file... pelican@Hytale ~ Server marked as offline... [pelican Daemon]: ---------- Detected server process in a crashed state! ---------- [pelican Daemon]: Exit code: 1 [pelican Daemon]: Out of memory: false [pelican Daemon]: Updating process configuration files... [pelican Daemon]: Ensuring file permissions are set correctly, this could take a few seconds...```

OVERLORD closed this issue

2026-02-05 16:39:34 +03:00

OVERLORD commented

2026-02-05 16:39:36 +03:00

@MrLuckyGamer commented on GitHub (Jan 17, 2026):

Error: Failed to download Hytale server files.
This may indicate:
  - You haven't purchased Hytale
  - Authentication credentials are invalid or expired

Have you done these? also block out your auth codes in error messages.

@MrLuckyGamer commented on GitHub (Jan 17, 2026): ``` Error: Failed to download Hytale server files. This may indicate: - You haven't purchased Hytale - Authentication credentials are invalid or expired ``` Have you done these? also block out your auth codes in error messages.

OVERLORD commented

2026-02-05 16:39:37 +03:00

@needkg commented on GitHub (Jan 17, 2026):

Yes, I have already done that. I purchased the game on this account and have tried fully logging out and logging back in on the official website to refresh the credentials, but the error persists when attempting to download the server files.

@needkg commented on GitHub (Jan 17, 2026): Yes, I have already done that. I purchased the game on this account and have tried fully logging out and logging back in on the official website to refresh the credentials, but the error persists when attempting to download the server files.

OVERLORD commented

2026-02-05 16:39:38 +03:00

@NATroutter commented on GitHub (Jan 17, 2026):

This doesn't look like an egg issue to me. Most likely it's either a network problem, firewall blocking something, or you just took too long to authenticate.

What kind of system are you running this on and who's the provider?

Also, did you authenticate immediately when the link became available?

Was there any time between when the authentication website said the app is authenticated and when the error came up?

Try running the downloader directly on your host machine to see what's actually going on.

SSH into your host
Make a test folder somewhere like mkdir ~/hytale-test && cd ~/hytale-test
Download the Hytale downloader there hytale-downloader.zip
Make it executable chmod +x ./hytale-downloader-linux-amd64
Run it ./hytale-downloader-linux-amd64
Send me whatever output you get

That way we can figure out if the problem is with the egg setup or if it's something else on the system or network side.

@NATroutter commented on GitHub (Jan 17, 2026): This doesn't look like an egg issue to me. Most likely it's either a network problem, firewall blocking something, or you just took too long to authenticate. What kind of system are you running this on and who's the provider? Also, did you authenticate immediately when the link became available? Was there any time between when the authentication website said the app is authenticated and when the error came up? Try running the downloader directly on your host machine to see what's actually going on. 1. SSH into your host 2. Make a test folder somewhere like `mkdir ~/hytale-test && cd ~/hytale-test` 3. Download the Hytale downloader there [hytale-downloader.zip](https://downloader.hytale.com/hytale-downloader.zip) 4. Make it executable `chmod +x ./hytale-downloader-linux-amd64` 5. Run it `./hytale-downloader-linux-amd64` 6. Send me whatever output you get That way we can figure out if the problem is with the egg setup or if it's something else on the system or network side.

OVERLORD commented

2026-02-05 16:39:39 +03:00

@needkg commented on GitHub (Jan 17, 2026):

I’m currently running the following setup:

A dedicated server hosted at my home
Ubuntu 24.04
Pelican Panel running in Docker

Yes, I authenticated immediately after the link became available.
After completing the authentication on the website, it takes around 5 seconds for the error to appear.

I then SSHed into the host machine and ran the commands you suggested.
Running the downloader directly on the host works perfectly, and I was able to download the server without any issues. Here is the full output:

XXXXXXX@XXXXXXX:~/hytale-test$ ./hytale-downloader-linux-amd64
Please visit the following URL to authenticate:
https://oauth.accounts.hytale.com/oauth2/device/verify?user_code=XXXXXXX
Or visit the following URL and enter the code:
https://oauth.accounts.hytale.com/oauth2/device/verify
Authorization code: XXXXXXX
downloading latest ("release" patchline) to "2026.01.17-4b0f30090.zip"
[==================================================] 100.0% (1.4 GB / 1.4 GB)
validating checksum...
successfully downloaded "release" patchline (version 2026.01.17-4b0f30090)

@needkg commented on GitHub (Jan 17, 2026): I’m currently running the following setup: - A dedicated server hosted at my home - Ubuntu 24.04 - Pelican Panel running in Docker Yes, I authenticated immediately after the link became available. After completing the authentication on the website, it takes around 5 seconds for the error to appear. I then SSHed into the host machine and ran the commands you suggested. Running the downloader directly on the host works perfectly, and I was able to download the server without any issues. Here is the full output: ``` XXXXXXX@XXXXXXX:~/hytale-test$ ./hytale-downloader-linux-amd64 Please visit the following URL to authenticate: https://oauth.accounts.hytale.com/oauth2/device/verify?user_code=XXXXXXX Or visit the following URL and enter the code: https://oauth.accounts.hytale.com/oauth2/device/verify Authorization code: XXXXXXX downloading latest ("release" patchline) to "2026.01.17-4b0f30090.zip" [==================================================] 100.0% (1.4 GB / 1.4 GB) validating checksum... successfully downloaded "release" patchline (version 2026.01.17-4b0f30090) ```

OVERLORD commented

2026-02-05 16:39:40 +03:00

@NATroutter commented on GitHub (Jan 17, 2026):

After some research I managed to find this github issue on Pterodactyl's GitHub. It seems to be basically the same thing. Maybe this helps?

@NATroutter commented on GitHub (Jan 17, 2026): After some research I managed to find [this github issue](https://github.com/pterodactyl/panel/issues/4784) on Pterodactyl's GitHub. It seems to be basically the same thing. Maybe this helps?

OVERLORD commented

2026-02-05 16:39:41 +03:00

@NATroutter commented on GitHub (Jan 18, 2026):

If you need more help i'm happy to help 😄

@NATroutter commented on GitHub (Jan 18, 2026): If you need more help i'm happy to help 😄

OVERLORD commented

2026-02-05 16:39:42 +03:00

@needkg commented on GitHub (Jan 18, 2026):

You were absolutely right in pointing out issue #4784.
The problem was indeed a network configuration issue on my side, specifically within the Wings config.yml.

Root Cause

In my config.yml, the local gateway (192.168.1.1) was configured as the first entry under docker -> network -> dns. Because the Docker container runs in an isolated network, it was timing out when trying to resolve DNS through this local address. As a result, the container failed to fetch the Hytale manifest, triggering Client.Timeout errors, even though the host machine itself had normal internet access.

Resolution

I updated /etc/pelican/config.yml to use public DNS resolvers directly, bypassing the local gateway entirely:

docker:
  network:
    dns:
      - 1.1.1.1
      - 1.0.0.1

After fully restarting Pelican, the installation completed successfully.

Thank you very much for the help and for pointing me in the right direction.

@needkg commented on GitHub (Jan 18, 2026): You were absolutely right in pointing out issue **#4784**. The problem was indeed a network configuration issue on my side, specifically within the **Wings `config.yml`**. ## Root Cause In my `config.yml`, the local gateway (`192.168.1.1`) was configured as the first entry under `docker -> network -> dns`. Because the Docker container runs in an isolated network, it was timing out when trying to resolve DNS through this local address. As a result, the container failed to fetch the Hytale manifest, triggering `Client.Timeout` errors, even though the host machine itself had normal internet access. ## Resolution I updated `/etc/pelican/config.yml` to use public DNS resolvers directly, bypassing the local gateway entirely: ```yaml docker: network: dns: - 1.1.1.1 - 1.0.0.1 ``` After fully restarting Pelican, the installation completed successfully. Thank you very much for the help and for pointing me in the right direction.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/egg-hytale#25