Dedicated server V1.0 (b333) cannot connect via public IP

4

420science

New member
The problem:

Me and my friend cannot connect to my friends 7 days to die server using public IP, my friend has the server PC next to him so he can connect via local IP, after he joins and invites me via steam then i can join even tough i am not connected to his local network.(server set to public with password)

Steam server favorites does not find the server, neither does the ingame browser OR the direct connect via IP.

When we try to add the server to our favorites all the server console said was: Bad data received.

When we try to connect to the server we get: Unable to retrieve server info.

Steps taken:

Did clean server setup, all settings are correct, ports have been forwarded UDP&TCP(just to be sure). Also tried changing the port to a port we knew that worked for other servers.

Firewall is completely turned off so thats not the problem.

Server & client versions are both the same (server was freshly downloaded, my game has fresh install to)

We tried changing the "crossplatform" & "SteamNetworking" settings.

Forwarded ports:

BasePort: 26900-26905 or 27015-27020 (for server browser visibility)
Game ports: 26900-27050 (for gameplay traffic)
Telnet port: 27015-27030

If anyone has other things we can try, please lemeknow because we can not find a way to fix it except my friend inviting me, but that kinda defeats the point of a dedicated server....

Thanks in advance!

 
Rule 1: Never use any ports from 27000-27099 if you can avoid it at all. They are commonly used for Steam functions or Valve games.

Rule 2: Never forward any ports from 27000-27099 unless it is absolutely required for a Valve game that is using port 27015 as default.

Rule 3: Only ever forward the exact ports and protocols that you need for the dedicated server. If you are not hosting a dedicated server, you do not need to forward ports.

Rule 4: Always give the dedicated server a static IP address in the local LAN.

So in your case, the server is on port 26900. 

You would forward TCP 26900 to the computer, and port range UDP 26900-26903 to that computer.

Also note, SteamNetworking should absolutely be disabled in the server network protocols if you have proper forwarding. If you are unable to forward the ports, enabling SteamNetworking is a crutch that may bypass that. It comes at a cost of increased overhead and network latency though. Will likely increase ping to the server as well.

LiteNetLib should never be disabled except in rare troubleshooting cases where you know exactly what you are looking for.

At a guess, the ports are not properly forwarded/opened or other issues are occurring by re-directing traffic that should not be redirected.

 
My friend fixed it, the answers where sadly not useful but thanks anyway for the fast reply :)

The problem:

Windows firewall has 2 ways to allow traffic, one via the automatic pop-up that allows ALL ports for the specific application, and one more advanced where you can pick the ports for the application.

If u use the pop-up "Allow an app or feature through Windows Defender Firewall" which allows ALL ports for the specific application, and if you disable this line it will block all traffic to that application even if you disable windows firewall.

Just REMOVE the line that allows ALL ports if u want to use the advanced way.

So all lines/port allowances I added in Advanced Settings were automatically blocked, even when windows firewall was disabled.

Still dont get why joining via steam worked before, but now the server is visible and i can connect without a problem.

 
I am having the exact same issue where my friends can connect to the server by joining me (through Steam) when I am connected to the server through local IP, but they cannot connect directly using my public IP.

I don't really understand what you did to solve this?

We have the ports forwarded on the router, and the ports open in Windows firewall on the computer running the server.

Do you mean that we should edit the Windows firewall settings on the server host, or on the clients connecting?

Hope you can help!

 
Atlas8817 said:
У меня точно такая же проблема: мои друзья могут подключиться к серверу, присоединившись ко мне (через Steam), когда я подключен к серверу через локальный IP, но они не могут подключиться напрямую, используя мой публичный IP.

Я не совсем понимаю, что вы сделали, чтобы решить эту проблему?

У нас есть переадресованные порты на маршрутизаторе, и порты открыты в брандмауэре Windows на компьютере, на котором работает сервер.

Вы имеете в виду, что нам следует редактировать настройки брандмауэра Windows на хосте сервера или на подключающихся клиентах?

Надеюсь, вы сможете помочь!
Click to expand...
open the ports via Powershell

New-NetFirewallRule -DisplayName "7 Days to Die Server" -Direction Inbound -LocalPort 26900-26903 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "7 Days to Die Server" -Direction Outbound -LocalPort 26900-26903 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "7 Days to Die Server" -Direction Outbound -LocalPort 26900-26903 -Protocol UDP -Action Allow
New-NetFirewallRule -DisplayName "7 Days to Die Server" -Direction Inbound -LocalPort 26900-26903 -Protocol UDP -Action Allow"

New-NetFirewallRule -DisplayName "7 Days to Die Server" -Direction Inbound -LocalPort 8080-8082,26900-26903 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "7 Days to Die Server" -Direction Outbound -LocalPort 8080-8082,26900-26903 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "7 Days to Die Server" -Direction Outbound -LocalPort 26900-26903 -Protocol UDP -Action Allow
New-NetFirewallRule -DisplayName "7 Days to Die Server" -Direction Inbound -LocalPort 26900-26903 -Protocol UDP -Action Allow

 
Server host PC should be the only one that needs ports forwarded on firewall and router.

My friend is not online so i will ask for a more clear answer when he is back but as far as i understand it you have 2 options in windows that could be conflicting:

!) Windows defender firewall
2) Windows Defender Firewall with Advanced Security

Check: Windows defender firewall

And look if u have disabled 7 days to die server anywhere in that tab

Check: Windows Defender Firewall with Advanced Security

If you have an entry in here for 7 days server specifying a port/port range in that tab

If both are true, then you need to remove the disabled entry in: Windows defender firewall

And make sure the right ports are allowed in: Windows Defender Firewall with Advanced Security

Its a bit hard to explain thx to windows having double settings but i hope this makes sense :P

 
You must log in or register to reply here.
Back
Top