Having issues connecting to multiplayer server

[chris13524]

So I'm trying to setup a dedicated multiplayer server. This is on a Ubuntu 18 .04 DigitalOcean instance. I followed the wiki article on how to do so here: https://avorion.gamepedia.com/Setting_up_a_server#Setting_up_the_Server_.28Linux.29

 

The issue I'm having is with connecting to this server.  When I start it using these options:

 

./.steam/steamcmd/hu-avorion/server.sh --galaxy-name "HU Galaxy" --datapath /root --admin mechris13524 --use-steam-networking 0

 

And when I go to connect to this server (by opening Avorion, going to multiplayer, selecting Join by IP, and typing in the server's domain name), it takes exactly (and I mean exactly) 60-61 seconds before the "Connecting..." turns into "Loading...". I've tested this an upwards of 10 times, and each time it takes exactly 60-61 seconds. Very reproducible and fishy.

 

If I change the flag to USE Steam networking (--use-steam-networking 1), it still takes exactly 60-61 seconds, but then instead of connecting, it gives me the error: Connection to xxx.xxx.com:27000 failed: Server unreachable

 

When Steam networking is ON, I see this in the server logs during the 60 second connection cycle:

OnP2PSessionRequest from 76561198027014673

STEAMPS3 - AsyncTCPSocket created

STEAMPS3 - AsyncTCPSocket created

Client 76561198027014673 lost connection

STEAMPS3 - AsncTCPSocket destroyed

STEAMPS3 - AsncTCPSocket destroyed

Ending authentication session of 76561198027014673

 

Also when Steam networking is ON, I see this during the startup sequence:

Listed server version: 0.17.1.12316

[s_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.

Setting breakpad minidump AppID = 445220

Game Port: 27000

Steam Port: 27021

Steam Query Port: 27020

Query Port: 27003

 

Using the command `netstat -ntulp`, I see that when Steam networking is OFF, these are the things listening:

tcp        0      0 0.0.0.0:27000          0.0.0.0:*              LISTEN      2752/./bin/AvorionS

udp        0      0 0.0.0.0:27000          0.0.0.0:*                          2752/./bin/AvorionS

udp        0      0 0.0.0.0:27003          0.0.0.0:*                          2752/./bin/AvorionS

 

When steam networking is OFF, these are the things listening:

udp    11520      0 0.0.0.0:27003          0.0.0.0:*                          2596/./bin/AvorionS

udp        0      0 0.0.0.0:27020          0.0.0.0:*                          2596/./bin/AvorionS

udp    22272      0 0.0.0.0:44702          0.0.0.0:*                          2596/./bin/AvorionS

 

It seems the cause of the error "Connection to xxx.xxx.com:27000 failed: Server unreachable" when Steam networking is on could be caused by the fact that the server isn't even listening on 27000.

 

I'm happy to provide more information about the server, or my client environment. The behavior is consistent across a few different networks (including my college network and my phone's hotspot).

[Devious]

Do you have all the required ports forwarded?

 

    tcp/27000

    udp/27000

    udp/27003

    udp/27020 

    tcp/27020 

    udp/27021 

    tcp/27021

 

Also , --admin needs your Steam64 ID.

 

It might also be that DO doesn't play nice, I'm not 100% sure but I think someone else had similar issues with it.

[chris13524]

We do not have a firewall enabled, so there shouldn't be any need to forward anything. I'm able to connect, but only after the suspicious 60-second delay.

[DrMasik]

Sorry for poor English.

 

1) Never use root account for game servers and any other servicies

2) Trun off firewall and Ubuntu (google + "ubuntu 18.04 firewall")

3) Check your DNS configuration (back-resolving for IP)

4) Use tcpdump for debug traffiic :)

5) Try to add:

--public 1

--listed 1

--use-steam-networking 1

 

[Decappi]

Any updates, chris13524? I'm having the same issues here.