How to authenticate a Hytale server
A Hytale server can boot without tokens and then warn No server tokens configured. On berrybyte, click Authenticate so the panel runs /auth login device, approve the case-sensitive console code on the printed link, and players can join. Public Server Discovery is a separate, optional listing.
A Hytale dedicated server can start with no tokens. The console then warns
No server tokens configured, and players cannot join until you finish
device login. On berrybyte that is a two-stage Hytale Link flow: the
unauthenticated server stays up, you click Authenticate in the alert, the
panel sends /auth login device, and a modal shows the case-sensitive code
and URL the console printed. Approve that request in the browser. Success
dismisses the UI.
This is not silent automatic authentication. The server is allowed to start first; linking happens after the warning.
Hypixel documents the same console command in the Hytale Server Manual and the Server Provider Authentication Guide. Use the exact URL and code your console prints. Printed hosts have varied across builds.
Authenticate with Hytale Link
Start the server
Open the server in the dashboard and start it from the sidebar or Overview. Wait until the server is up. See Start, stop & restart if you need the power controls. A first boot after setup is enough; you do not need to stop it to authenticate.
Open the authentication alert
When the console warns that no server tokens are configured, the panel shows Hytale server authentication required. That alert is the first stage. It does not log you in by itself.
Click Authenticate
Press Authenticate. The panel sends /auth login device to the
running console. The button may show Requesting code… for a few
seconds.
Approve the printed code
The Hytale Link modal shows the device code exactly as the console
printed it, plus Open linking page. The code is case-sensitive. Sign
in to the Hytale account that should own this server and approve the
request before the printed expiry (the console line looks like
Waiting for authorization (expires in … seconds)).
Wait for success
A successful login prints Authentication successful and the modal and
alert close on their own. Players can now
join. If the code expires, the modal
closes and the alert returns so you can request a fresh one.
If you dismiss the alert, the server keeps running. Type
/auth login device in Console, or bring the alert back by requesting
a new code after the next warning.
Run device login from the console
Use this on any host, or on berrybyte if you prefer the console to the button.
Make sure the server is running
Device login is a console command. It needs a running server, not a stopped one.
Run the official command
In Console, send:
/auth login deviceOpen the printed URL
The console prints a Visit URL, an Enter code value, and often an Or visit URL that already includes the code. Open the exact URL it printed. Do not guess a host or retype the code in a different case.
Approve, then confirm
Approve the request in the browser. Watch for
Authentication successful. The official provider guide also lists
/auth status if you want to check the current login after that.
Treat the code like a short-lived password. Anyone who approves it links the server to their Hytale account. Do not paste expired codes, and do not change capitalization.
What persists after a restart
After a successful device login, the running server can accept players. How long that login survives a stop depends on credential storage.
The official provider guide documents two stores: Memory (this session
only) and Encrypted (written to auth.enc). A running authenticated
server refreshes its session on its own. Re-authentication is expected if the
boot warning returns, or if the server stayed offline longer than the unused
refresh window in that guide (30 days).
On berrybyte, do not assume a later start will skip Hytale Link. If the warning is back, click Authenticate again.
Authentication is not Server Discovery
| What you need | What it does | When you need it |
|---|---|---|
Device login (/auth login device) | Lets the dedicated server use Hytale's APIs and accept joins | Every server players will connect to |
| Server Discovery listing | Optional public catalogue from the in-game browser (Update 5) | Only if you want strangers to find the server in that list |
Players can join by address once the server is authenticated, even if you never list it. Listing, review, and heartbeats are covered in Server Discovery.
Common issues
The alert never appears
Confirm the server is actually running and the console showed
No server tokens configured. A server that is already authenticated
will not show the warning. If you dismissed the alert, run
/auth login device in Console.
Authenticate does nothing, or no code appears
The server must be up, not stopping or offline. Wait a few seconds and
try again, or send /auth login device yourself. Use the new code, not
an old screenshot.
The code looks wrong or approval fails
Enter the code exactly as printed. Codes can be mixed-case and may or may not include a dash, depending on what that build printed.
Players still cannot join after success
Confirm the console showed Authentication successful and that you are
sharing the current address from
How to join a Hytale server. Client
and server must be on the same protocol version after an update.
If the warning persists after a successful approval, open a
support ticket with the server
linked and the latest console lines around /auth login device.
See every Hytale guide for setup, join, settings, and mods.
Frequently asked questions
Does a Hytale server start before I authenticate it?
Yes. The server starts and can reach a normal boot. Without tokens it warns No server tokens configured and will not accept player connections until you finish device login. Authentication is not silent and is not required for the server to start.
How do I authenticate a Hytale server on berrybyte?
Start the server, wait for the Hytale server authentication required alert, and click Authenticate. The panel sends /auth login device. A Hytale Link modal then shows the exact case-sensitive code and link from the console. Approve it in the browser while signed into the Hytale account that should own the server. Success dismisses the alert and modal.
Is authenticating the same as listing the server in Server Discovery?
No. Base authentication lets the dedicated server talk to Hytale's APIs and accept player joins. Server Discovery is a separate, optional public catalogue. Players can join by address after auth even if you never list the server.
Will I have to authenticate again after a restart?
Not always. A running authenticated server refreshes its session on its own. Official storage is either in memory for that session or encrypted on disk as auth.enc. If the boot warning returns after a stop, or the server stayed offline longer than the unused refresh window documented in the Server Provider Authentication Guide (30 days), run the Hytale Link flow again.
The Hytale link code expired. What should I do?
Request a new one. Click Authenticate again, or type /auth login device in Console, and use the new code and URL the console prints. Do not reuse an expired code or change its capitalization.