Linux Dedicated Server not showing up on server list

[DracoPlaysGames]

Hello, I am running the newest version of Ubuntu on a home server.

Here is the command/output log that I use to start the server:



According to this image, it should be running correct?

I have forwarded all of my ports correctly (I created a server on my Windows machine last night and my friends could connect just fine) And yes, I have switched the internal IP addresses to my server's instead of my Windows machine.

Here are the ports (excuse my port names lol, 7dtd2 and f*ck are the ones that I use for my server):



And here is my output log.

I can provide any additional information if necessary,

Thanks!

 

[SylenThunder]

Can you upload your config file to pastebin?

I'm not seeing any issues in the log.

 

[DracoPlaysGames]

Is there any other way to troubleshoot this issue?

I just don't see it whatsoever on the server list, and I cannot direct connect to it at all or access the web console.

 

[DracoPlaysGames]

Can you upload your config file to pastebin?
I'm not seeing any issues in the log.

sorry about the late response, here is my config file.

 

[SylenThunder]

Still not seeing any issues. Do you have the ports opened in UFW?

 

[DracoPlaysGames]

Still not seeing any issues. Do you have the ports opened in UFW?

Yes sir,

my ports that opened are:

26900-26902 TCP/UDP


25000-25003 UDP

as shown in the second screenshot.

I installed LGSM, and it allowed me to connect to the web console, but I could not see it on the server list.

Here is a support thread that I opened earlier today that explains my problem in a little more detail.

EDIT:

Here are my UFW settings (I just started using Linux recently, so there are many things that I do not know yet)

 

[SylenThunder]

UFW isn't configured correctly. You're missing 26901, and 2500-25003 is not used since a15.

It should look more like this....

root@eden:/home/sdtd# ufw statusStatus: active


To                         Action      From
--                         ------      ----
20:22/tcp                  ALLOW       Anywhere
20:22/udp                  ALLOW       Anywhere
8080:8083/tcp              ALLOW       Anywhere
8080:8083/udp              ALLOW       Anywhere
26900:26903/tcp            ALLOW       Anywhere
26900:26903/udp            ALLOW       Anywhere
20:22/tcp (v6)             ALLOW       Anywhere (v6)
20:22/udp (v6)             ALLOW       Anywhere (v6)
8080:8083/tcp (v6)         ALLOW       Anywhere (v6)
8080:8083/udp (v6)         ALLOW       Anywhere (v6)
26900:27099/tcp (v6)       ALLOW       Anywhere (v6)
26900:27099/udp (v6)       ALLOW       Anywhere (v6)


root@eden:/home/sdtd/

- - - Updated - - -

To set the range of ports in UFW, you would use the following commands...

ufw allow 26900:26903/tcp

ufw allow 26900:26903/udp

ufw allow 8080:8083/tcp

ufw allow 8080:8083/udp

So I'd recommend clearing out what you have and re-doing it.

 

[DracoPlaysGames]

UFW isn't configured correctly. You're missing 26901, and 2500-25003 is not used since a15.
It should look more like this....

root@eden:/home/sdtd# ufw statusStatus: active


To                         Action      From
--                         ------      ----
20:22/tcp                  ALLOW       Anywhere
20:22/udp                  ALLOW       Anywhere
8080:8083/tcp              ALLOW       Anywhere
8080:8083/udp              ALLOW       Anywhere
26900:26903/tcp            ALLOW       Anywhere
26900:26903/udp            ALLOW       Anywhere
20:22/tcp (v6)             ALLOW       Anywhere (v6)
20:22/udp (v6)             ALLOW       Anywhere (v6)
8080:8083/tcp (v6)         ALLOW       Anywhere (v6)
8080:8083/udp (v6)         ALLOW       Anywhere (v6)
26900:27099/tcp (v6)       ALLOW       Anywhere (v6)
26900:27099/udp (v6)       ALLOW       Anywhere (v6)


root@eden:/home/sdtd/

- - - Updated - - -

To set the range of ports in UFW, you would use the following commands...

