Sea of thieves hazelnutbeard ошибка

---

Автор: Largo

Обновлено: ноябрь 16-го 2021

---

Если ошибка Hazelnutbeard не позволяет вам получить доступ в Sea of Thieves, попробуйте предпринять перечисленные ниже шаги:

Решение 1: перезагрузите Sea of Thieves

1. Нажмите клавишу Windows
2. Наберите «Приложения и функции»
3. Найдите в списке Sea of Thieves
4. Выберите «Дополнительные параметры»
5. Выберите «Сбросить»

Решение 2: подтвердите, что дата и время вашей системы выставлены верно

1. Правой кнопкой мыши щёлкните на изображении часов в стартовом меню
2. Выберите «Выставить дату/время».
3. Снимите и снова поставьте отметку в пункте «Автоматически выставлять часовой пояс». (Если часовой пояс уже выставляется автоматически, переключитесь на изменение вручную, а потом снова на автоматическое выставление)
4. Перезагрузите компьютер

Решение 3: проверьте обновления Windows

• Нажмите клавишу Windows
• Наберите «Обновить»
• Выберите «Проверка обновлений»
• Если есть доступные обновления, загрузите и примените их.
• Перезагрузите свой компьютер, а затем попробуйте снова зайти в Sea of Thieves
• Решение 4: IP Helper

1. Нажмите клавишу Windows и откройте поиск служб.
2. Найдите в списке IP Helper и проверьте, работает ли эта служба; если нет, возможно, в этом причина проблемы.
3. Щёлкните по IP Helper правой кнопкой мыши и перейдите в «Свойства», а затем во вкладку «Зависимости».
4. Ищите каждую зависимость в списке служб; удостоверьтесь, что все они работают, и выставьте для каждой автоматический запуск. Проверку можно провести, щёлкнув правой кнопкой мыши на службе и выбрав «Свойства». На этой странице есть раскрывающийся список запуска. Убедитесь, что в нём выбран автоматический запуск (как правило, не работает служба WinHTTP Web Proxy Auto-Discovery service)
5. Как только вы найдёте неработающую службу, щёлкните по ней правой кнопкой мыши и нажмите «Начать». Если надпись неактивна, и вы не можете перезапустить процесс, переходите к следующему этапу. Если вы можете запустить процесс, перезагрузите компьютер и проверьте, работает ли IP Helper. Этого должно быть достаточно.
6. Если процесс всё ещё не идёт, переходите к части 2.

Часть 2

1. Если процесс нельзя запустить из меню правой кнопки мыши, вероятно, у вас проблема с реестром, из-за которой он не работает должным образом.
2. Нажмите клавишу Windows и найдите редактор реестра, затем запустите от имени администратора.
3. Быстрый поиск в Google подскажет вам, где именно искать неработающую службу зависимости.
   Найдите для службы значения по умолчанию и измените их в свойствах.
4. Перезапустите компьютер
5. Проверьте IP Helper

Решение 5: исправление ошибки Ashbeard
https://support.seaofthieves.com/hc/articles/360000695787-Troubleshooting-Ashbeard-error-Player-is-not-signed-into-xbox-live 

Решение 6: перенаправление порта
https://support.xbox.com/help/Hardware-Network/connect-network/network-ports-used-xbox-live 

Другие решения, которые вы можете использовать:

— Отключите все использующиеся VPN
— Запустите сканирование на вредоносное ПО на вашем компьютере (отличается от антивирусного сканирования)
— Отключите антивирус и проверьте, повторяется ли ошибка. Если нет, вам нужно будет внести Sea of Thieves в «белый список» вашей антивирусной программы

---

Как и во всех видеоиграх, для игры в которые требуется подключение к сети, Sea of ​​Thieves выдает некоторые коды ошибок, когда они работают некорректно. В случае с этой игрой коды ошибок представлены в виде разных бород. Если вы играете в Sea of ​​Thieves на Xbox или на Windows 10, возможно, вы столкнулись с кодом ошибки Hazelnutbeard. Вот что вы можете с этим поделать.

Исправление 1 — Обновление 2.1.1.1

В мае 2021 года в игре произошла ошибка, из-за которой игроки вылетали из игры Hazelnutbeard, когда слишком много ящиков с товарами торговых эмиссаров с разных аванпостов было собрано в одном месте за раз. Разработчики заявили, что исправили эту ошибку в обновлении 2.1.1.1.

Если вы все еще получаете код ошибки Hazelnutbeard, похоже, это может иметь какое-то отношение к вашему подключению к серверам игры. Починить это:

Попробуйте сбросить Sea of ​​Thieves, набрав «Приложения и функции» в строке поиска Windows (вы можете нажать клавишу Windows, чтобы открыть его). Найдите Sea of ​​Thieves в списке приложений и нажмите «Дополнительные параметры». Прокрутите вниз, пока не найдете Сброс, и выберите его.

