Reviving this discussion because the other thread was shut down for replies due to being old. When trying to connect through "online play." I can't get in and get the message that "Your account settings has changed. Please connect again now." I just bought the game and set up the link to the EA account to my nintendo account. I tried unlinking and relinking. I tried resetting the time and clearing the cache. I tried using a manual DNS. Nothing has worked so far.

@EA_Cath Hello! Thank you for responding. Both me and my partner have tried that and we’re still getting the same error.

@MommaParham @2c60f673e406b844 @ness568 Hey everyone, apologies for the delay. This topic kinda slipped out of my sight.Are you guys still experiencing this issue? If so, are you all playing on Nintendo Switch?We've been seeing more recent reports and hopefully we should have enough examples to raise this bug to the studio, but I want to make sure this is still happening for you.

can you please do your job and come here and help us instead of dropping a useless method that does nothing and disappears for a long time? This is why I continue to hate your company, and your products

EA_Leeuw, I also began running into this issue as a full block on April 11th 2026 and I decided to do a more detailed analysis of the traffic over my network to have a better understanding of the root cause of the issue because it occurs on both Home Networks and Hotspots intermittently while happening much more often on non-hotspots (as observed/noted previously).BACKGROUNDI ran into the 105-80190000 error from the first day I bought the game in mid-late February 2026, but it would typically let me create a session after rebooting my console 1-3 times while still using my WiFi, so I didn't think too much of it, but after I reached Chapter 6 I was unable to get past the error even after many restarts. This is what I've concluded from my analysis:This is not particularly a client-side network issue, or an ISP/firewall blocking the handshake; rather there is an issue with the response time of EA backend infrastructure and it should probably be escalated to your infrastructure or backend engineering team for review. MY SYSTEM INFORMATIONPlatform: Nintendo SwitchNETWORK DETAILSTo play the game I use an AT&T Router linking to Fiber InternetNAT Type: BAll testing was done using Raspberry Pi as an access point with an ethernet uplink/WiFi uplink to the same AT&T Router or mobile hotspot uplink also AT&T based. No changes were made to the network/firewall, all alterations to speed were run through the Raspberry Pi as it intercepted traffic and then forwarded it to the Mobile Hotspot/AT&T Router. Networks tested:Home ethernetHome WiFiiPhone cellular hotspot SUMMARY OF FINDINGSOnline session creation fails due to a race condition in EA's backend session preparation pipeline. The Switch reaches the Blaze session server and completes authentication faster than EA's backend finishes preparing the session. When the Switch presents its auth result to the Blaze Server, EA's backend is not yet ready to validate it, returns an unexpected response, and the Switch aborts the connection with a TLS Encrypted Alert.Artificially slowing the network connection (adding 30ms and 50ms and 75ms latency via Linux traffic control) improved the success rate from ~2% on base ethernet to ~40% with a 30ms delay added and then 100% with 75ms added. So higher natural/artificially added latency confirms that connection speed — not network configuration — determines the outcome. I ran 100 tests across the three network settings mostly with my natural ethernet based connection.Here's the breakdown: Notice that slower connections using a cellular/hotspot connection or WiFi work because they give EA servers time to respond when the Switch expects and create the session correctly. Ethernet connections were 100% successful with artificial latency of 75ms added, but it improved as more latency was added when it almost never worked with its natural low latency.RACE CONDITION EXPLANATIONThe bug is a timing dependency between two EA backend systems:1. The Blaze session server accepts the connection and begins session setup2. EA's auth backend (accounts.ea.com coordination) prepares the session credentials in parallelOn low-latency connections the Switch completes its auth steps and returns to the Blaze Server before the auth backend finishes. The Blaze Server receives the Switch's auth presentation but cannot validate it because the backend preparation is not complete. It returns an error response, the Switch sends an Encrypted Alert, and the session fails.On high-latency connections the additional network delay gives EA's auth backend enough time to finish. The Switch's auth presentation arrives after the backend is ready, validation succeeds, and the session completes. This is consistent with all observed data across 100 captures.EVIDENCE AVAILABLEI have the following available to share upon request:100 packet capture files (.pcap and .csv) spanning failed and successful sessions across all network typesCaptures with and without artificial 30ms, 50ms, 75ms latency delay confirming the timing hypothesis.Timestamped session log showing outcomes across multiple days and times of dayMore detailed statistics that show which connection speeds work better than others. I am happy to provide any of these to your engineering team, but they may also be able to reproduce the behavior detailed above on their own just from this information. Thank you for your time and attention to this. I hope this report helps your team identify and resolve the issue for all affected players. Edit- Adding some detail about the flow of network traffic during the failures/successes: DETAILED FAILURE SEQUENCEEvery failed session follows this exact sequence:1. Switch queries spring18.gosredirector.ea.com and is assigned a Blaze Server 2. Switch initiates TLS connection to assigned Blaze server — handshake completes successfully3. Initial Application Data exchange occurs between Switch and Blaze Server4. Switch simultaneously contacts accounts.ea.com, qoscoordinator.gameservices.ea.com, Nintendo auth servers, and other EA services during a multi-second gap5. Switch returns to Blaze Server with auth result6. Blaze Server responds with Application Data7. Switch immediately sends a TLS Encrypted Alert — indicating it received an unexpected or invalid response8. Switch sends TCP RST to Blaze Server9. Blaze Server sends FIN ACK (terminating the connection to the Switch) 10. Session creation fails and players get the "Account settings has changed..." error message.In successful sessions, Step 7 does not occur, instead, the Switch receives a valid response and the Application Data exchange continues for ~2-3 additional seconds until the session is fully established.Also, "Blaze Server" refers to any of the following 4 servers as the Switch may be assigned to any one of the four after being redirected by spring18: itt-prd-blaze-app-01.ea.comitt-prd-blaze-app-02.ea.comitt-prd-blaze-app-03.ea.comitt-prd-blaze-app-04.ea.comThese servers are present across failures and successes pointing towards this being a backend timing issue, and not a server health issue as they wouldn't work at all if there was a health issue. They just need more time than our connections give them to handle the authentication/session creation correctly.In my experience with this error, the manipulation of the speed of the network proved to be the only fully reliable way to avoid the issue. Outside of my recorded testing I had more success creating a session with my phone's hotspot, but like others, it still doesn't work some portion of the time because the speed of the network is variable, so without forcing it to be slower you're just gambling with better odds when using a hotspot...it seems like a fix but it is actually just masking the issue.Please help get this information into the right hands, so we can get past this error once and for all.Edit - Here are two links to others that've used this information to get past the error message on Windows using Clumsy: Jacklib: It Takes Two Nintendo Switch Error - 105-80190000 | EA Forums - 13181754ThotSlayerKaiYu: It Takes Two Nintendo Switch Error - 105-80190000 | EA Forums - 13181754

