Hytale startup error - Server session token not available - Cannot request auth grant Print

  • Hytale, Startup Error, authentication token
  • 0

Hytale Game Hosting

This guide will help you learn about the startup authentication error where the session token is not found.

Click here to order your Hytale server with Citadel Servers today!

 

This indicates that the server attempted to start but could not proceed because it lacks a valid session token.

A session token is only created after the server successfully authenticates with a Hytale account, so this error appears when authentication has not yet been completed or previously saved credentials are missing.
Without a valid session token, the server cannot request an authentication grant and will immediately reject all player connections.
This guide explains why the error occurs during startup and how to resolve it using Hytale’s device authentication flow.

 

 

Hytale Server Error: "Server session token not available – cannot request auth grant"

 

Overview

When launching a Hytale server, you may encounter the following message in the console:

Server session token not available – cannot request auth grant

When this appears, the server will boot but immediately refuse all player connections. The issue occurs because the server has not yet been authenticated with a valid Hytale account.

This guide outlines the cause of the error and walks you through resolving it using Hytale’s device authentication process.

Symptoms

Typical log output looks like this:

[HandshakeHandler] Server session token not available - cannot request auth grant
Server authentication unavailable - please try again later

Players will be unable to connect while this error is present.


Post Mortem ( The Cause\Issue )

Hytale servers must authenticate with a valid Hytale account before they can generate a server session token.

This error occurs when either of the following is true:

  • The server has never been authenticated
  • The server was authenticated previously, but the credentials were not saved and were lost after a restart

Without a valid session token, the server cannot request an authentication grant and will reject all incoming player connections.

Most game server providers, such as CitadelServers.com, automate this process behind the scenes. If you’re hosting your own instance, however, you’ll need to complete the authentication step manually.

Solution: Authenticate the Server

Step 1: Start the Server

Start by Logging into your Citadel Servers Game Control Panel and navigate to your service.

Start your Hytale server as normal and wait for it to finish booting.

The authentication error may already appear at this stage — this is expected.


Step 2: Run the Device Login Command

In the server console, run:

/auth login device

The console will display a device authorisation prompt similar to:

Visit: https://oauth.accounts.hytale.com/oauth2/device/verify
Enter code: AuXnfPxD

 

Step 3: Authorise via Browser

  1. Open the verification URL shown in the console
  2. Log in with your Hytale account
  3. Enter the displayed code if prompted
  4. Approve the authorisation request

Once completed, the server will authenticate automatically.

You should see logs similar to:

Authentication successful! Mode: OAUTH_DEVICE
Successfully created game session

At this point, the server is authenticated for the current runtime only.


Step 4: Persist Authentication (Required)

To ensure the authentication survives server restarts, run:

/auth persistence Encrypted

You should see confirmation such as:

Credential storage changed to: Encrypted
Loaded encrypted credentials from auth.enc

This stores credentials securely and prevents the error from returning after a restart.


Verification

You can confirm the authentication state at any time with:

/auth status

An authenticated server will report an active session and credential store.


Want a Trouble-Free Setup?

If you would rather avoid manual authentication, command-line setup, and server management entirely, you can order a fully managed Hytale server from LOW.MS.

With LOW.MS:

  • Server authentication is handled automatically
  • Credentials are securely persisted for you
  • Servers are preconfigured and ready to join
  • No manual console commands are required

This is the simplest option if you want a reliable, low-maintenance Hytale server without dealing with setup issues or future authentication changes.


Summary

Step Action
1 Start the server
2 Run /auth login device
3 Authorise in browser
4 Run /auth persistence Encrypted
5 Restart safely

Still Seeing the Error?

If the error persists:

  • Confirm the Hytale account login completed successfully
  • Ensure the server has outbound internet access
  • Check that auth.enc exists and is writable
  • Restart the server after persisting credentials

If you continue to have issues, contact our support team and include your full server startup logs.




Did the above information not work for you?
Please click here to contact our support via a ticket.


Was this answer helpful?

« Back