Исправление 3 — Обновите системную дату и время

Если описанный выше метод не помог вам исправить ошибку Hazelnutbeard в Sea of ​​Thieves, разработчики также рекомендуют проверить правильность даты и времени в вашей системе. Это, вероятно, так для большинства людей, поэтому проверьте, полностью ли обновлено ваше Sea of ​​Thieves. Если вы играете в более старую версию игры, это может вынудить вас отказаться от нее.

Если ни один из вышеперечисленных способов у вас не помог, рекомендуем перейти на страница поддержки игры и связаться с командой там. Кто-то должен быть в состоянии помочь вам.

«Бородой», а точнее кодом «-beard» в Sea of Thieves отмечаются самые разнообразные баги, сбои и ошибки. На момент публикации этого поста разноцветных и разно…плановых бород в игре мы насчитали почти 40 штук.

Так что, с багами в Sea of Thieves, что называется, полный порядок — в буквальном смысле на любой вкус и цвет, если считать вот так по бородам.

Но так как значительная часть этих самых beard-кодов по факту означают одно и то же, то и сгущать краски особого смысла нет (по крайней мере пока).

И самое главное, по коду бороды в любом случае гораздо проще определить причину проблемы и её быстренько пофиксить. О чем сейчас и будем рассказывать.

В общем, по мере актуальности (юзаем поиск по странице — так будет проще):

код Marblebeard в Sea of Thieves

…выкидывает из игры — происходит это либо из-за перегруза на сервере, либо из-за сбоя подключения (в т.ч. по причине некорректного типа NAT), следовательно, сначала пробуем просто перезайти и если не получилось, то проверяем статус сервера, проверяем подключение (перезагружаем консоль и роутер), проверяем тип NAT

• в меню гида переходим в раздел «Профиль и система«,
• открываем «Настройки» > «Общие» > «Настройки сети»,
• в разделе «Текущее состояние сети«, находим поле «Тип NAT».

Тип NAT должен быть «Открытый» (Open) — подробнее ЗДЕСЬ.

код Kiwibeard

…чаще всего возникает по причине того, что с консоли игра регистрирует сразу несколько тегов, а заходить можно только одному пользователю. Потому проверяем и выходим со всех учеток, и затем перезаходим в Sea of Thieves по-новой.

Кроме того, Kiwibeard также иногда выскакивает, когда сбоят сервера. А значит текущий статус сервера тоже не лишним будет проверить.

код Hazelnutbeard

… но сначала в игре начинают происходить всякие непонятки вроде неубиваемых скелетов, неоткрываемых сундуков и пр. После чего выскакивает сообщение об ошибке с кодом Hazelnutbeard. Иногда, если повезет и быстро перезапустить игру, то получается нормально перезайти. Но это не точно…

Если же этот код выскакивает регулярно и не дает нормально играть, то в таком случае рекомендуется сначала проверить корректность даты и времени системы и выставить правильные. А если с этим все ОК, то тогдп надо сбросить данные игры (если играем на компе). А для этого:

• в строке поиска системы пишем приложения и возможности
• далее в списке программ кликаем Sea of Thieves и жмем «Дополнительные параметры«
• следующее окно прокручиваем чуть вниз и кликаем кнопку «Сброс«.

коды Yellowbeard и Grandpabeard

Yellowbeard означает временный бан в игре. Как правило, дают его по чьим-то жалобам и в качестве наказания за нарушения правил поведения в Sea of Thieves (мат, оскорбления, читерство, стрим-снайпинг и т.п.). Срок бана зависит от масштабов и/или количества проступков.

Не пропустите:

Если выскочил код Grandpabeard, значит вас «кикнули» прямо по ходу игры. Теперь отдыхаем и делаем выводы…

Ещё «по мелочи»:

• коды Cinnamonbeard и Bronzebeard — не получается зайти в Sea of Thieves > пробуем перезайти, а если все равно не получается, то перезагружаем консоль и потом пробуем зайти еще раз.

• код Redbeard — перманентный БАН аккаунта. За «успешное» нарушение правил игры. Теперь точно придется начинать все заново и с новой учеткой.

• код AlapacaBeard — игра куплена на Steam-е и «что-то пошло не так с покупкой», потому проверяем, прошла ли оплата и с какой учетной записи (возможно, надо перелогиниться) — если не помогает, то переустанавливаем игру и клиент Steam.

• код Strawberrybeard — либо серверы остановлены на техобслуживание (проверяем статус и смотрим твиттер саппорта), либо есть проблема со связью (проверяем подключение), либо сбоит Xbox Live (перезагружаемся и проверяем обновления).

• код Ashbeard — заходим в свою учетку на Xbox Live, после чего перезапускаем игру. Если игра есть, а аккаунта в Xbox Live еще нет, то регистрируемся — без Xbox Live игра работать не будет.

