Tried. Nope, does not work for me.
Issue : Cannot access main game. Error Code 2007 / internal_error. No game crash, only server error.
Reproduction : Any connection to game servers, only able to play tutorial/ character introduction.
Platform : Steam
Player ID : Titanium Blue Steam Community :: Titanium Blue
Time of issue : Have tried to access game almost daily since release, same result every time.
Logs : Uploaded 5 most recent.
console-2022-11-22-21.16.56-8cd8ace5-f479-45f3-a44a-877b1e551276.log (71.6 KB)
console-2022-11-21-21.55.22-8519f19f-b57a-40e6-9545-bbc2f08bc30f.log (36.3 KB)
console-2022-11-21-04.04.03-6fc67fa4-c0f1-4bad-99fc-136166bb5bc5.log (31.2 KB)
console-2022-11-21-03.58.21-973f708a-9d20-4522-8e2c-ceb63275375d.log (30.7 KB)
console-2022-11-21-03.09.01-7774c58e-ba8f-4dee-bf73-0ef6b2ddfdd1.log (36.0 KB)
Apparently its not a big enough issue for them to fixā¦
Unplayable since Fridays downloadā¦ and no fixesā¦ But we got a barberā¦
Beta or not, this is impressive in a really sad wayā¦
1 Like
I am still getting this problem except now it just says error code 2007 instead, really hope this gets fixed because i am completely unable to play the game 
Still the same after 1.0.7 patch, except now itās called āError 2007ā instead of āinternal_errorā. At best I can load up the hub level and stay there for approximately 5 seconds. At worst, itās immediate after pressing āstartā.
Crash Report (If Applicable):
Error 2007
Steps to Reproduce:
Log in and pick an operative to start loading into the hub.
Platform:
Steam
Player ID:
justdontdoitever
Approx. Time of Issue & Timezone:
11/23/2022 16:20 UTC
Reproduction Rate:
100% without VPN
Console Log:
console-2022-11-22-16.25.11-614584ab-c99d-48f3-8269-1ae92aadf9ef.log (54.5 KB)
Iām fairly certain its A large portion of Imperial Owners who are having Error 2007 at this point, its the only factor that would be causing my version of the error. Like I posted before I purchased the game for 3 of my friends (all standard edition) and Myself (Imperial edition), Iām the only one who has this issue out of us all and I think it has to do with the digital Currency trying to be added to the account even though its disabled right now. However the same could be said for the cosmetics but Iāve heard that player with the cosmetics have been able to maneuver a little but also crash or disconnect often.
This issue always start when going to meet with the NPC after the Training Room Tutorial, After that the character canāt get into the game.
Steps to Reproduce:
- Launch Game Via the Launcher
2.Load to Character Select
3.Pick Character (I made one of each class all the same issue)
4.Load Screens for 25 Seconds roughly
5.Message on the right saying āDisconnected form server: Error 2007ā
6.Booted back to Character Select or Stuck in loading until Alt F4
Platform:
Steam
Steam ID:
Time:
5:41 PM 11/22/2022
console-2022-11-22-22.39.31-868fad51-9cd4-45b0-9466-34b905b5c98b.log (35.3 KB)
Havenāt been able to play since the beta launched. First internal_error, now Error Code 2007. Tried every suggested temporary fix. Nothing has worked. This has been extremely frustrating, and is in dire need of a solution for the many people experiencing this, Beta or not.
2 Likes
Use an ethernet cable or increase/activate QOS on wireless router, do some port forwarding, these workarounds were given a few answers back. Try to see if they help
Thank you, I want them to fix it finaly we gave monyā¦I bought the game as soon as it was awaliable , I play Vermintide 2 for a long time and I like what they did with it,I am shure this game will be great but they need to fix this .
1 Like
More testing after 1.0.7 update, still about the same since my last tests, if not possibly worse. Managed to finish a few missions but the disconnects are still pretty bad - every few minutes. Had one good game at the start where I only got disconnected once halfway through, but the next two games were horrid, getting disconnected every 1-2 mins.
Steps to Reproduce:
- Select character - Pysker
- Load into Mourningstar
- Join quick play game
- Play for a few minutes
- Encounter 2007 error
ISP: Aussie Broadband, Australia
Location: Australia
Platform: Steam
Player ID: Steam Community :: mace
Approx. Time of Issue & Timezone:
Date 2022-11-23
Times - in UTC from log file
Launched game - 00:26
internal_error / 2007:
- 00:31
- 00:36
- 00:38
- 00:40
- 00:44
- 00:45
- 00:47
- 00:49
- 00:50
- 00:51
- 00:54
- 00:55
- 00:57
- 01:06
- 01:08
- 01:20
- 01:22
- 01:24
From a play session that was just under an hour, and across three missions, got disconnected 18 times. It was pure chance that I managed to reconnect before the mission finished to actually get the rewardsā¦
Console Log:
console-2022-11-23-00.26.38-c6d1361b-14b2-4366-8f4c-5f3d64ebf74c.log (788.6 KB)
Still happening, wheeeeeee
ISP: SpinTel, Australia
steam: lolghurt
console-2022-11-23-03.11.45-f70d16a3-1069-42b9-b074-de29b1b3bbd3.log (57.9 KB)
darktide_launcher.log (495.5 KB)
Still have yet to play more than 45 seconds in a single session. Never finished a game. Vast majority of the time I disconnect either trying to load the Mourningstar or a few seconds after dropping into the Mourningstar. Iāve seen every error code under the sun at this point. Error Code: 2007 is the just the latest, so thatās why iām posting in this thread.
LOGS attached.
console-2022-11-23-04.38.39-b5449871-6a8a-443c-9970-29671a93eb95.log (182.9 KB)
console-2022-11-23-04.29.18-b1ec108a-8758-4019-81f3-8810ddff4ca5.log (74.0 KB)
console-2022-11-23-04.32.52-0c6d11e9-cdcc-4f50-abc4-d7c9531c1c0f.log (112.1 KB)
1 Like
This has nothing to do with imperial edition, we have standard game
Tried it. Changes nothing for me regarding error 2007.
These are my 2 attempts logs:
7:45
7:51
console-2022-11-23-06.39.05-74e2f649-72f4-4cdc-a6ba-f1dc31f98df7.log (105.1 KB)
console-2022-11-23-06.47.28-1f292b73-bc3c-4649-bad9-952e56605a3e.log (114.3 KB)
FWIW I have Xfinity internet (wifi) and was unable to select a character (posted way further up in the thread with deets). Getting VPN fixed everythingā¦ Weird.
Is the networking team aware of the possibility that some/all people reporting this issue are using Carrier Grade NAT due to their ISP.
I say this as I have experienced severe network issues in other games due to having 5g based broadband internet which utilises CGNAT, opposed to regular wired broadband.
Carrier Grade NAT (CGNAT) resulting in a double NAT, which games consoles often object to, which means you donāt get your own public IP address but share it with other users. So you canāt be uniquely idāed on the Net & therefore your LAN cannot be addressed from outside for unsolicited accesses. This is unlike fixed BB.
What Iām curious about is how this regression was introduced, as I was not experiencing these issues in the Closed Beta
2 Likes
Iām using static IP with my ISP and Iām having this issue 100% of the time unless I jump onto VPN.
Furthermore, the symptoms (you can join the hub and you will see other players there, just for a very short time) indicates that thereās nothing wrong with NATs. You can connect, but for some reason the game boots you out really fast.
2 Likes
The fact that using a VPN seems to be a universal work-around suggests that it is related to NAT/IPv4 configuration in some regard.
All Iām saying is if Fatshark havenāt considered the implications of CGNAT they should at least rule it out.
Being able to connect briefly isnāt indicative of anything without knowing the netcode, anything further is pure speculation at that point.