[Server Crash Fixes + First Official Test Servers]

Thank you for the update. Is there a fix for adding servers to "Join via IP" which have the same IP but different game ports? (i.e. adding x.x.x.x:27000 and x.x.x.x 28000 display the same server).

[Server does not start on correct port]

I am attempting to run the server on custom ports (defaults +5). According to the server log, all the ports have been changed apart from the game port. It does have the correct port in the server.ini and at the start of the server logs, but further down the log it switches back to the default game port.

 

"C:\Users\avorion\bin\AvorionServer.exe" --datapath "C:\Users\avorion\galaxies" --galaxy-name galaxy1 --admin 0 --max-players 20 --port 28005 --query-port 27008 --steam-query-port 27025 --steam-master-port 27026 --use-steam-networking 1

 

Sun Jan 29 13:50:04 2017| Enabled Traces: 
Sun Jan 29 13:50:04 2017| Avorion server Beta 0.10.2 r7361 running on Windows 8.1+ starting up in "C:\Users\avorion\galaxies\galaxy1"
Sun Jan 29 13:50:04 2017| CPU: GenuineIntel 8 Cores
Sun Jan 29 13:50:04 2017| name: Avorion Server
Sun Jan 29 13:50:04 2017| seed: M7ONb4EPjo
Sun Jan 29 13:50:04 2017| port: 28005
Sun Jan 29 13:50:04 2017| max online players: 20
Sun Jan 29 13:50:04 2017| save interval: 600
Sun Jan 29 13:50:04 2017| broadcast interval: 5
Sun Jan 29 13:50:04 2017| max loaded sector time: 300
Sun Jan 29 13:50:04 2017| weak update: yes
Sun Jan 29 13:50:04 2017| worker threads: 1
Sun Jan 29 13:50:04 2017| difficulty: Veteran
Sun Jan 29 13:50:04 2017| infiniteResources: no
Sun Jan 29 13:50:04 2017| collision: 1
Sun Jan 29 13:50:04 2017| access list: Blacklist
Sun Jan 29 13:50:04 2017| public: yes
Sun Jan 29 13:50:04 2017| authentication: yes
Sun Jan 29 13:50:04 2017| listed: yes
Sun Jan 29 13:50:04 2017| steam networking & authentication: yes
Sun Jan 29 13:50:04 2017| administrators: 'admin' 
Sun Jan 29 13:50:04 2017| Warning: Command status has not been assigned to a user group.
Sun Jan 29 13:50:04 2017| Starting up 1 worker threads.
Sun Jan 29 13:50:04 2017| no file "C:\Users\avorion\galaxies\galaxy1\jumps.dat" found
Sun Jan 29 13:50:05 2017| Game Port: 27000
Sun Jan 29 13:50:05 2017| Steam Port: 27026
Sun Jan 29 13:50:05 2017| Steam Query Port: 27025
Sun Jan 29 13:50:05 2017| Polling Port: 27008
Sun Jan 29 13:50:05 2017| 
Sun Jan 29 13:50:05 2017| Server UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0
Sun Jan 29 13:50:06 2017| Server connected to Steam successfully
Sun Jan 29 13:50:06 2017| Server is VAC Secure!
Sun Jan 29 13:50:06 2017| 

[Patchnotes January 28th, 2017]

No parameters for binding IP addresses. You can see the commands by starting the server without any command line arguments or with --help.

 

How does one start the server without parameters? Simply running the following doesn't do anything (quits instantly). Works if I input all the required parameters.

 

bin\AvorionServer.exe --help

[Patchnotes January 28th, 2017]

Nice work! :)

 

What are the new server commands for setting ports? Also is there a command for binding to a specific IP address?

 

Thanks.

[Multiple Servers Same Machine]

Is there anyway to host multiple servers on the same machine?

 

When attempting to host a second server on a different port, I get the following error:

 

Thu Jan 26 18:32:17 2017| Server UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0
Thu Jan 26 18:32:17 2017| An exception occurred: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted

 

I have access to two IP addresses, and can use any other ports. So either can I bind the server to use a specific IP address (rather than localhost) or can I change change all the ports the server uses? It appears ports 27003, 27020 and 27021 remain un-changed when the game port is changed.

 

In-fact, if I turn listed and steam networking off the server only uses the game port. However, I still get the error above despite there being no port conflict.