• код Avocadobeard — требуется статус Xbox Live Gold — покупаем и/или проверяем срок подписки (возможно, пора продлевать).

• коды Greybeard и Charcoalbeard — обычно означают очередной сбой на стороне серверов, потому если перезагрузка не помогает, то проверяем статус сервера, и ждем пока саппорт все починит.

• код Lazybeard — система борьбы с ботами не спит. Не стоим и шевелимся, иначе выкинет из игры и напишет «ленивая борода».

• коды Alabasterbeard, Allmondbeard, Cyanbeard, Coarsebeard — указывают на проблему с подключением на стороне пользователя, а значит, проверяем связь (если надо перезагружаем комп, роутер и/или подключаемся через кабель), либо же не работают серверы Xbox Live (проверяем их статус).

• коды BeigeBeard и LightbeigeBeard — устаревшая версия игры — закрываем Sea of Thieves, проверяем и устанавливаем обнову и заходим заново (можно также включить автообновление).

• код Lavenderbeard — проблема с подключением — проверяем статус серверов и связь у себя, а также смотрим, чтобы игру не блочили антивирус или брандмауэр Windows (если блокируют, то или добавляем exe-шник Sea of Thieves в список исключений, или отключаем антивирус на время игры).

• код Fishbeard — не получается играть командой — вероятнее всего, это баг на стороне сервера, если перезапуск не помогает, то похоже часок-другой придется поиграть самому.

• коды Lapisbeard и Daffodilbeard — сбой серверов — проверяем статус на всякий случай, читаем твиттер службы поддержки и играем в другую игру, пока саппорт проблему выявит и пофиксит.

• код Amethystbeard — сбой серверов Xbox Live — тоже проверяем статус и играем в другую игру, пока саппорт Microsoft проблему выявит и устранит.

• код Fluffybeard — технические работы на серверах (как правило, перед выходом очередного обновления).

• коды Beatnikbeard и Gulliverbeard — на момент отправки приглашения команда уже распущена — связываемся с тиммейтами и уточняем ситуацию и/или играем соло.

• коды Trimmedbeard и Emeraldbeard — выкинуло из игры и подключится уже не получается и не получится — надо заходить по-новой (разница только в том, что Trimmedbeard — код для Арены, а Emeraldbeard — для режима приключений).

• коды Llamabeard, Coralbeard, Obsidianbeard — игра вылетает по непонятным причинам — проверяем статус серверов и подключение, перезагружаемся и пробуем зайти снова.

• код Sleepybeard — тоже самое, что и Lazybeard (см. выше) — выскакивает автоматом, если система замечает длительное бездействие персонажа, или, например, во время рыбалки, когда персонаж стоит на месте, и нажимать надо всего пару кнопок. Потому стараемся хоть немного двигаться.

• коды Bernardbeard и Hopscotchbeard — проверяем ящики.

• код Pastiebeard — «отвалился интернет» в буквальном смысле, то есть, во время игры отключился кабель Ethernet — потому аккуратно продаем все, что собрались, завершаем путешествия, и только потом чиним занимается подключением.

• код Copperbeard — персонаж не активен и/или окно игры свернуто — шевелимся!

• код Pythonbeard — система заметила применение макросов или многократное повторение какого-то действия — с макросами «завязываем», иначе будет ошибка Yellowbeard (см. в начале поста).

• код Crumbsbeard — попытка присоединиться к команде без приглашения — запрашиваем/отправляем приглос или создаем новую команду.

• код Bushybeard — команда укомплектована — пробуем присоединиться еще раз или ищем другую команду.

• код Mysteriousbeard — эта ошибка появляется, когда кто-то из тиммейтов выходит или подключается к сеансу, также Mysteriousbeard случается по ходу стрима, когда стример в качестве защиты от стрим-снайпинга или грубости игроков убирает свой геймтег.

• код Groomedbeard — случается в ходе командной игры, когда отключаешься или подключаешься к сеансу тиммейта — устраняется проблема перезапуском игры.

• код Coldbeard — баг в лобби перед выходом на Арену — просто пробуем зайти еще раз.

• код Granitebeard — непонятный баг игры в режиме Арены — в большинстве случаев лечится сменой режима (т.е. переходим в Приключения и потом возвращаемся в режим Арены).

• код Longbeard — проверяем настройки сети (QoS), перезагружаем роутер, перезапускаем игу.

• код Zaffrebeard — сбой подключения к серверу по ходу игры в режиме Арены — проверяем статус сервера и подключение, перезаходим в игру.

• код Tidybeard — проблема с подключением — проверяем связь, перезагружаем роутер и комп/консоль, проверяем тип NAT (должен быть «Открытый» см. выше) и порты для Xbox Live (тоже должны быть открыты), проверяем антивирус и брандмауэр Windows.

