Uploaded new 1.23 exp & tried to log in to DayZ EU - DE 8350 (Exp)
DayZ failed to log in
tried other servers, including Livonia, same issue
Deleted exp & reloaded - same issue
Uploaded new 1.23 exp & tried to log in to DayZ EU - DE 8350 (Exp)
DayZ failed to log in
tried other servers, including Livonia, same issue
Deleted exp & reloaded - same issue
Status | Assigned | Task | ||
---|---|---|---|---|
Acknowledged | None | T175914 DayZ 1.23.156797 EXP failure to connect 0x00020009 | ||
New | None | T176115 Connecting Failed to Join Server 1.23 |
Also having the same issue, Tried to join both Community and official servers, same result
So I just watched someone change servers, instantly connected. Went back to the server they were playing, Connected..
Maybe an issue with profile cached locally??
Update: I was able to join a EU server (it moved my saved geared character to the coast) but still cannot join any US servers afterwards, I heard that might have been a quick fix, but no so for me, will try other EU servers to test!
Same, still no fix?? I've tried over 10 different Community and Official No luck, no updates?
I spammed joined about 20-30 times and eventually mine worked. Haven't logged out yet to see if I can get straight back in
restarted the PC and it worked.
EDIT: not working anymore. Yesterday, the only official server I could join had a red server icon for desync. Then I joined a community one. Now not even that one works. I can't join anything...
Happening on console community servers, not just exp. Ps5, community server. Have reset console and tried to switch to alt. Other community servers still work fine.
trying to connect this morning . . .going through my rpt & log files under local
rpt
log
Dont know if this helps .. .
I have this issue too as well as a number of players trying out Exp 1.23 (but don't use the tracker...) this is both official and community Exp servers
For me I tried reinstalling EXP, PC restart, router restart, clearing out the DayZ Exp profile files and Steam verify integrity including changing by Steam download region... none of that helped.
What did happen is after many many join attempts (i'd estimate 60-70) I did eventually join an official Exp 1.23 server and was able to play for 1hr+ when I left I tried to rejoin the same server within 1min and got the same error connection issue again.
Hopefully that helps a little..
I run Windows 10 (fully patched) with high PC hardware specs fyi, the usual Windows Defender AV nothing out of the ordinary
I tried joining de 3536 and got that error at first attempt, clicked on server's and found that server again and managed to join with no issues.
The official had only around 20-30 and seemed to be stuck at 32-34 pop.
During the 30 min I played there was orange and red server icon and gameplay seemed a bit laggy.
So I decided to try the community server's and they seemed to be doing better with no server icons and had over 40 player's on.
Never got the connection error on them either.
Later on I tried the de 3536 and got only the connection error, tried over 60 times, never managed to get into that server and the server pop showed 32 to 34 pop all the time.
Got into the official first-person Livonia on first go that had 0 pop at that moment and lower pop 3rd person as well.
Seemed to me for de 3536 official that when population was around 32-34 it was nearly impossible to join.
Same connection error as most people , in your dayz exp 1.23 tweet you mentioned full wipe across all exp servers , currently DE3536 1st person official exp has not recieved a wipe although im grateful for still having my loot im unsure if this is related to the connection issue .
Having this same issue since yesterday when I first started trying to join EXP. Also tried on community servers with same result. Tried all official regions and various community servers with varying levels of ping
Same on my end. Manage to occasionally get into Official servers, but there is a red server icon,
Can occasionally get into community servers
Not had any luck what so ever joining any EXP server (official or community) since 1.23 dropped. 0x00020009 error or 0x00010001 every time.
cannot join any official EXP servers. Of note, I created a local LAN server and connect to it on LAN, but not public IP. I've created many servers, so this should be no different.
Same issue as above posters. either 20009 or 10001. Community servers have not been a issue, just official. Can you kill my character and see if having a fresh homie solves it? i would rather play then not.
Still getting this error on ALL Official AU and SG Experimental Servers.
Two Community servers are allowing me to load in intermittently but after a restart it may throw up the Connecting Failed 20009 error. Sometimes I'm able to switch between the two community servers from in game server browser, but then I cannot switch back to the previous one without the error.
Same issue been trying to connect all morning.
Multiple steam restarts
Multiple pc restarts
And verified files.
I tried using the game menu server browser that also didnt work.
did everything everyone could think of.
there's no way for me to connect to ANY of the exp servers, official, community etc.
0x00020009. It's what nightmares are made of.
Multiple steam restarts,
Multiple pc restarts,
verified files.
I tried the game server browser,
reinstalled, reset router,
tried different hard drive,
tried spamming different servers
tried joining all the servers,
community and offical.
Europe and US.
Tried deleting my custom user files in the my documents folder,
tried editing them.
what did i do to deserve this torture?
sentenced to live without dayz exp.
cruel.
fix asap plz.
Hey bro, haha.
I also tried all the connections to the Experimental official servers.
I could only connect to the EU-UK01 server.
I had no problem with the community servers.
Of course, I have rebooted the router, reinstalled the game and deleted the cache.
From Japan.
When this happened to me, I "created a new character" and was then able to connect to the experimental server I am playing on.
{F3167140}Hello,
I was able to experiment this bug, however the solution I found to solve the problem was to :
C:\Users\<user>AppDataLocalDayZ Exp C:\Users\<user>d\AppData\LocalDayZ Exp Launcher
In my case, it worked 3/3.
I can connect to UK 0-3. i don't know what is different about that one but i go right in. Same character. Tried to go back to either LA server and back to errors.
I can now connect to the public exp server - DayZ EU DE 8350
Will try some private & other servers later
Thanks
I havent created an new profile or done any major changes/deletions to my profiles. I just logged in as per normal, and the system accepted & I was in game on this release.
my character is fuly loaded from 1.22 with no issues ...
so far everything is good. . .
Solution for me was now to delete everything in
"C:\Users\_username_\Documents\DayZ Exp"
and then I started the game and was able to connect!
Same issue :(
I used to play it but now I can't play it, is a developer not solving these errors well?
It may be important to note that I run on the game (normally, quite well) under Linux.
Ultimately, I found that specifically using the launcher fixed the issue for me. I had been using the launch arguments "-nosplash -skipintro -noLogs -nolauncher", which people often use under Linux to improve their experience/compatibility. I finally thought to remove those. Upon doing this, the launcher subsequently complained about having corrupt settings and having to restore them - sorry, really wish I saved the specific error there! In any case, whatever the launcher "repaired" fixed the issue for me. I was able to join an official server, and from that point I was able to stop using the launcher again. To me, it seems quite likely some initialization or validation problem is more to blame, that anyone's internet connection...at least in many situations. I'd say JappeHallunken's fix backs this up too.
Note that even a full removing all Steam workshop content and removing the game from my library then reinstalling it did NOT fix this for me, nor did validating files, and so on. The only thing that finally got me there was to use the launcher and let it do whatever it had determined was needed to get it working again.
IMHO, the connection initialization code seems to need a bit of TLC to better identify the underlying cause of the apparently varied problems that can cause a connection failure.