code:net disconnects are back
Been happening pretty regularly for the last 4-5 days or so... Load in, start a game, pickup a handful of purple items, then ohhhh why cant i pick up this ammo CODE:NET Always seems to happen whe...
Forum Discussion
EA_Kent
Community Manager
Community ManagerHey all.
I know that the Code:Net errors definitely can be frustrating to deal with. Errors like this can come up for a lot of different reasons, so it can be tricky to narrow down what exactly might be causing it. Each situation is unique, so there may not be one specific, definite fix.
A good place to start troubleshooting this would be with the basic connection troubleshooting steps over at the EA Help website. It's also a good idea to check out the more platform-specific steps there as well, depending on which system you're using:
Also, if you can I'd recommend adding your information to this thread as well: https://answers.ea.com/t5/Technical-Issues/Code-Leaf/td-p/7977450/page/38. This error is something we've been gathering information on for a bit.
Thanks!
/Kent
@EA_Kent Yeah, not going to troubleshoot my PC for a server side issue. I was grouped with 2 people and in discord w/them, we are all from different geographical regions running vastly different hardware specs. We ALL THREE code:net disconnected at the same time from a game. This is server side, and if you'll come out and say 'does anyone want to help us playtest fixes for our buggy servers?' THEN I'll spend my time on this issue. Until then, I'm not troubleshooting my rig for YOUR server issue.
- EA_Kent
The Code:Net error is something that came up in the past, and was addressed by the Apex Legends team a few months ago:
https://trello.com/c/sknJsPvd/12-disconnects-caused-by-codeleaf-and-or-similar-errors
I understand where you're coming from, but I've seen cases where troubleshooting has fixed issues like this before in the past, but like I mentioned before every case is different. Unfortunately we can't always just point to one step and say "this is the solution" when it comes to disconnections like this.
If you've run through troubleshooting steps already and are still running into the same problem, please post your details at the thread I linked above to add it to the investigation.
/Kent
- @EA_Kent "every case is different" is all well and good, except in this instance literally you had an entire group of 3 people where the ONLY commonality is that we were in the same game/on the same server. Literally at the start of EVERY match I type "let's see how long we can go without a code:net" and at LEAST one of my team mates will say "yeah, I've been having those issues for a week now too. If a MINIMUM of 2/3 of each team is having these issues, then the single point of failure is the server side infrastructure. Could be their connection, could be their CPU, no ideas there, but the facts remain that the only single point of failure is server side.
Just because the code:net was addressed in the past doesn't mean a new patch didn't re-introduce it. As an IT professional that has done troubleshooting for 20+ years now, I assure you to sit here and ask the end user to troubleshoot an issue that affects a LARGE portion of the playerbase is going to QUICKLY erode any goodwill you have in the community. It doesn't make sense to pretend that 2/3rds of your playerbase needs to fix their computer when they are all experiencing the same error message/symptoms. How many people have get "CODE:NET ERROR" When they land on train? its happeing so much that that should be fixed!
What the “code:leaf” and “code:net” Apex Legends Error Means
Essentially, both the ‘code:leaf’ and ‘code:net’ errors are related to servers. The ‘code:leaf’ Apex Legends error means that the game asked to connect to a server and the server never sent a response. On the other hand, the ‘code:net’ error means that the game was on a server which suddenly became non-responsive.
SpoilerIn fact, they’ve been in the game since launch, but until recently starting becoming daily problems.- @EA_Kent So, guess how many code:net issues I've had today? Zero! Guess what I did to fix it? Not a DAMN thing. Tell the server/code/whoever fixed it on your end guys to keep at it. I've had a few lag spikes that made me THINK I was about to code:net, but then the server *didn't* crap the bed and kept on going.
Interresting! Did they find the problem?
I tried following steps so far (according to workarround list from June!):
checked my router firmware - It's up to date
Restarted router - still DCs
changed DNS servers in my network-adapter fromm automatic to google - still DCs
excluded Apex Legends and Easy Anti Cheat from firewall and virusdetection - still DCs
restarted router (unplugged power cable 10 minutes) - still DCs
tried London server - still DCs (like Frankfurt 1+2, Belgium 1-3 and Amsterdam)
tried DNS flush (deletes DNS cache) via command console - still DCs
repaired installation of Apex LEgends - still DCs
Yesterday evening I started Origin and Apex Legend as Admin.
I had a 3 hour session without DCs...
Gonna repport how it works today!
Featured Places