• код Cherrybeard — эта ошибка чаще всего случается, когда играешь в Sea of Thieves на Xbox, а потом заходишь в какую-то другую игру с того же аккаунта, но на компе — потому просто заходим в игру на консоли.

• код Inputbeard — ошибка указывает на то, что кто-то пытается присоединится к команде не с Xbox, а с ПК, притом к клавиатурой, а не с геймпадом — открываем настройки команды и разрешаем заходить всем, а не только пользователям Xbox.

коды Denimbeard и Cottonbeard в Sea of Thieves

Ошибка Denimbeard указывает на то, что вы пытаетесь поиграть в так называемую «инсайдерскую» версию Sea of Thieves, но без соответствующей учетной записи. Следовательно, сначала регистрируем аккаунт (из основных требований возраст 18 и старше, плюс знание игры).

Код Cottonbeard — баг из той же серии: вы пытаетесь поиграть в «инсайдерскую» версию, но учетка уже есть. В таком случае, инсайдерскую игру закрываем, запускаем обычную, играем некоторое время и выходим. После чего снова заходим в «инсайдерскую».

Beard Errors are quick reference codenames for various issues and errors that can occur in Sea of Thieves.

Solutions and causes provided below are a combination of official and user-observed information. The exact reason for a Beard Error may not be completely accurate for each occurrence, especially in the case of wide-spread server issues.

Types of Beard Errors[]

Alabasterbeard[]

A connection to Xbox live and/or the Sea of Thieves services was disrupted or lost, commonly caused by game server issues. If on Xbox One, Rare suggests to check the console’s network status via the Settings > Network menu. On a PC, determine that you have a stable Internet connection.

Allmondbeard[]

A connection to Xbox live and/or the Sea of Thieves services was disrupted or lost. If on Xbox One, Rare suggests to check the console’s network status via the Settings > Network menu. On a PC, determine that you have a stable Internet connection.

Alpacabeard[]

Error received when the Xbox Account has not purchased Sea of Thieves and tries to log in to the servers.

Amethystbeard[]

Error indicates that the player is not connected to Xbox Live due to a connection problem.

Ashbeard[]

A connection to Xbox Live is not established. Sea of Thieves requires an Xbox Live on Internet connection at all times to be played. Rare suggests the player to ensure their Xbox Live status is connected and then sign in and try again.

Averybeard[]

This error occurs when the session code is left blank when attempting to join a Custom Server.

Avocadobeard[]

An Xbox Live Gold membership was not identified on an Xbox One game client. When playing on an Xbox One console, a Player needs an Xbox Live Gold membership to play online. Rare suggests to check the subscription settings and purchase a Gold membership as needed.

Beatnikbeard[]

This error is given when the game detects that you are trying to join a crew that doesn’t exist.

Beigebeard[]

A player does not currently have the latest version of the game installed; a version mismatch. Rare suggests to check for updates. This can be done via the Microsoft Store app on Windows 10.

Beanbeard[]

Indicates that a network error has occurred. Causes of this error are unknown, but seems to be related to a session failure.

Bernardbeard[]

This error occurs when the player has a delivery crate pickup from an unknown location or when the player has a delivery crate with an unknown destination. The text «Good luck! The address has fallen off!» will appear.

Bronzebeard[]

A connection to the game was failed. Rare suggests to try the following if on console:

• Press the Guide Button on the controller.
• Highlight Sea of Thieves.
• Press the Menu Button (to the right of the Guide Button on the controller).
• Highlight «Quit» and press A.
• Re-launch Sea of Thieves from Pins, Recent or My Games & Apps areas of the console
• Navigate the menu and join a game as usual

Bushybeard[]

When trying to join a crew session when it has been filled.

Cabbagebeard[]

Details unknown. May be related to a server connection failure. This error may also be caused by antivirus/firewall settings, proxy servers or other network management/manipulation tools.

Charcoalbeard[]

Indicates a problem with matchmaking.

Cherrybeard[]

Happens when you get signed out of Xbox Live while playing.

Cinnamonbeard[]

A connection to the game was failed. Rare suggests to try the following if on console:

• Press the Guide Button on the controller.
• Highlight Sea of Thieves.
• Press the Menu Button (to the right of the Guide Button on the controller).
• Highlight «Quit» and press A.
• Re-launch Sea of Thieves from Pins, Recent or My Games & Apps areas of the console
• Navigate the menu and join a game as usual

Coarsebeard[]

A connection to Xbox Live and/or the Sea of Thieves services was disrupted or lost. If on Xbox One, Rare suggests to check the console’s network status via the Settings > Network menu. On a PC, determine that you have a stable Internet connection.

Coldbeard[]

Received when matchmaking with an Arena Game Mode Lobby fails. Try setting sail again if encountered.