ufw allow 26900:26903/tcp

ufw allow 26900:26903/udp

ufw allow 8080:8083/tcp

ufw allow 8080:8083/udp

So I'd recommend clearing out what you have and re-doing it.

Here is my updated UFW rules:



I have 26900-26902 TCP/UDP open and it works just fine on my windows machine, should I open the 26900:26903 tcp/udp range instead just for this server?

And where does the 26901 range come into play here?

 

[SylenThunder]

I can never recall offhand what the specific ports are for, but 26901 may very well be used for server listing. You can open only to 26902, but sometimes they use 26903, and once even used 26904 in an experimental build. I keep the range 26900-26903 so that I don't run into an unexpected issue during experimental. I host several servers, and usually keep the port ranges 5 apart. (i.e. the next server range would be 26905-26908) Always better safe than sorry I say.

 

[DracoPlaysGames]

I can never recall offhand what the specific ports are for, but 26901 may very well be used for server listing. You can open only to 26902, but sometimes they use 26903, and once even used 26904 in an experimental build. I keep the range 26900-26903 so that I don't run into an unexpected issue during experimental. I host several servers, and usually keep the port ranges 5 apart. (i.e. the next server range would be 26905-26908) Always better safe than sorry I say.

Ok, so I am going to open 26900-26901 tcp/udp, 26900-26903 tcp/udp instead of the ports that I currently have open?

 

[SylenThunder]

Heh found the list...

[TABLE=class: wiki]

[TR]

