Forum Discussion
thats sucks ! every day same * story ,why they dont fix it
Hey 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
- 6 years ago
Hi Kent,
I know your reply is likely a canned response, but thought i would try anyway. I play a lot and this last week the pc disconnects are absurd. Ive spent money on the game so not a "freeloader" either. There is clearly something wrong on the server side, my pc is gaming soley, hell im sending this on my phone because i dont surf on my gaming pc. Its not client based, i just want to know you guys are acknowledging the problem and working to fix it.
Thanks,
-Tom
- 6 years ago
@EA_KentI assure you it is EA/Respawn sided. When myself and my two squad mates (who are on discord) that live in different regions of the US, use different PC's, and different ISP's all 3 get code:net at exactly the same time in the same match, I assure you it's not the end users. Many of the people in our discord have opted to playing different games until we get at-least an acknowledgement that there are issues. It happened a few months ago, you guys applied some fixes, and It was fine up until about a week ago and suddenly its like wild fire again. The game is unplayable. I'm tired of spending several minutes between partying, queing, getting in, slow character selection screen (seriously, why cant I just straight que as what I want to play?), waiting for the stupid cargo bot to swing around and the hidden count down to tick, drop, get a gun, kill 3 then disconnected, no credit to dailies, xp, stats, etc. It's simply not worth the wasted time.
Might I add, there are several other posts in the forum that indicate various regions are experiencing this. I've tried on pretty much every US server in the list at the loading screen and have had the same results. Other people are complaining about it in other countries.
- 6 years ago@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_Kent6 years ago
Community Manager
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
- 6 years ago@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.
- 6 years ago
Originally, I never had any issues season 1 and season 2. This started around the halloween update for me. Code: nets consistently at legend select and main menu. It is still recurring. I've tried all of the troubleshooting you've suggested. Honestly, I'm going to give up at this point and go back to other games. Which, coincidentally, all work fine. Only apex has an issue. Don't try to tell us that it is our fault. It's ridiculous.
- 5 years agoFor about a week now since I've been trying to play, the code:net error is back and I have a LAN cable connection cat-6 wiring. Also chnaged DNS setting to primary 8.8.8.8 secondary 8.8.4.4, powercycled internet connection, powercycled PS4. Still issues. Im in U.S. East location in Florida. Really wanting to see a fix. A bit fustrating and haven't purchased apex coins for the shop because of it. Please fix very soon.
- 5 years ago@gamegainz814 I get it as well have done everything they advised to do and have had 2 times on console where it said server shutting down
- 5 years ago
Its a joke dude I cant even play I haven't played since mid season 5 I know it's not my wifi I'm on lan cable I get around 400-433mbps it's a literary a joke the fact that they cant fix a stupid server side issue
- 5 years ago
Dear Kent, I an avid player who during season 4 started having these issues has quit the game. I've spent at least 500$ in game for cosmetics and played enough hours to be decent. I went through your websites "troubleshooting" options none of which worked your servers are blown and can't handle more than 5 or 6 people at a time these players winning almost every match. This error is causing way more issues than a "free" game is worth. Don't reply with standard answers tell the community how you plan to fix your problems with the server side.
- 5 years ago
problem with this statement... when you search for what code:net actually means you get this
"
Code net means you're having connectivity issues to EA servers.
Unfortunately, there is nothing you can do to fix the issue on your side. You need to wait for EA to deploy a hotfix on their servers, which would solve the issue. Still, you may restart your computer/console and your router.. it may solve the issue !
According to EA support, code:net happens when your connection to Apex servers expired or when the server stopped responding to your requests. This is a server-side issue, not a client-side one."so why are they constantly telling US to reset our routers and consoles when their own status page indicates that its THEIR problem...
- 5 years ago@VinnieMac_RgQt whatever gets you off the line.
- 5 years ago@creamonurstream I hate to go immediately there, I TRY to give them some benefit of the doubt... but this has been going on for too long. This server has got to be the worst set up mp server in a long time.
- 4 years ago
Changing severs has helped with error code:net even though I'm playing on severs with more ping and little laggy wish you could fix the severs that are close to me (Texas severs) thanks
- Midnight97464 years agoHero+@SEBASTIAN_BLAIR The game update from today has broken the game for many players, its even heavily reported on the down detector's website.