Copperbeard[]

Related to inactivity, this error can occur when idle in the emporium menu for too long, can also occur if you tab out during a loading screen.

Coralbeard[]

Occurs when Sea of Thieves services are temporarily unavailable.

Crumbsbeard[]

Received when trying to join someone’s game who has limited their Crew only to invited people.

Cottonbeard[]

This error will trigger if a player hasn’t played on the retail build of Sea of Thieves for a long time and then attempts to play on the Insiders build. To solve this error the player should first log into and launch a session on the retail build.

Cyanbeard[]

A connection to Xbox Live and/or the Sea of Thieves services was disrupted or lost. If on Xbox One, Rare suggests to check the console’s network status via the Settings > Network menu. On a PC, determine that you have a stable Internet connection.

Daffodilbeard[]

Something has happened on Rare’s side that they are working to fix. Rare suggests to check the status of the game at https://www.seaofthieves.com/status for more information.

Daisybeard[]

Displayed when there are issues connecting to services. Rare suggests relaunching the game and trying again. This error may also be caused by antivirus/firewall settings, proxy servers or other network management/manipulation tools.

Denimbeard[]

Can display during the matchmaking flow on the Insider version of Sea of Thieves. Should a Player see this error it means that they are not signed up to the Insider programme. A player can sign up at https://www.seaofthieves.com/insider, providing that they are 18+ years of age and either own a Game Pass subscription or a physical or digital copy of Sea of Thieves.

Alternatively, a Player may have been removed from the old pioneer programme or the new Insider programme for breaking the Terms and Conditions agreed to when signing up. For further support on this issue Rare suggests raising a support request at https://support.seaofthieves.com/hc/en-gb.

Emeraldbeard[]

When trying to join a crew session that has been closed (usually when trying to rejoin a game when the crew/server has crashed). This one is presumably only for Adventure Mode, whereas Trimmedbeard is for Arena Mode.

Fishbeard[]

This is an issue with Sea of Thieves servers. Rare states that in this case, the team is hard at work to get everyone back in and playing as quickly as possible!

Fluffybeard[]

Rare have either taken the servers down for an update, or they are not currently running a playtest session at the time. Rare suggests to verify whether there is a scheduled playtest running in the player’s timezone.

Grandpabeard[]

This error is displayed when a player has been kicked from the game as a result of getting banned.

Granitebeard[]

Details unknown; Players have reported encountering the error during Arena.

Greybeard[]

This is an issue with Rare’s servers, the team are hard at work to get everyone back in and playing as quickly as possible!

Groomedbeard[]

An error received when trying to re-connect to a session, or connect to a crew via invite or direct from the friends list. It may also be due to a high influx of players on servers.

Possible solutions include: Starting a new session, restarting the Xbox App, or re-launching Sea of Thieves.

Gulliverbeard[]

An error received when trying to join a crew session that does not exist.

Hazelnutbeard[]

Appears to be a connection issue to the game servers. This error usually follows strange in-game behavior such as chests that cannot be opened, skeletons that cannot be killed, or random ship placement. Also can occur shortly after you sink an enemy player ship. This is believed to be caused by the server receiving too many packets.

Hopscotchbeard[]

This error occurs when the player has a delivery crate pickup from an unknown location or when the player has a delivery crate with an unknown destination. The text «Good luck! The address has fallen off!» will appear.

Inputbeard[]

The Crew you are joining is set to prefer Xbox players using Xbox controllers. The Crew leader will need to reform the Crew with the setting «Prefer to play with Xbox players using Xbox controllers» set to «No». This can be found in the «Matchmaking Preferences» setting menu.

Kiwibeard[]

This can be caused by any of the following:

• The Servers Are Closed – The game is not running a play session when a player tried to log in, so they cannot play Sea of Thieves at that moment.
• A player has more than one Gamertag signed in to their console. Rare suggests to sign all other accounts out of the console, and only launch the game with the one account that has been invited to play.

Lapisbeard[]

Something has happened on Rare’s side that they are working to fix. Rare suggests to check the status of the game at https://www.seaofthieves.com/status for more information.

Lavenderbeard[]

Can arise if new players are temporarily prevented from joining the game as part of an effort to resolve server issues. If this is the case, Rare will attempt to get everyone back in and playing as quickly as possible! This may also be caused by antivirus/firewall settings, proxy servers or other network management/manipulation tools.

This can also occur if there is an issue connecting to Xbox Live services, and has been known to happen on Steam after changing your Xbox account’s password. Signing out of Xbox Live services and back in may resolve this issue.

Lazybeard[]

The error stating that a Player has been removed from the active game session due to lack of activity. This is to prevent servers from being held open by inactive players and to give room for new players to join.

Leekbeard[]

Can occur when servers experience high server loads, such an increased amount of players logging in.
This can also be caused by version mismatch. Check that your game is updated to the current version.

