State
Hello Bohemia Interactive Support Team,
I am writing to demand a real solution to a critical issue with DayZ on my PlayStation 5. I have been completely locked out of the game for 15 days straight, facing the 0x00010001 error code on startup.
Read carefully: This issue occurs across ALL regions and ALL servers (both Official and Community servers).
I have already exhausted every possible troubleshooting step on hardware, software, and network levels. Do NOT send me a generic, copy-pasted troubleshooting response telling me to restart my router or clear cache. Here is the full log of what has already been done and proven:
Timeframe: The issue has persisted for 15 continuous days without a single successful login.
Game Re-installation: Completely uninstalled and reinstalled the game twice.
Console Maintenance: Cleared the PS5 system cache, rebuilt the database, and restored PlayStation Network (PSN) licenses multiple times.
Network & Router Overhaul:
Assigned a static local IP to the PS5.
Bypassed firewalls by putting the console in DMZ mode on the router (TP-Link Archer C50).
Released and renewed the WAN/Dynamic IP address.
ISP & Network Isolation (Definitive Proof): Tested the game using an entirely different network provider via a mobile cellular hotspot. The error persists identically. This 100% rules out my home ISP, local routing, or regional blocking.
Account/Server Scope: Tested across all available regions and server types (Official & Community). All other online multiplayer games and PSN services work perfectly fine.
Since local network variables, ISPs, and client files have all been completely ruled out, this is clearly a persistent backend desynchronization, auth token lock, or profile-level bug tied to my account on your servers.
I need a real investigation and a solution to fix my backend profile status, not generic advice.
Thank you, and I expect a prompt escalation of this issue.
Regards, Bogdan.
Game Maintenance: Completely uninstalled and reinstalled DayZ on PS5 twice.
Console Storage & Software: Cleared system cache, rebuilt database, and repeatedly restored PSN licenses.
Local Network Setup: Configured a static local IP address for the PS5.
Firewall & Ports: Placed the console into DMZ mode on the router (TP-Link Archer C50) to bypass all local blocking.
WAN / IP Cycling: Released and renewed the dynamic WAN IP address on the router multiple times.
ISP Isolation: Tested the game via a completely different network provider using a mobile cellular hotspot (the error remained identical).
Scope Check: Verified that the issue persists across all regions, all servers (both Official and Community), while all other online games and PSN features work without issues.
Backend Profile & Auth Reset: A manual reset or re-synchronization of my DayZ player profile and authentication tokens on your servers to clear the stuck session causing the 0x00010001 error.
Server-Side Authorization Fix: Investigation and clearing of any ghost locks, corrupted character states, or erroneous database flags tied to my account that prevent connection to all regions and servers.
Direct Escalation: Escalation of this ticket to a senior technical support engineer or database administrator, bypassing standard tier-1 automated responses.
Activity
Hello.
As mentioned in the other ticket you have been active on - this is unrelated to backend according to the dev team.
There is nothing else I can do for you unfortunately
"Hello.
This was further investigated by our programmers. From what we can see, the issue is very likely not backend related. If this were an issue on the backend side it would return a different error. 0x00010001 (“server is unreachable”) error is related purely to the client connecting to the server and that connection works entirely without the backend. The only thing we can suggest at the moment is to have an IT specialist to help you troubleshoot and fix the connection issue."
Who should I contact? If the block is most likely in my region... Odessa, Ukraine. I just don't understand where to look for a solution... It's not even the ISP. I've confirmed that. It's the game itself that's blocking my access! My other games are fine. I want to buy more of your games, but what guarantee do I'll be able to play them properly? Could you find a way to fix DayZ? Maybe reset my account, my character somehow... I seriously created five accounts to try and fix it, and nothing worked... What should I do? What can an IT specialist do?
Hello. I performed additional network diagnostics from a Windows 7 laptop connected to the same Kyivstar home Internet connection/router as my Xbox Series X.
I compared a DayZ EU server that I can successfully connect to with a DayZ EU server that consistently returns 0x00010001 (server is unreachable).
1. Working DayZ server
IP: 31.214.158.208
Port: 11100
The server is accessible from my Xbox and I can connect to it successfully.
ICMP ping from the laptop: 4/4 replies, 0% packet loss, ~229 ms RTT.
tracert 31.214.158.208 reaches the destination successfully.
2. Non-working DayZ server
IP: 195.82.158.114
Port: 11000
The Xbox consistently fails to connect and returns 0x00010001.
ICMP ping from the same laptop: 0/4 replies, 100% packet loss.
tracert 195.82.158.114 reaches a Nitrado node in Frankfurt (80.81.194.168), after which all subsequent hops time out until the end of the trace.
Both tests were performed from the same physical network, same router and same ISP (Kyivstar). The difference is therefore reproducible when comparing an accessible DayZ server against an inaccessible one.
I understand that ICMP filtering can cause ping/traceroute timeouts and that this alone does not prove that traffic is being blocked. However, the combination of:
Xbox → 0x00010001
same Kyivstar connection → 100% ICMP loss to the affected IP
traceroute stopping after a Nitrado/Frankfurt hop
while another DayZ EU server is reachable from the same connection
suggests a possible routing/reachability issue between my ISP and specific DayZ server IP ranges, rather than a general Xbox Network or DayZ backend problem.
Interestingly, both IPs appear to be hosted by marbis GmbH / AS199610, so the issue may be related to the path to a specific destination IP rather than the hosting provider as a whole.
Could the development/network team please check whether 195.82.158.114 is reachable from the relevant infrastructure and whether there are any known routing, filtering, firewall, or connectivity issues affecting connections from Ukrainian ISPs/AS15895 (Kyivstar) to this destination?
I can provide the complete tracert output/screenshots and additional server IP comparisons if required.
Hello,
I contacted my ISP, Kyivstar, regarding this connection issue. They confirmed that Kyivstar does not block access to the game or its servers.
I personally tested the game on PS5 using my Kyivstar internet connection, and the same issue occurs there.
My friend also tested the same servers on Xbox, and he has exactly the same problem.
The issue mainly affects nearby European DayZ servers. For example, we cannot connect to 195.82.158.114:11000 and receive error 0x00010001. At the same time, some other European servers are accessible(On XBOX, not ps5!!!), although some have extremely high ping.
This makes it unlikely that the issue is specific to one console or my individual Xbox. The problem appears to affect connections to certain European DayZ servers.
Unfortunately, I don't have access to a PC, so I cannot run tracert.
Could you please check whether there may be a regional/IP restriction or a routing issue affecting connections from Ukraine to these European DayZ servers?
Thank you.
Hello.
While your ISP might not be actively blocking the game or the servers there is a chance something is set up incorrectly. Since as you are mentioning, this affects multiple users by this ISP while other users do not experience this issue.
We would try to contact the ISP that while you are able to connect to certain IP's(make sure to provide the IP that works) you are unable to connect to specific ip's/cannot ping them (and include those IP's you cannot seem to be able to connect to)
You are not signed in. Please sign in to see more details and to reply.
State