KNOWN ISSUE: Backend Error

If you are experiencing Backend Error in Darktide, please see the solutions in the article linked below:

If none of the solutions above have worked for you, please help us out by including the information listed below in your report:

Issue Description:

Your Region & Name of ISP:

Name of Anti-Virus/Firewall Being Used:

[Steam/Microsoft Store/Xbox]

Player ID:
[Steam ID/Steam Profile URL/GamerTag]

[PC] Upload Console Log:
[Instructions: How To Provide a Crash Report, Console Log, or darktide_launcher.log]

Existing reports may be merged here, to help us keep track of the issues being reported.

1 Like

Ive had these errors since the first closed technical test. I would finish the download on steam and launch the game only to be met by backend error after pressing any button at the menu screen. After trying many steps including verifying the game cache, running in admin, reinstalling, etc, I found using a vpn cleared the issue. I would like to not have to use a vpn to play the game though. If it helps at all I live in the northeast of the united states

Spicysteeeve Steam Community :: SPICY STEEEVE
11/17/2022 1:30pm EST

editing this to say that a suggestion below fixed it:
Changing my dns server to googles’ ( or allowed me to play with no vpn this time

I have had this issue sine the last closed technical test, when I start up the game I get a backend error after it asks me to 'Press any button.
This only disappears if I have a VPN turned on, and it would be a hassle to need one on every time I want to play.

Platform: Steam

Profile URL: Steam Community :: Flameit

Time: 11/17/2022 07:40 PM CET

Console Log:
console-2022-11-17-18.33.03-1015ddb2-7274-484e-b6eb-529cc5937a3f.log (42.9 KB)

1 Like

Was hoping this issue would have been fixed, since I was unable to play at all during the Closed Tech period last month. Tried everything as listed above, but literally am unable to get past the starting screen/“Waiting for Inquisitorial Clearance” to create a character due to the “Backend Error” error.

Platform: Steam

PlayerID: 76561198038146157

Approx. Time: 11/17/2022, 1:36PM (EST)

console-2022-11-17-18.36.33-ac7c1c44-9ef9-4eaf-929c-2b55c51a2f5f.log (7.0 KB)

Can not get past (++ Processing Inquisitorial Clearance ++)

End in a backend error. Live in NA EST. Did not experience this during the closed beta test.


I’m having this issue. I can get to the screen where it says “press space to enter” and it says “waiting for inquisitorial clearance” or whatever and then times out and says it experienced a back end error.
I’m on steam
Steam ID: 76561198024564305

console-2022-11-17-18.50.47-2816551a-d9b9-48f4-9949-b77d190678c4.log (28.1 KB)
console-2022-11-17-18.57.32-0c904cbc-7166-41ee-bd1b-007efe3687c8.log (19.0 KB)
console-2022-11-17-19.03.01-c61e8487-8f44-4a51-8583-0ee268634a45.log (24.4 KB)

Installment and download perfect getts pass the shade and come pass the clearance gets backenderror last time this happened I got forced to vpn, pleases tell me i don’t need to use it again
Steam pc

Player ID:

[Mikay] Steam ID: 76561198043742206

Approx. Time of Issue & Timezone:
[11/17/2022,20:21PM] [+1 timezone]

Upload Console Log:
console-2022-11-17-19.05.23-07300e83-d8c7-4bc3-9833-e547ff75fcd3.log (32.1 KB)

Loading Screen into backend error same as in last beta
SteamID: Feng-Shuizid

20:15 CET
20:24 CET
console-2022-11-17-19.21.17-41ac818b-d47b-499b-943f-13c02c7adffd.log (6.7 KB)
console-2022-11-17-19.12.08-cf4940d9-db6d-4dd9-84c9-021554ad0763.log (34.5 KB)

Steps to Reproduce:

  1. Launch game from steam.
  2. Press play from launcher
  3. Press “space” to log in.
  4. Game crashes at “processing inquisitorial clearance” with backend error message.


Player ID:
SteamID: 76561198021437034
Steam Profile URL: Steam Community :: MauserTeleri

Approx. Time of Issue & Timezone:
[11/17/2022, 11:20AM/PM] [PST]

Upload Console Log:
console-2022-11-17-19.09.07-15052131-4917-49a2-82cf-d2258e05c01f.log (23.9 KB)
console-2022-11-17-19.16.00-81919556-f1db-4dc4-a7a2-ce05b4e16a43.log (19.9 KB)

Cannot load passed the “Processing Inquisitorial Clearance” section on the main screen. I receive a backend error every time, no crash report. Did not have this problem during the beta test during October.

Platform: Steam

Steam ID: Steam Community :: Solid

Time: 11-17-2022 1:36PM EST

Console Log:
console-2022-11-17-18.37.58-9f1f601f-ca58-4106-b20b-ff5f039d111b.log (25.2 KB)
console-2022-11-17-18.43.36-e420f962-f257-4e70-9c50-517ce217711b.log (19.1 KB)
console-2022-11-17-18.36.05-8f989a83-ec6c-4e4f-9890-93ae0205c86c.log (24.2 KB)


ID: Steam Community :: Bloodmastery

17.11.2022 / 21:00 - 21:40 +2 europe time

console-2022-11-17-19.40.23-0ad26b43-cb97-4ae8-9d80-43b933b6ebb6.log (132.0 KB)

After flashing needing inqusitiral clearance it says backend error


Player ID:

Approx. Time of Issue & Timezone:
[11/17/2022, 21:52AM/PM] [EETC]
[11/17/2022, 21:27AM/PM] [EETC]

Upload Console Log:
console-2022-11-17-19.25.53-b7df953e-dbc3-4837-8d98-8deb1797b5d0.log (33.5 KB)
console-2022-11-17-19.52.04-bdedfd16-3920-449f-89f3-4327ef36aec6.log (33.1 KB)

Backend error here too.

It’s the same exact problem we had in the closed beta where we had to use a vpn to play. This is unacceptable.

Edit: Yep, if you use a VPN the Backend error disappears.

Issue Description:
Backend Error - Unable to sign in

Crash Report:

GUID: 158648b5-06e7-486e-8d8a-ff004e286bc0
Log File:
Info Type:
[Crash Link]:

Steps to Reproduce:

  1. Attempt to login from main splash screen


Player ID:
Steam ID: 76561198006687525

Approx. Time of Issue & Timezone:
11/17/2022 03:00 PM EST

Upload Console Log:
console-2022-11-17-19.49.05-88837c33-5459-4255-9954-f3ed55136906.log (63.3 KB)

Cannot load passed the “Processing Inquisitorial Clearance” section on the main screen. Had this problem during the beta test during October.


Player ID:

Approx. Time of Issue & Timezone:
[11/17/2022, 1:00PM MST

console-2022-11-17-19.58.04-bfe5f510-726f-412c-a5b3-bb50957a72c3.log (49.6 KB)
console-2022-11-17-20.05.17-f312a9d5-fa66-4580-b539-90ea63843653.log (28.0 KB)
Console Log:**

my permanent fix: setting IP address to static with DMZ hosting
temporary solution: Using a VPN

console-2022-11-17-18.30.04-34ecce66-26b1-4a58-bc80-3ef318b9c0d6.log (383.1 KB)

  1. Just trying to enter game
  2. After trailer game ask me to click “space” after clicking i wait 1-2 minutes and have this error


right now


console-2022-11-17-20.11.36-8a594c81-c566-4872-945a-21ce7889f08f.log (24.2 KB)
console-2022-11-17-20.22.00-db2edc22-082c-42f2-8f4d-049465303251.log (19.2 KB)
console-2022-11-17-20.06.38-88389a1f-5034-486e-8668-b00c0c73fbbb.log (32.9 KB)

When trying to enter the game I keep getting Backend Error after pressing space. It shows up almost immediately with “processing inquisitorial clearance” as the text at the bottom. This also happened when I tried to play the closed beta test.
Platform : Steam
Steam Profile :
Date and Time : 17/11/22, 8:35pm UTC
Console Log :
console-2022-11-17-20.33.41-3da7c2d7-22e6-427e-a388-905e7da4fe01.log (20.1 KB)

Issue Description:
Trying to log into game from main menu. Says “Processing Inquisitorial Clearance” for some then, then give a Backend Error and cancels the log in.

Steps to Reproduce:
Just happens every time. Won’t let me log in from the main menu.

Steam PC

Player ID:
Demi-Socialist Jontex

Approx. Time of Issue & Timezone:
09:45am 18/11/2022 NZDT
Upload Console Log:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
  4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
  5. Upload here
    console-2022-11-17-19.30.18-a24d553f-a12e-447b-9b2c-a956eed53235.log (69.9 KB)
    console-2022-11-17-19.44.55-b189d0fa-b15b-4c5e-bbbe-98a00a245b84.log (33.7 KB)
    console-2022-11-17-20.00.48-eb271a3a-8f0d-4f04-aa41-946c1a611d5d.log (25.0 KB)
    console-2022-11-17-20.38.30-012e3e46-a255-442f-a9f8-f8dc3dc43f46.log (39.4 KB)
    console-2022-11-17-20.57.50-55a42be4-2c79-41ad-81a1-371dab76b250.log (6.4 KB)