We are aware of and looking in to reports of players using Verizon and CenturyLink ISP that are unable to log in and are encountering “Backend Error - Error Signing In”.
We have identified that these two ISP’s and players based in Midwest US appear to be most commonly affected. However, the issue may extend to players in other regions, and possibly other ISP.
Please help us out by including the information listed below in your report:
When the Backend Error first began
Your Steam Name/ID
Your ISP
Your Region
Upload Console Log:
Press the Windows key + R
Enter %appdata% within the search input and select ‘OK’
Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
Upload here
We will be merging any related posts to this thread, and will post any updates regarding the issue here.
Everytime i get to menu to login (Processing Inquisitorial Clearence) Backend error non stop i have reset wifi and use direct plug in,i have verified files restarted pc several times and it wont work
Crash Report (If Applicable):
GUID: bac32552-5b5c-41a3-9ba0-22dac9ebeb0f
Log File:
Info Type:
Error Displayed (If Applicable):
Steps to Reproduce:
Mission Name (If Applicable):
Platform:
[Steam/Microsoft Store]
**Player ID:Dagoth Ur
**Approx. Time of Issue & Timezone:**5/20/2023 1.17pm mountain time .
Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)
Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]
Also i forgot to post some details this issue is constant it will not get past login screen without back end error i have also tried additional steps including vpn and darktides suggested methods for backend errors all hhave failed i even reinstalled for laughs and giggles and still to no avail.Also another note is that it did work the night prior to this original post no issues until what i posted above also i have done firmware and modum updates and still nothing this only is a issue for darktide, vermintide works
@Dagoth, @Hollyvvood
I’ve merged your posts here, as I believe you are both CenturyLink ISP users and that you are currently encountering this issue.
Unfortunately I have no immediate solution, but please be assured our Backend Developers are investigating to determine if this is an issue we can address our side, or whether the issue is out of our hands and with the ISP.
I am on Century Link, had the issue through the weekend, and solved it by disabling the IPv4 Firewall service on the ISP modem, which is an Axon C4000XG.
The commonality may be that it is the modem, or the firewall component that is causing this to be widespread, but without any particular outage. Other Steam games work fine with the modem’s default ‘low’ security settings in the firewall - as Darktide did previously. Something has changed.
I can also re-enable the firewall once I bypass the Backend Error and reach the character selection screen, and can then successfully play the game for hours without trouble. This makes me think the traffic is some piece of authentication.
A Darktide Steam Community post from back in Dec’22 included a list of UDP ports (you gotta scroll down a bit on the page) seen from Darktide via Wireshark while troubleshooting. One could conceivably add these to a rule allowing the traffic, but it does compromise some security by definition:
I tested the ports and it seemed to work, but disabling and then toggling back on the firewall is thankfully quick, and that’s what I am doing for the moment. No way to know exactly what caused this to occur (ISP modem update, game code, Steam servers), but I’d of course love some more elegant fix for the long-term. I hope this helps.
Saw some posts about disabling the firewall so tried that and it worked. Enabled port forwarding on the following which apparently Dartide uses. But that didn’t seem to work, however, if I connect right after enabling or disabling my ISP-provided router Firewall I am able to connect. Go figure.
I have a buddy suffering from this.
Can we get a definitive list from a dev of which ports+remote Steam and Darktide use
together? Including auth servers OFC.
Adding some info, in my opinion it seems to be a CORS related issue. Using the Store Plugin Website as an extra debug tool to watch the network calls I first see a Certificate Error, however I believe this isn’t the root cause. When I manually go to the website generating the cert error (https://bsp-cdn-prod.atoma.cloud/items/versions/76376/\[removed\].json) it says the website isn’t secure because of the certificate not being authenticated. Proceeding to the website anyway will make the browser cache the certificate. I can then go back to the Store Plugin Website and it returns the error below to which I believe is the root cause.
Access to fetch at ‘https://bsp-cdn-prod.atoma.cloud/items/versions/76376/\[removed\].json’ from origin ‘https://accounts.atoma.cloud/’ has been blocked by CORS policy: Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.
bundle.js:30294
What I think is happening on the store website is the same as the login failure, it attempts to go to the same GET url and is blocked by the router’s ipv4 firewall rule, the browser thinks it’s a Cert error at first because of cascading exceptions being thrown.
So this is interesting. Saw a reddit post of someone logging into their Century Link modem and disabling the Cyber Security state. to fix it.
Note this is not the modems IPv4/6 firewall.
Tried it myself and I can confirm, with Cyber Security state. on I get a Backend Error. With it off I don’t.
Yeah saw that post too, it seems it’s the embedded McAfee Security software embedded in the router/modem that may be the culprit, there was a McAfee ref in my buddy’s error and some posts on the web such as
Centurylink customer here w/Zyxel modem. Disabling cybersecurity feature also fixes my backend error problem. Able to log in for first time since 20th of May.
