starred/egg-hytale
1
0
Fork 0
mirror of https://github.com/NATroutter/egg-hytale.git synced 2026-03-01 11:21:13 +03:00
Code Issues Packages Projects Releases Wiki Activity

auth encrypted storage doesnt work #24

New Issue
Closed
opened 2026-02-05 16:39:22 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-05 16:39:22 +03:00
Owner
Copy Link

Originally created by @Prefix on GitHub (Jan 15, 2026).

might be requiring more packages on docker os level

Originally created by @Prefix on GitHub (Jan 15, 2026). might be requiring more packages on docker os level
OVERLORD commented 2026-02-05 16:39:25 +03:00
Author
Owner
Copy Link

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

Works fine for me

@MrLuckyGamer commented on GitHub (Jan 15, 2026): Works fine for me
OVERLORD commented 2026-02-05 16:39:26 +03:00
Author
Owner
Copy Link

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

might be requiring more packages on docker os level

It's kind of impossible to diagnose any issues without any logs, etc.
I'm assuming that you are trying to use the command "/auth persistence Encrypted" and it throws an error.

>....[2026/01/15 08:54:02   WARN]                   [HardwareUtil] Failed to get Hardware UUID
java.lang.RuntimeException: Failed to get hardware UUID for Linux - all methods failed
............
..................
......................
[2026/01/15 08:54:02   WARN]   [EncryptedAuthCredentialStore] Cannot derive encryption key - encrypted storage will not persist credentials

If it's like that, this is not an egg/image issue, it's a pelican/pterodactyl issue, and I can't do anything about it, but anyway you don't even need to use the command because the egg has its own system for managing credentials..

@NATroutter commented on GitHub (Jan 15, 2026): > might be requiring more packages on docker os level It's kind of impossible to diagnose any issues without any logs, etc. I'm assuming that you are trying to use the command "/auth persistence Encrypted" and it throws an error. ``` >....[2026/01/15 08:54:02 WARN] [HardwareUtil] Failed to get Hardware UUID java.lang.RuntimeException: Failed to get hardware UUID for Linux - all methods failed ............ .................. ...................... [2026/01/15 08:54:02 WARN] [EncryptedAuthCredentialStore] Cannot derive encryption key - encrypted storage will not persist credentials ``` If it's like that, this is not an egg/image issue, it's a pelican/pterodactyl issue, and I can't do anything about it, but anyway you don't even need to use the command because the egg has its own system for managing credentials..
OVERLORD commented 2026-02-05 16:39:27 +03:00
Author
Owner
Copy Link

@Mwubi01 commented on GitHub (Jan 16, 2026):

might be requiring more packages on docker os level

If you use Pterodactyl, you have to assign a Mount. Pterodactyl cant read the Linux Machine ID directly.

  1. On your Pterodactyl host server do:
# Create a persistent machine-id for this server
mkdir -p /srv/pterodactyl/machine-ids
uuidgen | tr -d '-' > /srv/pterodactyl/machine-ids/YOUR_SERVER_NAME

  1. After that open the config:
    nano /etc/pterodactyl/config.yml

  2. Find allowed_mounts section

allowed_mounts[]

# >>> Change to following and save

allowed_mounts:
  - /srv/pterodactyl/machine-ids

  1. Restart wings
    systemctl restart wings

  2. Now go to Pterodactyl Panel > Admin > Mounts > Create New > fill out:

Name: hytale-machine-id (For Example)
Description: Machine ID for Hytale encrypted auth persistence
Source: /srv/pterodactyl/machine-ids/YOUR_SERVER_NAME
Target: /etc/machine-id
Read Only: False
User Mountable: False

Save

  1. Go to your created mount and open it.
  • Add your Node
  • Add your Hytale Egg

  1. In the Admin Panel go to > Servers > Hytale Server > Mounts > Press '+' to add the newly created Mount.

  2. Restart your Server and Re-Auth.

Should work now. At least for me, hope this helps.

Ps: If this isnt done by the User, the managing system of the egg for credentials doesnt work. You still have to Re-Auth every restart. Well, at least i had to.

@Mwubi01 commented on GitHub (Jan 16, 2026): > might be requiring more packages on docker os level If you use **Pterodactyl**, you have to **assign a Mount**. Pterodactyl cant read the Linux Machine ID directly. 1. On your Pterodactyl host server do: ``` # Create a persistent machine-id for this server mkdir -p /srv/pterodactyl/machine-ids uuidgen | tr -d '-' > /srv/pterodactyl/machine-ids/YOUR_SERVER_NAME ``` 2. After that open the config: ` nano /etc/pterodactyl/config.yml ` 3. Find allowed_mounts section ``` allowed_mounts[] # >>> Change to following and save allowed_mounts: - /srv/pterodactyl/machine-ids ``` 4. Restart wings ` systemctl restart wings ` 5. Now go to Pterodactyl Panel > Admin > Mounts > Create New > fill out: ``` Name: hytale-machine-id (For Example) Description: Machine ID for Hytale encrypted auth persistence Source: /srv/pterodactyl/machine-ids/YOUR_SERVER_NAME Target: /etc/machine-id Read Only: False User Mountable: False ``` Save 6. Go to your created mount and open it. - Add your Node - Add your Hytale Egg 7. In the Admin Panel go to > Servers > Hytale Server > Mounts > Press '+' to add the newly created Mount. 8. Restart your Server and Re-Auth. Should work now. At least for me, hope this helps. Ps: If this isnt done by the User, the managing system of the egg for credentials doesnt work. You still have to Re-Auth every restart. Well, at least i had to.
OVERLORD commented 2026-02-05 16:39:29 +03:00
Author
Owner
Copy Link

