In this guide, we will show you the steps to fix the Connection Type error in Escape from Tarkov. This multiplayer first-person shooter game has created a niche segment of the loyal fanbase for itself. Combating with other players in ‘raids’, the ultimate aim for survival is no easy task in itself. However, what is even more challenging are the issues that this game gets bugged with, more so when it happens after installing an official patch. In this regard, the game recently got blessed with the update version 0.12.12.15.4.
However, alongside that, users had to welcome an unwanted bug. All those users who had changed the Connection Type right before updating their game were no longer able to log in to the game right after the update. Whenever they tried doing so, they were instead greeted with an error URL message [which is inaccessible by the general users]. If you are also in the same boat, then this guide shall make you aware of a handy workaround to fix the connection type error in Escape from Tarkov. Follow along.
How to Fix Escape from Tarkov Connection Type Bug
As of now, the developers are saying that users shouldn’t change the in-game Connection Type. But what if the users who had already done so and are currently facing this issue. Well, for those sets of users, we have found a nifty workaround. There exist a tweak through which you could change the Connection Type by editing the game’s configuration files, without even interacting with the game. Here’s how:
- Bring up the File Explorer via Windows+E shortcut keys.
- Then copy-paste the below location in its address bar and hit Enter [replace username accordingly].
C:\Users\username\AppData\Roaming\Battlestate Games\Escape from Tarkov\Settings
- Within that folder, there will be an INI file, open it via Notepad.
Reference Image - Finally, change the Connection Type to Default and the issue stands rectified.
That’s it. These were the steps to fix the connection type error in Escape from Tarkov. As far as the official stance on this matter is concerned, the developers are aware of this issue, but they haven’t given out any ETA for the rollout of a fix. As and when that happens, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet.
