KNOWN ISSUE: Backend Error

Right, I give up, I’ve had enough.

Here are the last 5 of todays logs. I’ve managed a few games, each time its taken me ages to connect past the spacebar screen, as many attempts to get logged into any character, and then half a dozen 4008 errors to get a game. The shops don’t load, if I complete a mission I crash out on the rewards screen.

I had none of this before the .13 patch, beta was solid, I was excited. I can’t deal with this anymore.

console-2022-12-08-21.43.19-456222a4-bdce-4334-81d1-755c9ec0feeb.log (122.3 KB)
console-2022-12-08-21.35.31-ff42d134-6007-4397-9837-b15913ff790a.log (125.3 KB)
console-2022-12-08-20.57.59-c0f98a24-cf32-4c93-9bc4-f93a8bda18d5.log (194.5 KB)
console-2022-12-08-22.40.07-345446b1-83a0-4049-8893-bdcd6de8537c.log (30.5 KB)
console-2022-12-08-21.49.01-4cf1cf8b-bd21-4cb1-9f59-0cdc1db82335.log (4.5 MB)

1 Like

Backend Error Problem when Sign in.

Just got it and i dont know what to do…

i Cant sign in to Dark tide.

1 Like

Issue Description:
Same as the other, press space bar and BOOM Backend Error

Crash Report (If Applicable):
N/A

Error Displayed (If Applicable):
Error Signing in

Steps to Reproduce:

  1. Load game
  2. Press spacebar at title screen

Mission Name (If Applicable):
N/A

Platform:
Steam

Player ID:
Nirama

Approx. Time of Issue & Timezone:
9/12/2022 at around 06:00 - 06:30 PM UTC+7

Reproduction Rate:
Constant (100%)

1 Like

Hey look at that, still a backend error while using a VPN this long after release. On both Steam and Game Pass. Doesn’t look like this is getting fixed anytime soon. Get your thrill elsewhere, boys.

Backend Error Signing In

Crash Report (If Applicable):
Backend Error Signing In; already tried verifying 3 times, disconnected/restarted wifi, used experimental build

Backend Error Signing In

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

  1. Run game

Starting screen

Platform:
Steam

Player ID:
ZeMarauder

Approx. Time of Issue & Timezone:
6:55PM Bangkok Time

Reproduction Rate:
Constant (100%)

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-12-09-11.46.19-bc982b80-b3b5-4bb1-93e5-b07f65e75ea4.log (23.2 KB)
    console-2022-12-09-11.52.28-9d17f20f-e0b8-409f-83b7-ba7aa3682097.log (20.1 KB)

Upload darktide_launcher.log:

  1. Press the Windows key + R
    darktide_launcher.log (548.2 KB)

  2. Enter %appdata% within the search input and select ‘OK’

  3. Navigate to AppData\Roaming\Fatshark\Darktide

  4. Locate the darktide_launcher.log in this directory

  5. Upload here

1 Like

Most Backend reports are from at least 20 days ago, but happened to me. Already using experimental build. No non-alphabetical characters (even if so, how can i change when i cant even enter game). Not using Kaspersky. None of the “solutions” work. Maybe address and fix the issue instead of giving temporary “solutions” that don’t even work

Steps to Reproduce: Clicking space-bar on start menu.

Reproduction Rate:
Constant (100%)

1 Like

yeah unlikely they’ll even address the issue head on let alone fix it

Haven’t even been able to launch the game today.

Here have some more logs.
console-2022-12-09-17.35.30-643a86f9-fa4a-4e38-8449-00aab5d94951.log (31.9 KB)
console-2022-12-09-17.32.19-2a65617a-a8be-4dfa-bcc4-de4451a571cb.log (23.8 KB)
console-2022-12-09-17.30.36-e3766518-b70f-4f2d-bcab-7614aaa6cb6a.log (30.8 KB)
console-2022-12-09-17.39.18-fbe0af54-5aa4-4f13-8ed5-dd73cf39dbcc.log (3.9 MB)
console-2022-12-09-17.36.11-fe0444c3-eef3-4aa2-b213-1d919399b250.log (23.8 KB)

I guess my previous 45 hours without this issue will be all I get for my money.

2 Likes

Hello I have the Backend Error again after it beeing “fixed” in the experimental build. I tried lauching the game without disabeling my fire wall (kaspersky total security) in both the Experimental Build and normal build. After that failed I tried disabeling my fire wall and starting the normal build and Experimental Build both lead to the Backend Error.

Steps to Reproduce:

  • Launch game from steam. (experimental build, fire wall enabled)
  • Press play from launcher
  • Press “space” to log in.
  • Game shows backend error message on “processing inquisitorial clearance”.

  • Switch to normal build
  • Launch game from steam. (fire wall enabled)
  • Press play from launcher
  • Press “space” to log in.
  • Game shows backend error message on “processing inquisitorial clearance”.

  • Launch game from steam. (normal build, fire wall disabled)
  • Press play from launcher
  • Press “space” to log in.
  • Game shows backend error message on “processing inquisitorial clearance”.

  • Switch to experimental build
  • Launch game from steam. (fire wall disabled)
  • Press play from launcher
  • Press “space” to log in.
  • Game shows backend error message on “processing inquisitorial clearance”.

