Announcement

Collapse
No announcement yet.

Server is not displayed in Steamlist

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Dedicated Server is not displayed in Steamlist

    Hello,
    my server is not displayed but running.
    The server is running on port 26910, the port is tcp and udp open.
    I tested the option to disable ServerDisabledNetworkProtocols value="SteamNetworking" to value=""

    here my log -> https://pastebin.com/v7WRBxah

    someone has an idea why the server might not be displayed?

    #2
    A lot more ports needed. See for example https://7dtd.illy.bz/wiki/Ports for a list. Steams seems to need lots of ports in the 27xxx range

    Comment


      #3
      Originally posted by meganoth View Post
      A lot more ports needed. See for example https://7dtd.illy.bz/wiki/Ports for a list. Steams seems to need lots of ports in the 27xxx range
      According to log, the server also registers with Steam, even without having previously enabled the ports.
      Still unlocked ports 270xx for udp and tcp.
      Server is still not listed.

      EDIT:
      i got in my log the following messages, if i want to connect:
      2019-12-08T18:28:00 35.190 INF [Steamworks.NET] GameServer.Init successful
      2019-12-08T18:28:00 35.194 INF [Steamworks.NET] Making server public
      2019-12-08T18:28:00 35.288 INF Calculating hashes took 4617 ms (world size 683 MiB)
      2019-12-08T18:28:01 36.689 INF [Steamworks.NET] GameServer.LogOn successful, SteamID=90131054866784257, public IP=x.x.x.x
      2019-12-08T18:28:15 50.689 INF [Steamworks.NET] NET: P2PSessionRequest from: 76561198065623711
      STEAMPS3 - AsyncTCPSocket created
      STEAMPS3 - AsyncTCPSocket created
      2019-12-08T18:28:35 70.721 INF [Steamworks.NET] NET: Connection closed: 76561198065623711
      STEAMPS3 - AsncTCPSocket destroyed
      STEAMPS3 - AsncTCPSocket destroyed
      2019-12-08T18:28:43 78.565 INF [Steamworks.NET] NET: P2PSessionRequest from: 76561198065623711
      STEAMPS3 - AsyncTCPSocket created
      STEAMPS3 - AsyncTCPSocket created
      2019-12-08T18:29:03 98.585 INF [Steamworks.NET] NET: Connection closed: 76561198065623711
      STEAMPS3 - AsncTCPSocket destroyed
      STEAMPS3 - AsncTCPSocket destroyed
      Last edited by Wolkenstein; 12-08-2019, 05:30 PM.

      Comment


        #4
        Originally posted by Wolkenstein View Post
        Still unlocked ports 270xx for udp and tcp.
        Unlocked? Have you just opened them or have you FORWARDED them on your router to the computer your server is running on? And additionally opened on the firewall on this computer?

        Comment


          #5
          Originally posted by Liesel Weppen View Post
          Unlocked? Have you just opened them or have you FORWARDED them on your router to the computer your server is running on? And additionally opened on the firewall on this computer?
          I open the ports at my server, like for other gameservers like minecraft. The server is running in a datacenter, i haven't a router where i have to forward the traffic.

          7D2D:
          ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:26910
          ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:26910


          Steam:
          ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 27015:27099
          ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 27015:27099
          top shows me the server running and the console(running in a screen) say it too.
          I think steam don't want to talk with me, although the ports are open.

          Comment


            #6
            Can you connect to the server by ip?

            So when 26910 is your base port, whats with the ports 26911-26913?
            Last edited by Liesel Weppen; 12-08-2019, 08:18 PM.

            Comment


              #7
              Originally posted by Liesel Weppen View Post
              Can you connect to the server by ip?

              So when 26910 is your base port, whats with the ports 26911-26913?
              26911-26913 are open too.
              I can't connect to the gameserver with IP:Port, if remove the ServerDisabledNetworkProtocols value="SteamNetworking" to value="", the server gets a notice, gets the info that someone wants to log in, but then gets a time out.

              Comment


                #8
                Yeah they don't have all the ports listed that you need. You need to allow a specific Steamworks networking server to connect to your server, and they don't use fixed ports. They do, however, have static IPs. Here's the thread where I found out how to do all this: https://7daystodie.com/forums/showth...Steamworks-NET

                Here's the list of the Steamworks servers: https://bgp.he.net/AS32590#_prefixes

                You'll likely need something like Wireshark to see which Steamworks servers are trying to connect to your server, then allow their IPs through the firewall. There will only be one that you need to add.

                Comment


                  #9
                  You will need to have port 26910 TCP open and forwarded to the server.
                  You will need to have ports 26910-26913 UDP open and forwarded to the server.

                  It's usually easiest to just set up one rule to forward 26910-26913 with both TCP and UDP.

                  You should also forward ports 27000-27100 both TCP and UDP.

                  Don't forget to exclude the server client from your firewall.

                  Lastly, make sure that your server visibility option is set to "2".

                  Comment


                    #10
                    Those ports won't work for the Steamworks server that tries to connect to it, as it will use a random port above 3000.

                    Comment


                      #11
                      Originally posted by FiftyTifty View Post
                      Those ports won't work for the Steamworks server that tries to connect to it, as it will use a random port above 3000.
                      Those are not required to be forwarded for the client. They never have been.
                      I don't know why you insist in pushing this wholly incorrect information.

                      Code:
                      root@beta:~# netstat -lntup | grep 21451tcp        0      0 0.0.0.0:8086            0.0.0.0:*               LISTEN      21451/./7DaysToDieS
                      tcp        0      0 0.0.0.0:8087            0.0.0.0:*               LISTEN      21451/./7DaysToDieS
                      tcp        0      0 0.0.0.0:8088            0.0.0.0:*               LISTEN      21451/./7DaysToDieS
                      tcp        0      0 0.0.0.0:26905           0.0.0.0:*               LISTEN      21451/./7DaysToDieS
                      udp        0      0 0.0.0.0:26905           0.0.0.0:*                           21451/./7DaysToDieS
                      udp        0      0 0.0.0.0:26907           0.0.0.0:*                           21451/./7DaysToDieS
                      udp6       0      0 :::26907                :::*                                21451/./7DaysToDieS
                      26905 is the game port.
                      26907 is the query port.
                      8086 is Console
                      8087 is Telnet
                      8088 is the web API. If you do not have Allocs Server Fixes installed, you will not have this port.

                      Notice how there are no other ports in use?

                      Comment


                        #12
                        Ok i setup the Server on a different server in my network.
                        Exactly the same issue.

                        server with steam listining problem(GS00 | Server 1):
                        Code:
                        root@GS00:~# netstat -lntup | grep 34680
                        tcp        0      0 127.0.0.1:8081          0.0.0.0:*               LISTEN      34680/./7DaysToDieS
                        tcp        0      0 0.0.0.0:26900           0.0.0.0:*               LISTEN      34680/./7DaysToDieS
                        udp        0      0 0.0.0.0:26900           0.0.0.0:*                           34680/./7DaysToDieS
                        udp        0      0 0.0.0.0:26902           0.0.0.0:*                           34680/./7DaysToDieS
                        udp6       0      0 :::26902                :::*                                34680/./7DaysToDieS
                        different network and different server, where the same 7D2D files running without problems(GSFN | Server 2):
                        Code:
                        root@GSFSN ~ # netstat -tulnp | grep 12226
                        tcp        0      0 0.0.0.0:26930           0.0.0.0:*               LISTEN      12226/./7DaysToDieS
                        udp        0      0 0.0.0.0:26930           0.0.0.0:*                           12226/./7DaysToDieS
                        udp        0      0 0.0.0.0:26932           0.0.0.0:*                           12226/./7DaysToDieS
                        udp6       0      0 :::26932                :::*                                12226/./7DaysToDieS
                        on both server the firewall rules the same:

                        (GS00 | Server 1) the server with problem:
                        Code:
                        root@GS00:~# iptables -nL | grep -E "26900|26902|27000:27099"
                        ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:26902
                        ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:26902
                        ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:26900
                        ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:26900
                        ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpts:27000:27099
                        ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpts:27000:27099
                        (GSFN | Server 2) the server without problem:
                        Code:
                        root@GSFSN ~ # iptables -nL | grep -E "26930|26932|27000:27099"
                        ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:26930
                        ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:26930
                        ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:26930
                        ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:26930
                        ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            udp dpts:27000:27099
                        ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpts:27000:27099

                        Comment


                          #13
                          Are you using UFW?

                          Comment


                            #14
                            Problem is fixed.
                            The Datacenter installed the days a new port filtering, which filtert the 7d2d traffic.
                            I wrote them yesterday a email, with a strack trace and the connection problem for just 7d2d. They called the filter IMCP(i think they mixed the M and the C - ICMP).
                            Few minutes ago they deactivate the function and it worked again.
                            I can connect and the server shows up again at the steamlist.
                            Thanks for your help guys

                            Comment


                              #15
                              Originally posted by SylenThunder View Post
                              Those are not required to be forwarded for the client. They never have been.
                              I don't know why you insist in pushing this wholly incorrect information.

                              Code:
                              root@beta:~# netstat -lntup | grep 21451tcp        0      0 0.0.0.0:8086            0.0.0.0:*               LISTEN      21451/./7DaysToDieS
                              tcp        0      0 0.0.0.0:8087            0.0.0.0:*               LISTEN      21451/./7DaysToDieS
                              tcp        0      0 0.0.0.0:8088            0.0.0.0:*               LISTEN      21451/./7DaysToDieS
                              tcp        0      0 0.0.0.0:26905           0.0.0.0:*               LISTEN      21451/./7DaysToDieS
                              udp        0      0 0.0.0.0:26905           0.0.0.0:*                           21451/./7DaysToDieS
                              udp        0      0 0.0.0.0:26907           0.0.0.0:*                           21451/./7DaysToDieS
                              udp6       0      0 :::26907                :::*                                21451/./7DaysToDieS
                              26905 is the game port.
                              26907 is the query port.
                              8086 is Console
                              8087 is Telnet
                              8088 is the web API. If you do not have Allocs Server Fixes installed, you will not have this port.

                              Notice how there are no other ports in use?
                              Literally explained why to you, in the same thread I found that out: https://7daystodie.com/forums/showth...Steamworks-NET

                              Comment

                              Working...
                              X