#Issue with dedicated server -global block for Russia in my FW

1 messages · Page 1 of 1 (latest)

tulip leaf
#

Hi Windrose, I have a block for Russian IP's and it might be a false positive on my GeoBlock but I cannot connect to my own local dedicated server because I need to connect to 185.146.156.43, 149.154.64.47 and 155.212.169.178 to be able to connect to the server. Why do I need to connect these servers when I want to play on my on my local dedicated server? Is there a workaround? Thanks. #1493348541177794601

wheat void
#

Thanks for the report. In case you have our connectivity service servers block you need to switch to a direct connection (introduced in the new patch)

tulip leaf
#

The issue is the same with direct connection. This is verified when I tried this on another computer on a different network and it works fine. For some reasons - the client need to connect to the above IP's when connecting to a private, dedicated server. Please advice. Ping @wheat void

wheat void
#

Direct IP option does not require connection to our connectivity services, but depending on your home network, it can require manual router configuration (port forwarding / NAT setup).

tulip leaf
#

Thank you for the answer Cubert. I'm fairly versatile in network engineering and this information originates from my logs on my enterprise firewall. This is the first time I've experienced this on a dedicated server setup from any game. I've hosted 25+ different game-servers in my days and for some reason the client needs to connect to these IP's for the game-client to be able to (direct) connect to the server. Update: When I remove the GeoIP blocking the CIS region lights up under connected services and I can use the servers invite code to connect - but I still can't use direct connect, this points to that the client needs to go to these specific IP's (in Russia) to work and the clients behavior is different when using direct connect vs via invite code. Please advice.

tulip leaf
#

I've also verified that 7777 and 7778 and 3478 (STUN) UDP (nmap -sU -p 7777 <my ip>) are open. Ping @wheat void

wheat void
#

Can you provide your logs from Direct IP connection attempts both successful and unsuccessful? Client + Server, we'll look why does it still try to use our connectivity servers.

tulip sapphireBOT
#
BUG REPORTING GUIDE

Please share your game logs, game saves, crash dumps, and DxDiag. These are essential for diagnosing and fixing bugs.

HOW TO FIND LOGS

Game logs are located here:
C:\Users\%USERNAME%\AppData\Local\R5\Saved\Logs

Server logs are located here:
R5\Builds\WindowsServer\R5\Saved\Logs

To get there, open Steam, find Windrose in your library, right-click it, then go to Manage → Browse local files. From there, archive the files in the Logs folder and share them with us.

Please name your logs in a way that describes the problem, for example: Crashedwhile_fighting_Dodo.log

HOW TO FIND SAVES

Your saves are located here:
C:\Users\%USERNAME%\AppData\Local\R5\Saved\SaveProfiles
Please close the game before archiving your saves!

If you are playing on a dedicated server:
• Stop both the client and the dedicated server.
• Find and archive your server logs and world save.

Dedicated server logs are located here:
R5\Saved\Logs

Dedicated server saves are located here:
R5\Saved\SaveProfiles

To get there, open Steam, find Windrose Dedicated Server in your library, right-click it, then go to Manage → Browse local files (or go to the folder where your Windrose Dedicated Server is stored).

Please close the dedicated server before archiving your saves.

HOW TO FIND CRASH DUMPS

If crashes are involved, please share crash dumps:

Game client dumps (if play offline)
%LOCALAPPDATA%\Local\R5\Saved\Crashes
%LOCALAPPDATA%\Local\R5\.sentry-native

Server dumps (if you self-host from game client)
SteamLibrary\steamapps\common\Windrose\R5\Builds\WindowsServer\R5\.sentry-native
SteamLibrary\steamapps\common\Windrose\R5\Builds\WindowsServer\R5\Saved\Crashes

Dedicated server dumps
Windrose Dedicated Server\R5\.sentry-native
Windrose Dedicated Server\R5\Saved\Crashes

HOW TO FIND DXDIAG

Please also include your DxDiag report. This is your PC specifications in .txt format:

• Press Win + R.
• Type dxdiag and press Enter.
• When the tool opens, click Save All Information.
• Save the .txt file and attach it to your report.

Any additional screenshots and/or videos are HIGHLY appreciated!

tulip leaf
#

Hi Cubert, please help me understand why it works to connect to the server via invite code if I unblock the Russian IP's mentioned in the original post?

Update: I found one error - the DirectConnect=False settings in the ServerDescription.json was set to default NO, I update the IP, serverport and to true. But the problem persists.

tulip leaf
#

Update 2: Found the issue - the port 7777 was only open to UDP and not TCP - this solved the direct connect issue. Now the only question remaining the the Russien IP's via the Invite code. Thanks.

wheat void
#

There is no secret or conspiracy here. The game previously had only the invite-based connection, that was using our connectivity servers - EU/NA, RU and KR. After the early access release, we found out that numerous ISPs around the world blacklisted our servers as malicious. Some blacklisted RU servers, some - EU/NA, some - all three at once, etc. We couldn't find any real pattern there.

We began contacting them and asking players to contact theirs to provide any necessary information for whitelisting, but it takes time. Some ISPs responded quickly and unblocked us, some didn't - we're still working on it. And as a workaround we added Direct IP connection option last weekend, so people aren't stuck waiting for their ISP or aren't forced to use VPNs, but as you know it may require extra setup to work.

tulip leaf
#

Your FAQ mention a -EU server but the DNS resolves to your -RU server, perhaps update your FAQ then to reflect that you are still using Russian server, that would help future troubleshooting. Thanks.