Always Connection Timeout

[Xevichr]

Issue Description:
Whatever happens, I always get a connection timeout when looking for a game. When I host a game, I can see that players are trying to join, but are unable to. I tried to join my friends at some point, it said 4/4 players were in, but I wasn’t. I have tried the following:

Change DNS
Flush DNS
Renew IP address
Check for inbound firewall rule, it exists, Warhammer Vermintide 2
Verified game files
Tried with VPN
Tried without VPN
Checked for Steam updates
Connection is steady as it could be, ethernet. 946.99 mbps download, 84.01 upload and 15 ms to ISP.
Set max upload to 2 Mbps
Tried small network packets

Never used any mods

Crash Report (If Applicable):
[Please see instructions on how to provide a crash report in the pinned Topic]
No crash

Error Displayed (If Applicable):
Connection timeout
Connection refused and connection timeout of friends trying to join me

Steps to Reproduce:
Don’t understand the question

Map Name (If Applicable):
All maps

Platform:
[Steam/Xbox/PlayStation]
PC, Steam

Player ID:
Xevichr

Approx. Time of Issue & Timezone:
28-10-2023 19:00-21:00, CEST
Appeared a few days earlier, briefly, problem disappeared.

Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)

Rare. Played fine for months.

Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]

Warhammer Vermintide 2 2023 10 28 20 14 32 02 DVR

Video shows hosting a game, players trying to join.

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\Vermintide 2\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-2023-10-28-18.25.45-ba0b414f-d62e-4fbf-94e8-20ca4a80eec8.log (1.9 MB)
console-2023-10-28-18.50.42-cc74d7b2-249b-4eeb-89f2-e16ed8bd40dd.log (59.6 KB)
console-2023-10-28-18.52.41-10ec1d70-70b4-48e1-9879-59c5f6901856.log (137.8 KB)
console-2023-10-28-18.56.58-f204de54-db5b-43e7-951d-5c0cc5346673.log (156.2 KB)
console-2023-10-28-19.07.46-60a70853-a311-417a-a8fa-6d0e410f055a.log (329.0 KB)

Upload user_settings.config:

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to AppData\Roaming\Fatshark\Vermintide 2
4. Locate the user_settings.config in this directory
5. Upload here

user_settings.config (7.6 KB)

[Xevichr]

I wouldn’t know why, but it is working now.

Just waited and gave it some time.

I noticed I couldn’t reach steamcommunity.com as well for some time when I couldn’t play. Now I can play and reach that website. Weird, will look into it myself. Maybe someone can figure it out with the logs:

console-2023-10-28-22.23.31-ce2f1613-83e9-4105-9913-7ea58ba96816.log (958.4 KB)

If I find something I will post it here again.

[Xevichr]

It is likely an ISP side problem.

I found out my father had the early release version for UniFi enabled, so I backed it up, went to factory settings and still had the same issue on a stable version.

It is also broken again. Even though it worked yesterday after 23:00. No idea why, but at least that gets rid of my suspicion about it being DNS related. I didn’t change anything.

I tried the DNS of Microsoft, Google, Cloudflare and AWS (Amazon) all the same result.

[Xevichr]

The problem is either Steam or ISP side. As mentioned I also couldn’t go to http://steamcommunity.com/ on my entire network. I have confirmed it is either Steam side or ISP side. Unless if anyone can think of things I haven’t tried that I mentioned earlier.

[FatsharkLev]

Hey @Xevichr,

Thanks for the detailed report. From your findings, I’d suspect it to be an ISP issue.

You appear to have already run through all of our connectivity error solutions which I would normally suggest. If you do contact your ISP you can also quote our backend endpoint URL:
https://5107.playfabapi.com/
Just to ensure they aren’t blocking any network requests to our servers. (Though as this a connection timout error opposed to a sign-in timeout, I would expect this to be okay)