UPDATE 23/05 [image] KNOWN ISSUE: Backend Error Affecting CenturyLink & Verizon ISP Users Technical Support Hi all, We’re still currently investigating. One of our backend developers has asked if anyone still affected by this issue could please try the following - Set your DNS Servers on your PC to Google or CloudFlare running without VPN - and to check if this resolves the issue. This isn’t a long-term fix, but the results of this will help us to narrow down the issue slight_smile Here’s a CloudFlare guide: https://1.1.1.1/dns/ Thanks in advance! UPDATE 26/05 [image] KNOWN ISSUE: Backend Error Affecting CenturyLink & Verizon ISP Users Technical Support Hi all. Just chiming in to let you know this is still very much a priority for our Backend Engineers and we’re implementing additional logging to help pin down the issue. UPDATE 26/05 [image] KNOWN ISSUE: Backend Error Affecting CenturyLink & Verizon ISP Users Technical Support For CenturyLink customers, we believe this issue is the result of embedded McAfee router security as mentioned in @gpkgpk’s post above. You may also encounter this error if you’re using McAfee on your PC, so please check whether you have any McAfee services installed. We’re in contact with McAfee, and looking in to whether Verizon is also using the same embedded router security. UPDATE 26/05 [image] KNOWN ISSUE: Backend Error Affecting CenturyLink & Verizon ISP Users Technical Support Amazingly, we have received an almost immediate response from McAfee who will be removing us from their list of blocked domains in the coming hours. Keep us posted! 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.

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 [image] How to Disable CenturyLink McAfee Cyber Security Warnings Many CenturyLink users have discovered that attempting to visit certain web pages and websites leads to a giant McAfee cyber security “warning” message that says something to the effect… They have a partnership https://www.mcafee.com/support/?locale=en-US&articleId=TS103109&page=shell&shell=article-view Other reddit post Reddit - Dive into anything intersting metnions of dns and turning CyberSec off [image] strenif: 1.1.1.1 to no effect. From reddit years ago: Cloudflare dns or opendns. I prefer cloud flare. Log into modem at 192.168.0.1 to change it. On some of the older modems u gotta use 1.0.0.1. 1.1.1.1 doesn’t work for some reason. So just put 1.0.0.1 for both of them.

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.

Been getting this error for a few days, don’t remember the exact date but no more than 5 days I would think. Tan Stewie CenturyLink Midwest USA Switching the DNS helped for one day… now it no longer works. Can’t even use VPN as I can get to the character select but then get 4008 errors trying to load in. This is unacceptable.

Backend Error when I hit spacebar to “Processing Inquisitorial Clearance” Issues started on 5/21/2023 The Broodwich - 76561198009616863 Verizon FIOS US-North East console-2023-05-25-00.37.10-8e77a5ca-f0e4-4417-aee8-b23c8039d497.log (33.0 KB)

Been having this issue since 5/21 have 400+ hours on this game and never had any issues until now. Havent been able to play since. Tried everything including the DNS, verifying game files, reinstalling, moving to a different drive, flashing router, resetting router, reinstalling network drivers etc. Just hope this is resolved by the content drop, has been an absolute buzzkill all week. Backend error - Error signing in at “Processing inquisitorial clearance” Started 5/21/2023 Whappen412 - 76561197960545169 Verizon FIOs US - North East console-2023-05-21-07.40.46-f4396d5f-827a-4256-b594-f0a456a183f7.log (47.1 KB)

I was peparing a error report when I read about this fix concerning the backend issue with centurylink customers & I fall in that catagory. I’ll paste the text here. It worked & now I have no game problem but I have a less secure router now. Heres what worked: 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.

When the Backend Error first began may 22 2023 Your Steam Name/ID 76561199230351719 my username is sethisahuman Your ISP Centurylink Your Region Southwest Region US Upload Console Log: console-2023-05-26-00.09.08-70f4eb46-9ff5-46d3-aa1b-e0a4830fffd1.log (40.7 KB)

It does work. I can confirm that. Is the cyber security important?

KNOWN ISSUE: Backend Error Affecting CenturyLink & Verizon ISP Users

Warhammer 40,000: Darktide Technical Support

FatsharkJulia May 26, 2023, 9:01pm 33

Amazingly, we have received an almost immediate response from McAfee who will be removing us from their list of blocked domains in the coming hours. Keep us posted!

4 Likes

Topic		Replies	Views
KNOWN ISSUE: Backend Error After Nightmares & Visions Update Technical Support devpost	96	3725	July 5, 2025
KNOWN ISSUE: Backend Error Technical Support devpost	583	38186	May 25, 2026
KNOWN ISSUE: Backend Error After No Man's Land Update Technical Support devpost	100	5742	May 16, 2026
Backend error for days Technical Support acknowledged	12	202	October 6, 2026
Backend Error signing in - September 14, 2026 Technical Support acknowledged	12	286	September 23, 2026

KNOWN ISSUE: Backend Error Affecting CenturyLink & Verizon ISP Users

Related topics