Search the Community

So, im trying to setup at server for a friend and his group, but im running into this issue after installing it with steamCMD and doing main setup it wont listen on the primary game ports. and the stream ports 27003/udp, 27020/udp and some others direct ports with steam are listed and booted up, but port no 27000/tcp or udp is being listened to. To show how i see the ports active after my start sricpt is launched i run command `lsof` and it returns this. na@game-1:~$ sudo lsof -i -P -n COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME ....SSHD etc above. java 4235 na 136u IPv6 53976 0t0 TCP ipv4:25566 (LISTEN) #Minecraft server. which works. AvorionSe 10192 na 18u IPv4 78355 0t0 TCP ipv4:60497->extClientIp:27019 (ESTABLISHED) AvorionSe 10192 na 19u IPv4 78351 0t0 UDP ipv4:27020 AvorionSe 10192 na 36u IPv4 117889 0t0 UDP ipv4:27003 This is the only Ports is listening to after running this file as `./start.sh` #!/bin/bash # --ip is to set the right interface which uses that ip instead of */* any interface. ./server.sh --galaxy-name techw --admin *** --datapath *** --ip *** --public 1 --listed 1 --use-steam-networking 1 Which then gives these output in log na@game-1:/servers/avorion1$ ./start.sh Enabled Traces: Avorion server 2.3.1 4e8ec3bad8ad running on Ubuntu 22.04.2 LTS starting up in "/servers/techw/avorion1/galaxies/test" Version Hash: -8337054028857598234 CPU: AMD Ryzen 7 5800X 8-Core Processor 16 Cores RAM: 62GB Starting game server on ip IPV4.ITS.LISTED.ON, *** Server version, as listed publicly: 2.3.1.40236 [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. CAppInfoCacheReadFromDiskThread took 1 milliseconds to initialize Setting breakpad minidump AppID = 445220 Server connected to Steam successfully Server is VAC Secure! Game Server Steam ID: *** Game Port: 27000 Steam Port: 27021 Steam Query Port: 27020 Query Port: 27003 Steam Networking initialized. then runs the galaxy settings and displays it .... Server startup complete. I have No idea why it wont listen on the port or what i can to for it for them to beable to get them to join. i hope you can come with some inputs on how this can be solved bcz for me it seems weird or generally i wann rule out if its my server or avorions... Fire wall is displayed done by this. na@game-1:~$ sudo ufw status To Action From -- ------ ---- 25565:25570/udp ALLOW Anywhere # Minecraft 25565:25570/tcp ALLOW Anywhere # Minecraft 27000:27037/tcp ALLOW Anywhere # Steam Servers TCP 27000:27037/udp ALLOW Anywhere # Steam Servers UDP 25565:25570/udp (v6) ALLOW Anywhere (v6) # Minecraft 25565:25570/tcp (v6) ALLOW Anywhere (v6) # Minecraft 27000:27037/tcp (v6) ALLOW Anywhere (v6) # Steam Servers TCP 27000:27037/udp (v6) ALLOW Anywhere (v6) # Steam Servers UDP

Is there a location to inform us what is included in any updates? I couldn't find anything on Steam or this forum about the 600K update Steam installed for Avorion today. Any information would be helpful.

Idk if this is a unique issue or if everyone has it, but launching the game from the .exe just gives a steam error: "Failed to initialize Steam API, please restart Steam and try again." Doesn't seem to have anything to do with anything, the game runs fine if launched through steam. Not an issue with about any other steam game of the nearly 1,000 I have. Can't create a custom shortcut using steam url, would like to know if everyone has this, and if it can be fixed? Addendum: Tried restart, validate, reinstall, no fix. Latest Beta, issue since start of sept earliest recall. Win 10 x64

With the new great update of the game a lot of players are having the returning problem of not being able to connect to servers that haven't been updated yet. It may take a while for the mods to be updated as well so it occasionally happens that the playerbase is leaving the server for one that you actually can play on. Adding recent/older versions for users to select may help during the "transition phase". I can see the problem of not giving the admins/modders a hard enough insentive to update which in return will hurt the gameplay experience long term but I also think this is outweighted by basically abandoning your game you spent the last weeks on. Because lets be honest, once you started somewhere else it's hard to return to an old galaxy. I imagine this has been on the table in the past but haven't seen anything on the first couple of pages here. Any thoughts?