Server not showing in server list

[Loadnabox]

Running from a dedicated server in-home

8 core 4Ghz AMD, 24G ram on Ubuntu

 

People can connect to my server just fine if I give them my external IP however the server is not visible either from the steam client on my gaming system nor through the 7DTD server list

 

Router port forwarding is in the snippet below. Ubuntu Firewall is disabled for testing purposes

 

I've done some reading and followed most of the usual checks but nothing is panning out yet. Suggestions would be appreciated

 

[lazerblade01]

You need 26900 through 26905, both TCP and UDP. If you need telnet or ftp ports open as well, these are listed in the serverconfig/xml file - defaults are 8081 and 8082 I think. Just 26900 isn't going to be enough to list the server, only allow connections to it.

[Alloc]

Actually it's a few less ports: https://7dtd.illy.bz/wiki/Ports

(Should really find some time to port that list over to the official wiki ...)

[DEADication]

Actually it's a few less ports: https://7dtd.illy.bz/wiki/Ports

(Should really find some time to port that list over to the official wiki ...)

 

I have never had any ports in the 27xxx range open except 27000 itself... and the servers have always registered in the listing?

Ports I have open are 26900-27000 and 8080-8100. (for multiple instancing)

 

It all works fine??

[Loadnabox]

I followed the link and opened ports pretty liberally, however it's still not working

 

I think my next step is going to be to put the system into a DMZ so that it's directly exposed to the internet without NAT. This will help narrow things down a bit but it will take me some time to diagnose it (Maybe run some TCP dumps to see what inbound packets are hitting it)

 

I was also looking at a netstat output, I can see 26900 TCP and 2900-26902 UDP as open listening ports, but I didn't see any others that were in the port range for 7DTD nor did I see any strange ports associated with a 7DTD process tree.

 

I haven't opened up the web server and I disabled telnet. Telnet makes the IT geek in me have seizures and there's no reason that I know of to open the web panel unless it's a requirement. If it's a requirement I may need to play around with NAT some since there's another process using 8080 on my system so I remapped it to 8085

 

Is it possible I missed something in the serverconfig.xml?

 

Is there a place I'm supposed to put in the external IP?

[Alloc]

I have never had any ports in the 27xxx range open except 27000 itself... and the servers have always registered in the listing?

Ports I have open are 26900-27000 and 8080-8100. (for multiple instancing)

 

It all works fine??

You probably don't have a firewall set up that blocks outgoing connections by default. Or Valve changed something about how servers register recently (doubt this though).

 

 

 

I haven't opened up the web server and I disabled telnet.

That's fine. Also nothing else on 7DTD to configure. If you got the ServerPort as 26900 (which you seem to have when you can see those ports open with netstat) then opening up the 26900-26902 UDP as well as 26900 TCP should do the trick. Did you try an online TCP port tester on 26900? Or a friend to run a netsocket or just Telnet client on that port? That should print out server information if it can be accessed.

[lazerblade01]

I use Portforward to check my ports based on IP, and it's been pretty consistent with checking and reporting whether the ports are working or not.

[Loadnabox]

So I was delving down the rabbit hole and saw this in netstat

tcp 0 0 *:26900 *:* LISTEN

udp 0 0 *:26900 *:*

udp 768 0 *:26901 *:*

udp 0 0 *:26902 *:*

 

 

 

It looks like the system is indeed receiving the UPD packets, but those aren't being ingested by the application. This is determined by the second column showing 768 packets in the recv-q that are waiting.

 

Thoughts?

[Alloc]

No idea, logs might have an indication of any issues (if there are any game side) though.

[Loadnabox]

OK, Now I'm baffled.....

 

Logs showed problems starting the unity engine due to port conflict. I determined it was conflicting with another app for port 8080 on the control panel. I moved CP back to 8085

 

Now netstat doesn't show open ports but I can still connect to the game

 

So when it failed to open ports, netstat shows ports open, when it doesn't report any errors, netstat doesn't show the ports open. In both cases I can connect to the server

 

 

2016-05-16T16:53:52 6.792 INF NET: Starting server protocols

Failed to initialize network interface. Is the listen port already in use?

 

(Filename: Line: 221)

 

2016-05-16T16:53:52 6.794 INF NET: Unity NW server could not be started: CreateSocketOrThreadFailure

2016-05-16T16:53:52 6.794 INF NET: Untiy NW server stopped

2016-05-16T16:53:52 6.796 INF [steamworks.NET] NET: Server stopped

