Page 1 of 3 123 LastLast
Results 1 to 15 of 31

Thread: Server not showing in server list

  1. #1
    Refugee
    Join Date
    May 2016
    Posts
    16
    Rep Power
    0

    Server not showing in server list

    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

    Routersettings.jpg

  2. #2
    Colony Founder lazerblade01's Avatar
    Join Date
    Jun 2014
    Posts
    2,842
    Rep Power
    1
    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.

  3. #3
    Fun Pimps Staff Alloc's Avatar
    Join Date
    Oct 2013
    Location
    Germany - Darmstadt
    Posts
    3,154
    Rep Power
    1
    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 ...)

  4. #4
    Colony Founder DEADication's Avatar
    Join Date
    Apr 2015
    Location
    Ballarat Aus
    Posts
    1,004
    Rep Power
    1
    Quote Originally Posted by Alloc View Post
    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??
    Last edited by DEADication; 05-17-2016 at 12:32 AM. Reason: posted wrong ports

  5. #5
    Refugee
    Join Date
    May 2016
    Posts
    16
    Rep Power
    0
    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?
    Last edited by Loadnabox; 05-17-2016 at 03:15 AM.

  6. #6
    Fun Pimps Staff Alloc's Avatar
    Join Date
    Oct 2013
    Location
    Germany - Darmstadt
    Posts
    3,154
    Rep Power
    1
    Quote Originally Posted by DEADication View Post
    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).



    Quote Originally Posted by Loadnabox View Post
    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.

  7. #7
    Colony Founder lazerblade01's Avatar
    Join Date
    Jun 2014
    Posts
    2,842
    Rep Power
    1
    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.

  8. #8
    Refugee
    Join Date
    May 2016
    Posts
    16
    Rep Power
    0
    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?

  9. #9
    Fun Pimps Staff Alloc's Avatar
    Join Date
    Oct 2013
    Location
    Germany - Darmstadt
    Posts
    3,154
    Rep Power
    1
    No idea, logs might have an indication of any issues (if there are any game side) though.

  10. #10
    Refugee
    Join Date
    May 2016
    Posts
    16
    Rep Power
    0
    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
    [email protected]:~/7DTD_server/7DaysToDieServer_Data$ netstat -l | grep 296
    [email protected]:~/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
    Last edited by Loadnabox; 05-18-2016 at 01:27 PM.

  11. #11
    Fun Pimps Staff Alloc's Avatar
    Join Date
    Oct 2013
    Location
    Germany - Darmstadt
    Posts
    3,154
    Rep Power
    1
    Quote Originally Posted by Loadnabox View Post
    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

  12. #12
    Refugee
    Join Date
    May 2016
    Posts
    16
    Rep Power
    0
    Quote Originally Posted by Alloc View Post
    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

    [email protected]:~/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 *:*

  13. #13
    Fun Pimps Staff Alloc's Avatar
    Join Date
    Oct 2013
    Location
    Germany - Darmstadt
    Posts
    3,154
    Rep Power
    1
    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.

  14. #14
    Refugee
    Join Date
    May 2016
    Posts
    16
    Rep Power
    0
    Logfile
    http://pastebin.com/W6Us4Tph



    [email protected]:~$ 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)
    [email protected]:~# 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
    Last edited by Loadnabox; 05-25-2016 at 07:18 PM.

  15. #15
    Fun Pimps Staff Alloc's Avatar
    Join Date
    Oct 2013
    Location
    Germany - Darmstadt
    Posts
    3,154
    Rep Power
    1
    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.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •