Hytale Server Setup & Authentication Guide Print

This guide walks you through provisioning a Hytale server and completing interactive device authentication using the GlassMC Pterodactyl egg. Follow the steps in order. Do not skip steps.

Overview (Read First)

Make sure you are using the latest version of Wings. Update your wings server or Authentication will have to be manually executed every time the server starts.

Hytale Early Access servers currently require interactive device authentication.
On a fresh server, authentication must be completed once before the server can run normally.

To handle this, setup follows a three-phase bootstrap flow:

1. Offline bootstrap (initial startup)

2. Interactive device authentication

3. Authenticated operation

This is expected behavior under the current 100-session non-entitled model.

Requirements

Before you begin, ensure you have:

• Pterodactyl Panel (PTDL_v2)

• A server using the Hytale (GlassMC) egg

• A UDP allocation assigned to the server (Hytale requires QUIC/UDP)

• A valid Hytale account (for device authentication)

• Access to the server console

Step 1: Create the Server

1. In Pterodactyl, create a new server.

2. Select the egg:
   Hytale (GlassMC)

3. Assign:

   • At least 4 GB RAM (recommended)

   • A UDP port allocation

4. Complete server creation.

Do not start the server yet.

Step 2: Set Initial Authentication Mode (Critical)

Before first boot, you must start in offline mode.

1. Go to the server Startup tab.

2. Find the variable:

    

   HYTALE_AUTH_MODE

3. Set its value to:

    

   offline

4. Save changes.

This allows the server to boot without immediately requiring an authenticated session.

Step 3: First Server Start (Bootstrap)

1. Start the server.

2. Wait for startup to complete.

At this stage:

• The Hytale downloader will run

• Server files will be prepared

• The server console will become interactive

The server is not authenticated yet. This is expected.

Step 4: Perform Device Authentication

Once the server is running, authenticate it using device login.

In the server console, run:

The server will output:

• A URL

• A device code

Complete authentication:

1. Open the provided URL in your browser.

2. Log in with your Hytale account.

3. Enter the device code.

4. Approve the login.

Success confirmation

In the server console, you should see:

This writes authentication credentials to disk.
This step only needs to be done once per server.

Step 5: Switch to Authenticated Mode

After authentication is complete:

1. Stop the server.

2. Go back to the Startup tab.

3. Change:

    

   HYTALE_AUTH_MODE=authenticated

4. Save changes.

5. Start the server again.

The server should now:

• Boot normally

• Fetch signed manifests without errors

• Run without authentication prompts

Step 6: Verify Normal Operation

A correctly authenticated server will:

• Start without 403 Forbidden errors

• Not request /auth login device again

• Reach the normal “server booted” state

At this point, setup is complete.

Common Issues & Fixes

❌ 403 Forbidden on startup

Cause: Server is not authenticated yet.
Fix:

• Ensure you completed /auth login device

• Ensure the server was restarted in authenticated mode

❌ Server crashes immediately on first boot

Cause: Missing UDP allocation or incorrect startup order.
Fix:

• Confirm a UDP port is assigned

• Ensure first boot was done in offline mode

❌ Authentication prompt appears every restart

Cause: Server was not restarted after successful auth, or auth files were deleted.
Fix:

• Stop server

• Set HYTALE_AUTH_MODE=authenticated

• Start again

Decommissioning a Server (Important)

If you permanently remove a Hytale server:

1. Stop the server.

2. Delete its data directory.

3. Remove it from your inventory.

Each authenticated server counts toward your 100-session allowance, even if stopped.
Do not leave unused authenticated servers lying around.

What This Egg Does NOT Do

• It does not provide a Hytale license

• It does not bypass authentication

• It does not manage session limits for you

You are responsible for compliance with Hytale Early Access terms.

Summary

First time only:

1. Start in offline

2. /auth login device

3. Switch to authenticated

After that:
The server behaves like a normal dedicated server.