@Fundryi commented on GitHub (Jan 16, 2026):

might be requiring more packages on docker os level

If you use Pterodactyl, you have to assign a Mount. Pterodactyl cant read the Linux Machine ID directly.

1. On your Pterodactyl host server do:

# Create a persistent machine-id for this server
mkdir -p /srv/pterodactyl/machine-ids
uuidgen | tr -d '-' > /srv/pterodactyl/machine-ids/YOUR_SERVER_NAME

2. After that open the config:
   `nano /etc/pterodactyl/config.yml`

3. Find allowed_mounts section

allowed_mounts[]

# >>> Change to following and save

allowed_mounts:
  - /srv/pterodactyl/machine-ids

4. Restart wings
   `systemctl restart wings`

5. Now go to Pterodactyl Panel > Admin > Mounts > Create New > fill out:

Name: hytale-machine-id (For Example)
Description: Machine ID for Hytale encrypted auth persistence
Source: /srv/pterodactyl/machine-ids/YOUR_SERVER_NAME
Target: /etc/machine-id
Read Only: False
User Mountable: False

Save

6. Go to your created mount and open it.


* Add your Node

* Add your Hytale Egg


7. In the Admin Panel go to > Servers > Hytale Server > Mounts > Press '+' to add the newly created Mount.

8. Restart your Server and Re-Auth.

Should work now. At least for me, hope this helps.

Ps: If this isnt done by the User, the managing system of the egg for credentials doesnt work. You still have to Re-Auth every restart. Well, at least i had to.

This worked perfectly, thank you so much.
Just gotta make sure after you did this to use "/auth logout" and then "/auth login device" and do the auth one more time, after that I can now restart without any issues as many times as I want :)
If you delete/change the .hytale-auth-tokens.json, you will have to-do the above command again.

@Fundryi commented on GitHub (Jan 16, 2026): > > might be requiring more packages on docker os level > > If you use **Pterodactyl**, you have to **assign a Mount**. Pterodactyl cant read the Linux Machine ID directly. > > 1. On your Pterodactyl host server do: > > > ``` > # Create a persistent machine-id for this server > mkdir -p /srv/pterodactyl/machine-ids > uuidgen | tr -d '-' > /srv/pterodactyl/machine-ids/YOUR_SERVER_NAME > ``` > > 2. After that open the config: > `nano /etc/pterodactyl/config.yml` > > 3. Find allowed_mounts section > > > ``` > allowed_mounts[] > > # >>> Change to following and save > > allowed_mounts: > - /srv/pterodactyl/machine-ids > ``` > > 4. Restart wings > `systemctl restart wings` > > 5. Now go to Pterodactyl Panel > Admin > Mounts > Create New > fill out: > > > ``` > Name: hytale-machine-id (For Example) > Description: Machine ID for Hytale encrypted auth persistence > Source: /srv/pterodactyl/machine-ids/YOUR_SERVER_NAME > Target: /etc/machine-id > Read Only: False > User Mountable: False > ``` > > Save > > 6. Go to your created mount and open it. > > > * Add your Node > > * Add your Hytale Egg > > > 7. In the Admin Panel go to > Servers > Hytale Server > Mounts > Press '+' to add the newly created Mount. > > 8. Restart your Server and Re-Auth. > > > Should work now. At least for me, hope this helps. > > Ps: If this isnt done by the User, the managing system of the egg for credentials doesnt work. You still have to Re-Auth every restart. Well, at least i had to. This worked perfectly, thank you so much. Just gotta make sure after you did this to use "/auth logout" and then "/auth login device" and do the auth one more time, after that I can now restart without any issues as many times as I want :) If you delete/change the .hytale-auth-tokens.json, you will have to-do the above command again.
OVERLORD commented 2026-02-05 16:39:30 +03:00
Author
Owner
Copy Link

@Mwubi01 commented on GitHub (Jan 16, 2026):

Glad to hear. I hope someone makes a great Tutorial for it, because a lot of people have this issue. And i think most won't stumble across this here. 😩

@Mwubi01 commented on GitHub (Jan 16, 2026): Glad to hear. I hope someone makes a great Tutorial for it, because a lot of people have this issue. And i think most won't stumble across this here. 😩
OVERLORD commented 2026-02-05 16:39:31 +03:00
Author
Owner
Copy Link

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

Using the Hytale authentication system /auth is currently useless with this egg because the egg is handling the authentication and storing the credentials. Even if you enabled the hardware ID and toggled the persistent authentication on /auth persistence Encrypted, the server won't use it because the authentication is being overridden by the egg's own system.

If you are still having issues with the authentication and have to re-authenticate every time, you are using a very old version of the egg and should update it. Check the Updating the Egg section in the README.

@NATroutter commented on GitHub (Jan 16, 2026): Using the Hytale authentication system `/auth` is currently useless with this egg because the egg is handling the authentication and storing the credentials. Even if you enabled the hardware ID and toggled the persistent authentication on `/auth persistence Encrypted`, the server won't use it because the authentication is being overridden by the egg's own system. If you are still having issues with the authentication and have to re-authenticate every time, you are using a very old version of the egg and should update it. Check the [Updating the Egg](https://github.com/NATroutter/egg-hytale#updating-the-egg) section in the README.
OVERLORD commented 2026-02-05 16:39:32 +03:00
Author
Owner
Copy Link

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

fixed in latest wings version

@Prefix commented on GitHub (Jan 17, 2026): fixed in latest wings version
OVERLORD commented 2026-02-05 16:39:32 +03:00
Author
Owner
Copy Link

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

@NATroutter

@Prefix commented on GitHub (Jan 17, 2026): @NATroutter
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/egg-hytale#24
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?