Lettucebeard[]

Displayed when there are issues connecting to services. Rare suggests relaunching the game and trying again. This error may also be caused by antivirus/firewall settings, proxy servers or other network management/manipulation tools.

Lightbeigebeard[]

A player does not currently have the latest version of the game installed; a version mismatch. Rare suggests to check for updates. This can be done via the Microsoft Store app on Windows 10.

Lincolnbeard[]

This error occurs when an invalid session code is entered when attempting to join a Custom Server.

Llamabeard[]

This error occurs when Sea of Thieves Services are temporarily unavailable.

Longbeard[]

Indicates there is a problem with the player’s network setup, specifically around how it handles the game-play experience. Rare suggested making sure you don’t have QoS (Quality of Service) options enabled on your router.

Marblebeard[]

Is known to happen during a failed attempt to rejoin a session. Likely to occur after a disconnect due to another server error.

Mysteriousbeard[]

This error can appear with Replace Gamertags («Streamer Mode») enabled while crewmates join or leave your session.

Pastiebeard[]

This error occurs when the game detects a loss of connection due to Ethernet cable unplugging.

Pepperbeard[]

Has been known to occur when joining a game session through an invite. Causes unknown.

Pythonbeard[]

This error occurs when the game identifies that a player is using a macro or engaging in suspicious repetitious behavior.

Obsidianbeard[]

Occurs when Sea of Thieves server connection fails. No fix available.

Okrabeard[]

Details unknown. Players have reported encountering the error on Xbox consoles.

Redbeard[]

Occurs when the player is permanently banned from the game, usually due to a violation of the terms of service or code of conduct.

Sleepybeard[]

Related to inactivity, this error occurs after a certain amount of time not moving your character. Differs from Lazybeard as it can happen even if buttons are being pressed such as fishing in the same spot for a length of time.

Strawberrybeard[]

Most commonly caused by Sea of Thieves services being temporarily unavailable.

Has also been reported to be related to various errors including a version mismatch. Rare recommends updating your game to see if that fixes the problem. Another solution is to try logging out and then back into the Xbox account.

This error is given on the Insider Programme Client when the account has not logged into the Retail client for a few weeks. Log in to the Retail account to fix the issue.

Trimmedbeard[]

When trying to join a crew session that has been closed (usually when trying to rejoin a game when the crew/server has crashed).

Tidybeard[]

Occurs When a player’s connection is blocked by either IPV6/Teredo router settings, a closed NAT, closed Xbox Live ports, or firewall/antivirus software blocking the connection.

Yellowbeard[]

Occurs when the player is temporarily banned from the game.

Zaffrebeard[]

Occurs when connection to arena is mashed up.

Sea of Thieves has a strange, but fun way of identifying errors for players. If an issue shows up for players while they’re trying to connect, they display a Beard Error to help the player see what the problem is. In the list below, we explain what each error means and how to fix them! We’ve sorted them in alphabetical order.

AlabasterBeard, AlmondBeard, & CyanBeard

• Issue: This is a player-side internet issue that means the player’s connection to Xbox Live or the Sea of Thieves servers has been interrupted.
• Solution: Check your network to make sure it’s online and connected. If a firewall is enabled, change it to allow connection to the Sea of Thieves and Xbox Live servers.

AlpacaBeard

• Issue: This is a player-side issue that usually means the servers could not confirm you have a valid game license. It may be caused by using an illegally downloaded copy of the game or from corrupt game and Steam client files.
• Solution: Make sure your game client was purchased from a licensed platform. If you’re using Steam, make sure you’re properly logged in. If this fails, uninstall and re-install the game or Steam client.

AshBeard

• Issue: This is a player-side network issue that means you’re not properly logged in to the Xbox Live network.
• Solution: Make sure you’re logged in to Xbox Live and try to connect again. If you cannot log in to Xbox Live, contact Microsoft Support.

AvocadoBeard

• Issue: This is a player-side issue that means you do not have a Gold Membership with your Xbox Live account, which is required to play Sea of Thieves.
• Solution: Make sure you’re logged in to Xbox Live and have purchased an Xbox Live Gold Membership, then try again.

BeigeBeard & LightbeigeBeard

• Issue: This is a player-side issue that means you do not have the most recent version of the game.
• Solution: Force an update on the game on the Steam or Windows App Store. If it won’t install the updated, uninstall and re-install the game.

Related: How to Get Ancient Coins in Sea of Thieves — Pro Game Guides

BronzeBeard & CinnamonBeard

• Issue: This is a catchall error that means something interrupted your connection to the game, but the servers and game cannot determine the exact cause.
• Solution: If it happens repeatedly, a full game restart may be required. Force a shutdown of the game on your console with the following steps, then restart the game.
  1. Press the Guide button on your controller
  2. Highlight Sea of Thieves
  3. Press the Menu button on your controller
  4. Select Quit.