Hey @36d672336a1a76bb Thanks for this update, if the previous steps I've shared haven't help can you confirm by trying the following and checking if the same message pops up? Update switch to the latest version Change switch time settings to synchronous and restart the switch - https://www.nintendo.co.uk/Support/Nintendo-Switch/How-to-Change-the-Date-and-Time-1494763.html

[Known Issue] It Takes Two on Nintendo Switch: Online Play Error 105-80190000

267 Replies

zngotnfif1tj
New Novice
4 days ago
Thank you for the response! For the record, this thread has identified the main problem. If your internet is too fast, the connection speed to EAs servers is too fast for the authentication to happen.
Adding a 100 Ms delay to your internet connection has resolved it in every time for both myself and the friend I've played with like the post shared earlier up.
But this delay should be fixed on the EA server side. Please make sure your dev team sees that example of how to fix it to help them debug what's going on with the servers!
moonpie0808
Seasoned Newcomer
6 days ago
My friend and I connected on Aug 10 & 11, but have failed to connect since Aug 12 even after trying all fixes. We enjoy this game and hope this minor issue won’t disappoint players. Please resolve this bug as soon as possible.
EA_Leeuw
Community Manager
6 days ago
We’re sorry for the extended interruption affecting players who are unable to access online play in It Takes Two on Nintendo Switch, including those experiencing error 105-80190000. We understand how frustrating this is, especially for players trying to enjoy the game together with a friend or partner.

Our development and service teams are actively investigating the issue to understand the cause of this behaviour and determine an appropriate resolution. We recommend continuing to check the official channels for further updates as our investigation progresses.

Thank you for your patience, and the reports and information you have shared will help us in our next steps. We apologise again for the disruption and appreciate your understanding while we work to address the issue.
zngotnfif1tj
New Novice
7 days ago
Not gonna lie, I found it hilarious when the Switch 2 version of It Takes Two leaked. I thought of this thread and how that brand new version will likely have the same issue with EAs servers and stink from the moment it's released 😆
zngotnfif1tj
New Novice
7 days ago
The only thing that consistently worked for me are the later comments about adding delay to your internet connection when playing the game. There are instructions on how to do it in Windows at the end of the thread.
Train0fThought
Seasoned Newcomer
8 days ago
EA_Leeuw I have tried everything in your pinned in addition to clearing cache, save data, unlinking and relinking on both ends, rebooting my switch, rebooting my router, testing it two states away, everything. This continues to be an ongoing issue and needs to be escalated.
rufiopbkimchi
Seasoned Newcomer
8 days ago
I have this same problem. I was told to post here to get support from the Community Managers. I see they have responded but their fixes have not worked. My ticket has been open for a couple of days and would appreciate some support.
gorsyMChorsy420
Seasoned Newcomer
9 days ago
This happening to me and my girlfriend too. Absolutely insane a billion dollar company can’t fix a bug that is two years old. Already called my bank saying I bought a faulty product and can’t use it. I suggest everyone does the same. I paid for the game being told I can play online and can’t. With no answers if it will ever be fixed. Extremely un-professional. Not surprised this company has been failing.
alfruiz97
Seasoned Newcomer
13 days ago
Still having the issue on Nintendo Switch.
erikaaa222
Seasoned Newcomer
16 days ago
this is ridiculous, this error is still happening to so many users YEARS later. if there isnt s resolution provided im calling my bank and reporting the game