🎮 Game Error Codes What it means & how to fix it

Sea of Thieves Won't Connect to Services? Here's the Fix

When Sea of Thieves throws a 'Beard' error (LavenderBeard, CinnamonBeard, GreenBeard) or hangs on 'connecting to Sea of Thieves services', it's almost always a network/handshake problem, not your account. Fastest fix in 2026: flush DNS, allow the game through Windows Firewall, and set your DNS to 8.8.8.8 — then relaunch.

Sea of Thieves — the Teredo / NAT chain behind connect errors

Force a static Teredo port (Admin CMD)
netsh interface Teredo set state client clientport=60209
Check NAT type
Xbox App > Settings > Network — NAT must read Open, not Moderate/Strict
Router fixes
Enable UPnP, remove any Teredo filter; disabling IPv6 resolves some disconnects
Root cause
SoT needs a Teredo IPv6 tunnel; if the Teredo adapter fails you get Marblebeard-type connect errors

Last verified: September 2026

Error codes

LavenderBeard The game can't reach or authenticate with Sea of Thieves online services

Cause: A blocked port, stale DNS, or a temporary services outage on Rare's side.

Fix:
  1. Flush DNS: open cmd as admin and run ipconfig /flushdns, then relaunch.
  2. Allow Sea of Thieves through Windows Firewall (Private + Public).
  3. Check the official Sea of Thieves status page — if services are down, wait it out.
  4. Restart your router to pull a fresh connection to Xbox/Rare servers.
AlmondBeard Sea of Thieves lost connection to the game server mid-session and pushed you back to the ferry/main menu

Cause: A brief server-side drop, an unstable Teredo/IPv6 tunnel, or packet loss on Wi-Fi.

Fix:
  1. Switch to a wired Ethernet connection to cut packet loss.
  2. Reset the Teredo tunnel: netsh interface Teredo set state disabled then set state client (Admin CMD), reboot.
  3. Check the official Sea of Thieves status page for a live outage before retrying.
  4. Rejoin — AlmondBeard is usually transient once your NAT reads Open.
KiwiBeard The client could not reach Sea of Thieves matchmaking to place you in a session

Cause: Matchmaking/service congestion after a patch, a strict NAT, or a firewall blocking the handshake.

Fix:
  1. Wait a few minutes after a big update — matchmaking is often overloaded on launch day.
  2. Set NAT to Open: enable UPnP on your router and remove any Teredo filter.
  3. Allow Sea of Thieves through Windows Firewall on both Private and Public.
  4. Flush DNS (ipconfig /flushdns) and relaunch.
CinnamonBeard / GreenBeard Connection to the game session or Xbox Live service dropped

Cause: Xbox Live/PSN service hiccup, NAT/port issues, or an unstable Wi-Fi link.

Fix:
  1. Set your DNS to Google (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1).
  2. Use a wired Ethernet connection instead of Wi-Fi to stabilise the handshake.
  3. Open an Xbox app sign-out/sign-in to refresh your Live token, then relaunch.
  4. On PC, reset Winsock: netsh winsock reset (as admin), then reboot.
Stuck on 'Connecting to Sea of Thieves services' The client started the handshake but never finished authenticating

Cause: Corporate/school network blocking, VPN interference, or a stale login token.

Fix:
  1. Disable any VPN and retry — many VPN exit nodes are blocked by the services.
  2. Verify/repair game files (Steam: Properties > Installed Files > Verify; Xbox app: Manage > Verify & Repair).
  3. Sign out of the Xbox app fully, sign back in, then start the game.
  4. Reboot the PC to clear a stale authentication session.
GreybeardError The client version does not match the live Sea of Thieves servers — usually right after an update

Cause: A partial/queued update, a mod or old shader cache, or files that failed to patch cleanly.

Fix:
  1. Fully close the game and the Xbox app/Steam, then let the update finish before relaunching.
  2. Verify/repair files (Steam: Properties > Installed Files > Verify; Xbox app: Manage > Verify & Repair).
  3. Clear the Sea of Thieves shader/app cache and reboot to force a clean version check.
  4. If it persists, reinstall the latest patch — Greybeard almost always = version mismatch.
BeigeBeard Sea of Thieves lost the connection to the game server and could not re-establish it

Cause: Packet loss, a dropped Teredo/IPv6 tunnel, or an ISP route hiccup to Rare/Xbox servers.

Fix:
  1. Switch to wired Ethernet to kill Wi-Fi packet loss.
  2. Reset Teredo: netsh interface Teredo set state disabled then set state client (Admin CMD), reboot.
  3. Reset the network stack: netsh winsock reset and netsh int ip reset, then reboot.
  4. Restart your router to pull a fresh route to the servers.
SaffronBeard The matchmaking/login servers are overloaded and refused the session request

Cause: Launch-day or post-patch congestion, or a strict NAT slowing the handshake.

Fix:
  1. Wait a few minutes and retry — Saffronbeard spikes on patch days when servers are full.
  2. Set NAT to Open: enable UPnP on the router, remove any Teredo filter.
  3. Check the official Sea of Thieves status page for a live outage before retrying.
  4. Flush DNS (ipconfig /flushdns) and relaunch.
Teredo / IPv6 not available Xbox networking cannot build the Teredo IPv6 tunnel Sea of Thieves needs for multiplayer

Cause: Teredo disabled, a router blocking IPv6, or a VPN/adapter breaking the tunnel.

Fix:
  1. In the Xbox app > Settings > Network, run the test; if Teredo shows unavailable, re-enable it.
  2. Admin CMD: netsh interface Teredo set state type=default, then reboot.
  3. Enable IPv6/UPnP on your router and disable any VPN or extra network adapters.
  4. Set the Teredo server: netsh interface Teredo set state server=win1910.ipv6.microsoft.com.

Fixes that work for most Sea of Thieves errors

  1. Flush DNS (ipconfig /flushdns) and relaunch to clear a stale connection.
  2. Allow Sea of Thieves through Windows Firewall on both Private and Public networks.
  3. Set DNS to 8.8.8.8 / 1.1.1.1 to bypass a flaky ISP resolver.
  4. Disable VPN — blocked exit nodes trigger most 'Beard' errors.
  5. Check the official service status page before assuming it's your PC.
  6. Verify/repair game files and reboot to refresh your Xbox Live token.

FAQ

What does LavenderBeard mean in Sea of Thieves?

It means the game can't reach Sea of Thieves online services. Flush DNS, allow the game through your firewall, and check the official status page — if services are up, switch DNS to 8.8.8.8 and relaunch.

Is Sea of Thieves down or is it my connection?

Check the official Sea of Thieves service status page first. If it shows all-green, the problem is local: flush DNS, disable VPN, and use a wired connection.

How do I fix Sea of Thieves connection errors on PC?

Flush DNS, set DNS to 8.8.8.8, allow the game through Windows Firewall, disable VPN, and verify game files. Reboot to refresh your Xbox Live token.

What does AlmondBeard mean in Sea of Thieves?

AlmondBeard means the game lost its connection to the server mid-session. It is usually transient — switch to wired Ethernet, reset your Teredo tunnel, check the official status page, and rejoin.

Other games