DaffodilBeard

• Issue: This is a server-side catchall error that means something on their end couldn’t connect your game, but the servers and game cannot determine the exact cause.
• Solution: The game servers may be down. Try again later. Use our guide to check the Sea of Thieves Server Status to know when it’s okay to try again.

DenimBeard

• Issue: This is an error that applies only to players playing the Insider version of Sea of Thieves. It means there is an issue verifying the account. It can happen if the player is not signed up for the Insider version, or if their account was removed from the program for any reason.
• Solution: Verify your account status with the Insider program and try again. If you have been removed from the program, you cannot connect to the servers for that version of the game and must inside connect to the normal servers.

FishBeard, GreyBeard, & LapisBeard

• Issue: This is a server-side error that means there is an issue on their end stopping players from joining the game.
• Solution: The game servers may be down. Try again later. Use our guide to check the Sea of Thieves Server Status to know when it’s okay to try again.

FluffyBeard

• Issue: This is a server-side error that applies only to players playing developmental versions of the game. It means they’re not playtesting the version you want to use or it could not connect to your system.
• Solution: Check to see when they are playtesting in your time-zone and try logging in at the scheduled time.

KiwiBeard

• Issue: This could be a server-side issue or a client-side issue. It means that the servers are temporarily closed or that the player is trying to log in while their account is already logged in on another device.
• Solution: Sign out of all other accounts and try again. If it happens again, then the game servers may be down. Try again later. Use our guide to check the Sea of Thieves Server Status to know when it’s okay to try again.

LavenderBeard & StrawberryBeard

• Issue: This is usually a server-side issue that means their servers are down for maintenance. It can also be caused by a player’s Firewall or Antivirus software blocking the game from connecting.
• Solution: Verify that your Firewall and Antivirus allow the game client to reach outside of the network and try again. If it happens again, then the game servers may be down for maintenance. Use our guide to check the Sea of Thieves Server Status to know when it’s okay to try again.

Related: How to Find the Shores of Gold in Sea of Thieves | Shores of Gold Tall Tale — Pro Game Guides

LazyBeard

• Issue: This simply means that you were idle in the game too long, so they disconnected you from the server.
• Solution: When you’re ready to play again, log back in.

RedBeard

• Issue: This error means your account has been permanently banned from the Sea of Thieves servers and is usually only caused by a serious breach of the Code of Conduct or Terms of Service.
• Solution: Contact Sea of Thieves Game Support if you feel your account was banned in error.

YellowBeard

• Issue: This error means your account has been temporarily banned from the Sea of Thieves servers because of a violation of their Code of Conduct or Terms of Service.
• Solution: Wait until the account is re-enabled and the suspension is lifted, then try again. Contact Sea of Thieves Game Support if you feel your account was suspended in error.

Those are all the Beard Errors currently in the game! Be sure to check out our Sea of Thieves Homepage for more great guides and content!

Once you’re connected, be sure to use our guides to help you through all the Tall Tales! You can start with The Shroudbreaker or Heart of Fire.

Follow us on Twitter and Facebook to get updates on your favorite games!

Sea of Thieves has a strange, but fun way of identifying errors for players. If an issue shows up for players while they’re trying to connect, they display a Beard Error to help the player see what the problem is. In the list below, we explain what each error means and how to fix them! We’ve sorted them in alphabetical order.

AlabasterBeard, AlmondBeard, & CyanBeard

• Issue: This is a player-side internet issue that means the player’s connection to Xbox Live or the Sea of Thieves servers has been interrupted.
• Solution: Check your network to make sure it’s online and connected. If a firewall is enabled, change it to allow connection to the Sea of Thieves and Xbox Live servers.

AlpacaBeard

• Issue: This is a player-side issue that usually means the servers could not confirm you have a valid game license. It may be caused by using an illegally downloaded copy of the game or from corrupt game and Steam client files.
• Solution: Make sure your game client was purchased from a licensed platform. If you’re using Steam, make sure you’re properly logged in. If this fails, uninstall and re-install the game or Steam client.

AshBeard

• Issue: This is a player-side network issue that means you’re not properly logged in to the Xbox Live network.
• Solution: Make sure you’re logged in to Xbox Live and try to connect again. If you cannot log in to Xbox Live, contact Microsoft Support.

AvocadoBeard

• Issue: This is a player-side issue that means you do not have a Gold Membership with your Xbox Live account, which is required to play Sea of Thieves.
• Solution: Make sure you’re logged in to Xbox Live and have purchased an Xbox Live Gold Membership, then try again.

BeigeBeard & LightbeigeBeard

• Issue: This is a player-side issue that means you do not have the most recent version of the game.
• Solution: Force an update on the game on the Steam or Windows App Store. If it won’t install the updated, uninstall and re-install the game.