Platform: Steam

Player ID: Steam Community :: Rechet

Approx. Time of Issue & Timezone: 12/09/2022, 09:00PM UTC+2

Backend Error
console-2022-12-09-20.04.46-25de540a-a9e8-4088-9160-4d3f7a472430.log (25.7 KB)
console-2022-12-09-20.06.44-d6dbe4ec-59f3-43ac-b359-430c0b0cc599.log (26.9 KB)
console-2022-12-09-20.08.33-f68ba57a-96de-40ac-9201-0777eecd65b2.log (28.2 KB)
console-2022-12-09-20.00.19-2ccbfe34-4b22-482b-ad7f-aa9c82e2b50c.log (28.8 KB)

Managed a game today!
Two infact - First time I was lulled into thinking something had been fixed - until mission complete, where I didn’t get the results screen, and ended up stuck in an infinite loading screen:
20:55:58.720 error: [Unit] Unit: ‘#ID[61e644cb1f192b1b]’ has still childs attached to it, please unlink them before destroying the unit
child 0: ‘#ID[14be24292cf5d106]’
Log below
console-2022-12-09-20.17.49-5d75393d-0eb7-41b7-bd18-ddf0efbbf54d.log (248.5 KB)

Trying to reconnect, however, and it was business as usual, though this time I’m getting the certificate hashes back, which is a difference compared to other logs…
console-2022-12-09-21.12.32-493ef348-1049-4e14-9416-209dd4738f15.log (99.2 KB)
console-2022-12-09-21.22.08-d695c938-7e0a-4f80-9d49-ed1092748c79.log (21.3 KB)

so… no longer 100%… maybe AWS related… the mind boggles.

seem a different problem that the one i have

I found backend error in an unexpected place this time, and this one is silent!
Crash Report (If Applicable):
Backend Error from the social screen

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

  1. Run game
  2. Move around in the mourningstar
  3. Open the social screen and look at various players you’ve played with previously being nosy
  4. see what the functions are when you click on a player
  5. game locks up, ESC and no other key bind closes the social tab.
  6. Check log, backend error is recorded

Platform:
Steam

Player ID:
DrTechno

Approx. Time of Issue & Timezone:
22:13

Reproduction Rate:
unk

Upload Console Log:
console-2022-12-09-21.49.30-21131abd-a5bd-40e2-8cfc-e170e8f04cec.log (332.4 KB)

And we’re back to the old familiar Backend error at spacebar boss now I’ve had to restart the game to escape the above lock.

console-2022-12-09-22.40.01-5a08fd34-97ec-4b30-a840-878cbc5e9a81.log (73.0 KB)

1 Like

Backend Error again today. 2nd day. Gonna post and spam each day I get this until it gets fixed.

Steps to Reproduce: Clicking space-bar on start menu.

Reproduction Rate:
Constant (100%)

2 Likes

Been doing some experimentation with my various firewalls because of all the code=0 responses during the backend errors. Unfortunately yielded nothing noteworthy

However In some of the errors, I found that there was a progression from code=0 for a while, then getting the aws latency list but failing to connect past that, then finally getting in (on the nth attempt, not repeatable).

This was mimic’ed by the 4008 errors when joining the server.

Don’t know if this is a crashify artefact but here you go anyway, more logs for the log god.

console-2022-12-10-13.49.18-ef3b4944-e072-4f6c-b48e-889b78dcd788.log (46.1 KB)
console-2022-12-10-13.43.30-868bf279-c2d2-465b-842e-4cef435d32c4.log (24.2 KB)
console-2022-12-10-13.33.09-91501897-e740-47e2-afb8-363bcea73367.log (77.5 KB)
console-2022-12-10-13.26.36-febffa1e-a4e4-4cc2-a414-16481a7f88fa.log (44.4 KB)
console-2022-12-10-13.59.48-9124512d-6ba7-4c55-8556-0c1949d5b1ca.log (324.5 KB)

Had backend error for a week… finally tried experimental fix today and was able to log in!

what fix was that?

what was it?

Friends, Rejects, fellow BackendEnjoyers

I’ve fixed it on my end!
Fatshark have been repeatedly stating they don’t support IPv6 connections yet. Fine I thought, my router is using IPv4/IPv6 dual stack connections, so it will use the V4 and be fine with Darktide right?

Wrong! AWS Does support IPv6.
My fix was to disable the dual stack, setting my router to only use IPv4. I can now connect without issue first time, I do not get 4008 errors when trying to load in a character, the missions complete and return me to the morningstar, and the shop doesn’t crap out on me.

Log attached as… proof? dunno.
console-2022-12-10-20.57.24-0da18efd-a5c8-4a1d-ade8-c10849fe339b.log (1.2 MB)

Anyway, try turning off IPv6 even if its a combination with v4 or anything else. This came out of me investigating what could be causing a code=0 error when it tried to connect to the servers.

im not tech savvy please how you fix it??