2016-05-16T16:53:52 6.796 INF Error starting dedicated server: CreateSocketOrThreadFailure

steam@Ubuntu:~/7DTD_server/7DaysToDieServer_Data$ netstat -l | grep 296

steam@Ubuntu:~/7DTD_server/7DaysToDieServer_Data$

 

2016-05-18T06:18:23 574.568 INF PlayerLogin: Loadnabox/Alpha 14.6

2016-05-18T06:18:23 574.568 INF Token length: 1368

2016-05-18T06:18:23 574.569 INF [steamworks.NET] Auth.AuthenticateUser()

2016-05-18T06:18:23 574.570 INF [steamworks.NET] Authenticating player: Loadnabox SteamId: XXXXXXXXXXXXXXXXX TicketLen: 1024 Result: k_EBeginAuthSessionResultOK

[Alloc]

OK, Now I'm baffled.....

 

Logs showed problems starting the unity engine due to port conflict. I determined it was conflicting with another app for port 8080 on the control panel. I moved CP back to 8085

 

Now netstat doesn't show open ports but I can still connect to the game

 

So when it failed to open ports, netstat shows ports open, when it doesn't report any errors, netstat doesn't show the ports open. In both cases I can connect to the server

 

Probably another instance still running. It won't show any open ports though when you use the wrong grep-line ;P

269, not 296

[Loadnabox]

Probably another instance still running. It won't show any open ports though when you use the wrong grep-line ;P

269, not 296

 

DERP

 

 

/facepalm

 

excuse me while I do a walk of shame

 

now back to figuring this out

 

steam@Ubuntu:~/7DTD_server/7DaysToDieServer_Data$ netstat -l | grep 269

tcp 0 0 *:26900 *:* LISTEN

udp 0 0 *:26900 *:*

udp 0 0 *:26901 *:*

udp 0 0 *:26902 *:*

[Alloc]

I would start with making sure that *no* 7dtd process is running, then start just *one* of them. Then check the logs (or even provide them here). Also as I said if you have 26900/TCP open run Telnet / netcat / anything else on that port from outside of the server network (i.e. "the internet" ) and see if you get the proper results there.

[Loadnabox]

Logfile

http://pastebin.com/W6Us4Tph

 

 

 

root@Ubuntu:~$ ps -ef | grep Die

steam 2624 2598 29 08:26 pts/9 00:14:59 ./7DaysToDieServer.x86 -logfile 7DaysToDieServer_Data/output_log__2016-05-18__06-07-50.txt -quit -batchmode -nographics -dedicated -configfile=serverconfig.xml

user 6594 6572 0 09:18 pts/10 00:00:00 grep --color=auto Die

 

Downloads>nc64 -zvu XXXXXX 26900-26905

FQDN [iP] 26905 (?) open

FQDN [iP] 26904 (?) open

FQDN [iP] 26903 (?) open

FQDN [iP] 26902 (?) open

FQDN [iP] 26901 (?) open

FQDN [iP] 26900 (?) open

 

Downloads>nc64 -zv IP 26900

FQDN [iP] 26900 (?) open

 

Downloads>

 

Taken from before I ran the netcat above (just server daemon traffic)

root@Ubuntu:~# tcpdump -an portrange 26900-26902

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on enp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes

08:35:19.085151 IP 192.168.2.40.26902 > 162.254.195.47.27020: UDP, length 84

08:35:28.130421 IP 192.168.2.40.26902 > 162.254.195.47.27020: UDP, length 84

08:35:28.512301 IP 162.254.195.47.27020 > 192.168.2.40.26902: UDP, length 36

08:35:37.171942 IP 192.168.2.40.26902 > 162.254.195.47.27020: UDP, length 84

08:35:46.214236 IP 192.168.2.40.26902 > 162.254.195.47.27020: UDP, length 84

08:35:55.247215 IP 192.168.2.40.26902 > 162.254.195.47.27020: UDP, length 84

08:35:55.662014 IP 162.254.195.47.27020 > 192.168.2.40.26902: UDP, length 36

[Alloc]

Sorry, for some reason I missed your reply.

 

Well, 26900 TCP is indeed open and server is running fine. I would make sure to triple-check that you also forwarded at least 26900 and 26901 on UDP to that server because I can't even get a response in Steam when pointing it right to your IP/port.

[Loadnabox]

I tried to remove traces of my IP, I missed one, I suppose that helped though :-D PM me if you need it again so it's not quite so public

 

