3001 as an analog of the error SSL_CONNECT ERROR in verm2

Issue Type (Required):

Error - Backend Error

Issue Description (Required):

Vermentide 2 had an SSL_CONNECT ERROR that behaved like error 3001. In both cases, the successful connection chance was 30%.

Vermentide had a login server https://5107.playfabapi.com/ which had 3 IP addresses that changed periodically. And the problem was that when trying to connect, the game accidentally connected to 1 of the 3 servers, 2 of which might not work. The problem was solved very easily, you had to write a working IP address in the hosts file, for example 54.191.165.26 5107.playfabapi.com, after which the game connected to the game server in 100% of cases.

What server login does Darktide use?

1 Like

This isn’t an applicable solution for Darktide, unfortunately. I can’t share too much information, but the reason you were able to use this solution for Vermintide 2 was likely due to a DNS issue - which wouldn’t explain the error you’re experiencing in Darktide.

1 Like

The problem is in the random blocking of Amazon servers due to the poor work of some employees, a striking example of their work is the blocking of Telegram in 2018, which resulted in constant SSL_CONNECT ERROR. you yourself understand this since you wrote that this is a problem only for players from Russia. Using a VPN solves this problem. If you “remove servers” that are blocked for Russian players or redirect only to unblocked ones, this will solve the problem.