Related: How to Get Ancient Coins in Sea of Thieves — Pro Game Guides

BronzeBeard & CinnamonBeard

• Issue: This is a catchall error that means something interrupted your connection to the game, but the servers and game cannot determine the exact cause.
• Solution: If it happens repeatedly, a full game restart may be required. Force a shutdown of the game on your console with the following steps, then restart the game.
  1. Press the Guide button on your controller
  2. Highlight Sea of Thieves
  3. Press the Menu button on your controller
  4. Select Quit.

DaffodilBeard

• Issue: This is a server-side catchall error that means something on their end couldn’t connect your game, but the servers and game cannot determine the exact cause.
• Solution: The game servers may be down. Try again later. Use our guide to check the Sea of Thieves Server Status to know when it’s okay to try again.

DenimBeard

• Issue: This is an error that applies only to players playing the Insider version of Sea of Thieves. It means there is an issue verifying the account. It can happen if the player is not signed up for the Insider version, or if their account was removed from the program for any reason.
• Solution: Verify your account status with the Insider program and try again. If you have been removed from the program, you cannot connect to the servers for that version of the game and must inside connect to the normal servers.

FishBeard, GreyBeard, & LapisBeard

• Issue: This is a server-side error that means there is an issue on their end stopping players from joining the game.
• Solution: The game servers may be down. Try again later. Use our guide to check the Sea of Thieves Server Status to know when it’s okay to try again.

FluffyBeard

• Issue: This is a server-side error that applies only to players playing developmental versions of the game. It means they’re not playtesting the version you want to use or it could not connect to your system.
• Solution: Check to see when they are playtesting in your time-zone and try logging in at the scheduled time.

KiwiBeard

• Issue: This could be a server-side issue or a client-side issue. It means that the servers are temporarily closed or that the player is trying to log in while their account is already logged in on another device.
• Solution: Sign out of all other accounts and try again. If it happens again, then the game servers may be down. Try again later. Use our guide to check the Sea of Thieves Server Status to know when it’s okay to try again.

LavenderBeard & StrawberryBeard

• Issue: This is usually a server-side issue that means their servers are down for maintenance. It can also be caused by a player’s Firewall or Antivirus software blocking the game from connecting.
• Solution: Verify that your Firewall and Antivirus allow the game client to reach outside of the network and try again. If it happens again, then the game servers may be down for maintenance. Use our guide to check the Sea of Thieves Server Status to know when it’s okay to try again.

Related: How to Find the Shores of Gold in Sea of Thieves | Shores of Gold Tall Tale — Pro Game Guides

LazyBeard

• Issue: This simply means that you were idle in the game too long, so they disconnected you from the server.
• Solution: When you’re ready to play again, log back in.

RedBeard

• Issue: This error means your account has been permanently banned from the Sea of Thieves servers and is usually only caused by a serious breach of the Code of Conduct or Terms of Service.
• Solution: Contact Sea of Thieves Game Support if you feel your account was banned in error.

YellowBeard

• Issue: This error means your account has been temporarily banned from the Sea of Thieves servers because of a violation of their Code of Conduct or Terms of Service.
• Solution: Wait until the account is re-enabled and the suspension is lifted, then try again. Contact Sea of Thieves Game Support if you feel your account was suspended in error.

Those are all the Beard Errors currently in the game! Be sure to check out our Sea of Thieves Homepage for more great guides and content!

Once you’re connected, be sure to use our guides to help you through all the Tall Tales! You can start with The Shroudbreaker or Heart of Fire.

Follow us on Twitter and Facebook to get updates on your favorite games!

I had this same problem for a long time. It was recently fixed, maybe it’s a similar situation.

I had Hazelnutbeard errors for months, while it seemed for the most part that I could stream all the TV apps I wanted in any room with no problems. This game seemed to be the only thing that crashed my internet.

I have Comcast internet, and I used to have TV service through them as well. When installed, they put in an amplifier in the garage to boost the signal for the modem and three TVs. I cancelled the TV service months ago, but all they did was have me bring them the TV boxes. They should have come and uninstalled the amplifier.

When the tech finally came out he took one look at the amplifier and said “you probably have way too much signal for one modem”. He was right. He tested the signal and confirmed that the signal was too strong going into the modem, with not enough room for the signal to be sent back out (that’s the best way I can interpret his explanation). He bypassed the amplifier with the coax cable, and installed a new modem just in case.

It’s been a week now and my internet hasn’t shut down once, and I’ve been able to sail for hours upon hours with no ship floating, teleporting or Hazelnutbeard.

Obviously, the people who are on the other end of the phone calls have no idea what they’re talking about when trying to solve your problems, and told me that from their end, my internet connection was perfect. Luckily, this tech seemed to know the problem just by looking.