[TH=bgcolor: #F0E68C]Port[/TH]

[TH=bgcolor: #F0E68C]Default[/TH]

[TH=bgcolor: #F0E68C]Protocol[/TH]

[TH=bgcolor: #F0E68C]Direction[/TH]

[TH=bgcolor: #F0E68C]Used for[/TH]

[/TR]

[TR]

[TD]BasePort+0[/TD]

[TD]26900[/TD]

[TD]UDP[/TD]

[TD]In[/TD]

[TD]Game (Steam's master server list interface)[/TD]

[/TR]

[TR]

[TD]BasePort+1[/TD]

[TD]26901[/TD]

[TD]UDP[/TD]

[TD]In[/TD]

[TD]Game (Steam communication)[/TD]

[/TR]

[TR]

[TD]BasePort+2[/TD]

[TD]26902[/TD]

[TD]UDP[/TD]

[TD]In[/TD]

[TD]Game (networking via RakNet)[/TD]

[/TR]

[TR]

[TD]BasePort+3[/TD]

[TD]26903[/TD]

[TD]UDP[/TD]

[TD]In[/TD]

[TD]Game (networking via UNET)[/TD]

[/TR]

[TR]

[TD]BasePort[/TD]

[TD]26900[/TD]

[TD]TCP[/TD]

[TD]In[/TD]

[TD]Game (Game details query port)[/TD]

[/TR]

[TR]

[TD]WebControlPort[/TD]

[TD]8080[/TD]

[TD]TCP[/TD]

[TD]In[/TD]

[TD]Web based control panel[/TD]

[/TR]

[TR]

[TD]TelnetPort[/TD]

[TD]8081[/TD]

[TD]TCP[/TD]

[TD]In[/TD]

[TD]"Telnet" control interface[/TD]

[/TR]

[TR]

[TD]WebControlPort+2[/TD]

[TD]8082[/TD]

[TD]TCP[/TD]

[TD]In[/TD]

[TD]Web Panel of the Server fixes[/TD]

[/TR]

[TR]

[TD]270xx[/TD]

[TD][/TD]

[TD]UDP[/TD]

[TD]Out[/TD]

[TD]Registering at the server list

[/TD]

[/TR]

[/TABLE]

 

[DracoPlaysGames]

Heh found the list...
[TABLE=class: wiki]

[TR]

[TH=bgcolor: #F0E68C]Port[/TH]

[TH=bgcolor: #F0E68C]Default[/TH]

[TH=bgcolor: #F0E68C]Protocol[/TH]

[TH=bgcolor: #F0E68C]Direction[/TH]

[TH=bgcolor: #F0E68C]Used for[/TH]

[/TR]

[TR]

[TD]BasePort+0[/TD]

[TD]26900[/TD]

[TD]UDP[/TD]

[TD]In[/TD]

[TD]Game (Steam's master server list interface)[/TD]

[/TR]

[TR]

[TD]BasePort+1[/TD]

[TD]26901[/TD]

[TD]UDP[/TD]

[TD]In[/TD]

[TD]Game (Steam communication)[/TD]

[/TR]

[TR]

[TD]BasePort+2[/TD]

[TD]26902[/TD]

[TD]UDP[/TD]

[TD]In[/TD]

[TD]Game (networking via RakNet)[/TD]

[/TR]

[TR]

[TD]BasePort+3[/TD]

[TD]26903[/TD]

[TD]UDP[/TD]

[TD]In[/TD]

[TD]Game (networking via UNET)[/TD]

[/TR]

[TR]

[TD]BasePort[/TD]

[TD]26900[/TD]

[TD]TCP[/TD]

[TD]In[/TD]

[TD]Game (Game details query port)[/TD]

[/TR]

[TR]

[TD]WebControlPort[/TD]

[TD]8080[/TD]

[TD]TCP[/TD]

[TD]In[/TD]

[TD]Web based control panel[/TD]

[/TR]

[TR]

[TD]TelnetPort[/TD]

[TD]8081[/TD]

[TD]TCP[/TD]

[TD]In[/TD]

[TD]"Telnet" control interface[/TD]

[/TR]

[TR]

[TD]WebControlPort+2[/TD]

[TD]8082[/TD]

[TD]TCP[/TD]

[TD]In[/TD]

[TD]Web Panel of the Server fixes[/TD]

[/TR]

[TR]

[TD]270xx[/TD]

[TD][/TD]

[TD]UDP[/TD]

[TD]Out[/TD]

[TD]Registering at the server list

[/TD]

[/TR]

[/TABLE]

Ok, I'll start forwarding.

But my only question is how come my Windows server worked perfectly fine with just the one port open, and this one is requiring me to forward 6+ more ports?

Is it because it's a different OS?

 

[SylenThunder]

Most likely because of the OS, yes. That's not the forwarding, that's the firewall.

Windows firewall is a lot weaker than Linux's.

 

[DracoPlaysGames]

Most likely because of the OS, yes. That's not the forwarding, that's the firewall.
Windows firewall is a lot weaker than Linux's.

Ok, I'll let you know what happens.

Thanks for the speedy reply!

- - - Updated - - -

Ok, I'll start forwarding.But my only question is how come my Windows server worked perfectly fine with just the one port open, and this one is requiring me to forward 6+ more ports?

Is it because it's a different OS?

One more quick question about the ports, since this table is just listing different variations of the 26900 range, would I include the 26900 range first then the different variations in the second?

For example, for the baseport+2, would I do the range 26900-26902 UDP?

 

[SylenThunder]

I just keep it like it is. It's a lot tidier to group them in the firewall rules. Technically you can just do 26900 TCP and then 26900-26902 UDP.

I am not certain why Alloc listed them that way in particular.

 

[DracoPlaysGames]

I just keep it like it is. It's a lot tidier to group them in the firewall rules. Technically you can just do 26900 TCP and then 26900-26902 UDP.
I am not certain why Alloc listed them that way in particular.

Ok, adding just 26900 TCP and then adding the range 26900-26902 UDP worked fine, then when I got to adding the 26900-26903 UDP range it said that it was in conflict with another port.

 

[SylenThunder]

Ok, adding just 26900 TCP and then adding the range 26900-26902 UDP worked fine, then when I got to adding the 26900-26903 UDP range it said that it was in conflict with another port.

If you set 26900-26902 UDP then you wouldn't set 26900-26903 UDP because the first three ports are the same. (Which is the cause for the error. You can just add 26903 by itself.