You can see in the tcpdump that it was getting incoming on UDP 26902, but I'll go back and try again by tethering to my phone from a separate computer. I also note that steam on my local LAN doesn't identify it when listing servers. Maybe that's a clue.

 

Can you point me to information on how to specify it from within steam? I haven't run across that info before.

[Alloc]

Server browser traffic would be on 26901 though. Also it should indeed show up in the LAN tab if on the same network.

 

Steam: View -> Servers -> Favorites: Right click in the list -> Add by IP -> enter IP:port (port is the server browser port though, i.e. in this case 26901). Then select "Find games at this address" and it should either show your server or say nothing is responding.

[Loadnabox]

Server browser traffic would be on 26901 though. Also it should indeed show up in the LAN tab if on the same network.

 

Steam: View -> Servers -> Favorites: Right click in the list -> Add by IP -> enter IP:port (port is the server browser port though, i.e. in this case 26901). Then select "Find games at this address" and it should either show your server or say nothing is responding.

 

Hunh... doesn't find it even when specifying. I went through my router settings and disabled any uPnP related stuff (which was suggested in steam forums) but that didn't seem to help. The ports disappear from netstat when I stop the process for the 7dtd dedicated and don't show up even after a reboot until I restart, and the ports act like they're connecting when I scan. I can see my windows system hitting the unix system in a tcpdump when I manually attempt to scan it

 

16:30:06.637223 IP 192.168.2.50.50316 > 192.168.2.40.26901: UDP, length 25

[Alloc]

Yeah, everything looks fine from what I can see... Server set to public, TCP port reacting to requests, log does not show any issues either ... Sorry, but I'm out of ideas currently

[lazerblade01]

For most routers, as far as I know, you can only specify one port on one IP to forward to. Example: forwarded ports would be 26900-26902, internal port would be 26900 (same one listed in the serverconfig.xml file), internal IP would be 192.168.x.x (IP of dedicated machine) - and there can only be one set of port forwards that match this. However, I'm not a router expert. Is it possible that the forwarded ports are pointing to more than one destination IP or destination port? Do you have other ports forwarded for other systems on your network, or possibly an IP conflict that needs resolved? Did you reserve the IP address for your dedicated server in your router configuration so that rebooting the router or the dedicated server maintains the IP address assigned to the machine? Just throwing out some possible issues that may have been overlooked.

[Alloc]

The weird part is that he can't even get the server info on his local network, so at least not only a router issue

[lazerblade01]

The weird part is that he can't even get the server info on his local network, so at least not only a router issue

 

If the router is looking at the wrong IP then it could still be a router issue - looking at the wrong IP. Correct?

[Alloc]

Local (private) networks typically aren't routed but switched. There won't be a "looking at the wrong IP" in this case. Of course it could be routed but I highly doubt so

The router will only matter in his situation if someone's trying to connect from outside or Steam through the master server list but neither for looking for LAN games nor if he tells Steam to look at the local IP of his server directly (which it seems he did according to his last post). And this is why it's really weird here ... at least that part should always work (unless there's generic port conflict issues or similar)

[SylenThunder]

I'm a little surprised I haven't posted in this thread yet.

 

portforward.net is a good resource to check how you need to configure your particular equipment, and they have a lot of other information also.

 

 

If you cannot even see it on the local network though, it's almost certainly either a local routing issue or a firewall. As Alloc stated, most home networks aren't using internal routing, although I have seen some strange stuff on the newer modems ISP's are pushing. Most common issues are incorrect use of DMZ on the modem (just don't use it), duplicate IP addressing, or multiple port redirects (same port with conflicting rulesets, or similar).

[Loadnabox]

I have an ASUS RT-AC66U It can forward as many ports as I want to any port I want. I have verified this by looking at the ipchains output from the router. (underlying OS is linux based) Ipchains is tied to WAN port only on the router pointing to internal IP's

 

Both desktop and unix server are on an edge switch off of the main router so in theory if they're doing their jobs right they shouldn't be putting anything but broadcast packets to the router.

 

Physical ports

Router:

Switch 1 Interswitch Link

Switch 2 Interswitch Link

Smart TV

Fire TV

extra long spare cable

 

Switch 1:

Windows Desktop

Linux Server

Ooma

Work Laptop

Interswitch Link

 

Switch 2:

Wireless access point extension (repeater dumb mode)

Room 1

Room 2

Room 3

Interswitch Link