Right present there’s a Halloween lawsuit moving for Overwatch 2, but a just magnitude of players are facing a antithetic benignant of terror: A antecedently known server mistake with the codification “LC-208” appears to beryllium disproportiantely hitting players aft the astir caller update.

While server and transportation errors often hap for online games, “Overwatch 2 Console Error LC-208” is presently plaguing a ample fig of players connected console, preventing them from connecting to servers and playing the game. Blizzard has its ain steps for moving astir this issue, arsenic it’s been astir since the motorboat of the game, though not successful specified numbers. Until Blizzard issues a broader connection oregon further fix, players person been discovering quirky, unexplainable ways to hole it, involving signing successful connected PC archetypal oregon loading into the game’s firing scope and quitting earlier hitting matchmaking, though these aren’t needfully bullet-proof prescriptions.

Kotaku has reached retired to Blizzard for remark but didn’t perceive backmost anterior to publication.

Since yesterday’s Halloween update, hunt results connected Twitter, Reddit, and adjacent Overwatch 2’s ain forums person started turning up countless reports of players not being capable to participate the game. The problem, fixed the mistake code’s info, seems to deed console players only. Anecdotally it seems to beryllium hitting PS4 and PS5 players the most, though galore Xbox players are reportedly facing the mistake arsenic well.

A main thread for the LC-208 issue successful Blizzard’s authoritative forums, with astir 300 replies and implicit 2,500 views, starts with “LC-208’d aft the Halloween lawsuit update. Never had an contented with this before. Can’t get into the game.” “I tried everything to hole the Login Error LC-208” Twitter idiosyncratic Phish (no, not the band) says. “I person signed retired of my conflict nett account, restarted my [router], restarted my game, utilized a antithetic wireless connection, tried utilizing ethernet, and redownloaded the crippled and I americium inactive getting LC-208.”

They’re not alone, arsenic countless tweets and Reddit threads work similarly. Some person recovered non-optimal workarounds. Twitter idiosyncratic hatsune niiku reports bypassing the LC-208 mistake connected console by entering the game’s firing scope connected PC, closing the game, and past logging successful connected console. “Worked for maine conscionable now,” they say.

Sadly, not everyone has a gaming PC astatine the acceptable to effort this out, nor is it an existent hole for the problem. Blizzard recommends the pursuing steps for solving LC-208 error. Hopefully it volition enactment retired for you:

If your console relationship is linked with your Battle.net account, you request to person a BattleTag. If you person a BattleTag but your accounts are not linked, travel the transportation steps linked beneath to resoluteness the error.

Note: If your Battle.net relationship is connected to your console account, disconnecting it and reconnecting tin resoluteness the error.

1. Check your web configuration to find immoderate issues with your firewall, router, oregon larboard settings.

2. Reset your web devices to marque definite your router hasn’t go flooded with data.

3. If you’re utilizing a wireless connection, optimize your net transportation to regularisation retired a transportation issue.

4. Run your console’s built-in transportation trial (Playstation 4) (Xbox One) (Nintendo Switch).

5. Use your console’s net browser to tally a Looking Glass test. This volition assistance find if the occupation is betwixt your console and our servers.