"No connection could be made because the target machine actively refused it"

[MinimumEffort]

Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0


IP Address removed as I don't want my IP to be public. I run the server from my Windows machine, the same machine I run the game from. The lag is horrendous if I or my friend connect remotely, via the public IP. If I connect with the localhost (127.0.0.1) I have no issues.

The message above is typically output by .NET network assemblies when a firewall is blocking communication. My router firewall has ports 27000 - 27050 for UDP and TCP forwarded to my machine. My machine has the Windows Firewall disabled. The only Anti-Virus tool I have running is Windows Defender.

Any idea what else could be wrong?

[MinimumEffort]

I also see this in the server log -

2017-03-28 20-41-46| SteamGameServer_Init call failed
2017-03-28 20-41-46| Error starting steam-based networking. Falling back to standard TCP/UDP protocols.
2017-03-28 20-41-46| Server UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0
2017-03-28 20-41-46| The server will not be authenticated via Steam and won't show up in public server lists.
2017-03-28 20-41-46| WARNING: The fallback TCP/UDP protocols are deprecated and potentially UNSAFE!
2017-03-28 20-41-46| Server UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0
2017-03-28 20-41-46| If you're running a dedicated server, this is HIGHLY discouraged!
2017-03-28 20-41-46| Use steam networking instead; Enable with --use-steam-networking 1

But even if I try to enable steam networking, it never works. I run the server by double-clicking the server.bat file that is provided with the install.

[kaashy]

Have you tried using the Avorion Dedicated server tool? Does it work when running it via the launcher through Steam?

[MinimumEffort]

What is the Avorion Dedicated server tool and where do I get it?

There is no way that I know of to launch the server through Steam, how do you do that?

[kaashy]

There should be a "Avorion Dedicated Server" entry in the tools of your steam library. There's a launcher included. That tool is meant for hosting dedicated servers on their own machines, and it should work with Steam not running.

[MinimumEffort]

I do not have anything in my tools with Avorion in the name

[MinimumEffort]

and to clarify, Steam is always running on my computer.

[MinimumEffort]

I did a check of file integrity and it said it found 1 file that was damaged, but I still don't see an option for an "Avorion Dedicated Server" tool.

I then uninstalled the game and reinstalled it. Still nothing in the tool section.

After reinstalling the game and running server.bat I get the same errors as before.

2017-03-29 21-35-25| Enabled Traces:
2017-03-29 21-35-25| Avorion server Beta 0.11 r7854 running on Windows 8.1+ starting up in "C:\Users\tom\AppData\Roaming\Avorion\galaxies\avorion_galaxy"
2017-03-29 21-35-25| CPU: GenuineIntel 8 Cores
2017-03-29 21-35-25| name: Avorion Server
2017-03-29 21-35-25| seed: tXw1DVEcAw
2017-03-29 21-35-25| port: 27000
2017-03-29 21-35-25| max online players: 10
2017-03-29 21-35-25| save interval: 300
2017-03-29 21-35-25| broadcast interval: 5
2017-03-29 21-35-25| max loaded sector time: 300
2017-03-29 21-35-25| weak update: yes
2017-03-29 21-35-25| worker threads: 1
2017-03-29 21-35-25| generator threads: 2
2017-03-29 21-35-25| difficulty: Veteran
2017-03-29 21-35-25| infiniteResources: no
2017-03-29 21-35-25| collision: 1
2017-03-29 21-35-25| access list: Blacklist
2017-03-29 21-35-25| public: yes
2017-03-29 21-35-25| authentication: yes
2017-03-29 21-35-25| listed: yes
2017-03-29 21-35-25| steam networking: yes
2017-03-29 21-35-25| administrators: 'avorion_admin'
2017-03-29 21-35-25| Initializing sector database...
2017-03-29 21-35-25| Initializing faction database...
2017-03-29 21-35-26| Starting up 1 worker threads...
2017-03-29 21-35-26| Loading jumping entities...
2017-03-29 21-35-26| Loaded 56 jumping entities.
2017-03-29 21-35-26| Loading groups...
2017-03-29 21-35-26| Galaxy initialized.
2017-03-29 21-35-26| Listed server version: 0.11.0.7854
2017-03-29 21-35-26| SteamGameServer_Init call failed
2017-03-29 21-35-26| Error starting steam-based networking. Falling back to standard TCP/UDP protocols.
2017-03-29 21-35-26| Server UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0
2017-03-29 21-35-26| The server will not be authenticated via Steam and won't show up in public server lists.
2017-03-29 21-35-26| Server UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0
2017-03-29 21-35-26| WARNING: The fallback TCP/UDP protocols are deprecated and potentially UNSAFE!
2017-03-29 21-35-26| If you're running a dedicated server, this is HIGHLY discouraged!
2017-03-29 21-35-26| Use steam networking instead; Enable with --use-steam-networking 1
2017-03-29 21-38-26| Connection to player established
2017-03-29 21-38-27| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-29| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-29| <Server> Player tomince joined the galaxy
2017-03-29 21-38-29| Player logged in: tomince, index: 5
2017-03-29 21-38-29| scheduled save for sector (-2:-9), 0x4027190, entities: 30
2017-03-29 21-38-29| saving sector (-2:-9)
2017-03-29 21-38-29| sector (-2:-9) saved to "C:\Users\tom\AppData\Roaming\Avorion\galaxies\avorion_galaxy\sectors\-2_-9"
2017-03-29 21-38-30| player events roughly every 13.52 minutes
2017-03-29 21-38-30| scheduled save for sector (-2:-9), 0x4027190, entities: 30
2017-03-29 21-38-30| saving sector (-2:-9)
2017-03-29 21-38-30| sector (-2:-9) saved to "C:\Users\tom\AppData\Roaming\Avorion\galaxies\avorion_galaxy\sectors\-2_-9"
2017-03-29 21-38-30| Player tomince moved to sector (-2:-9) server time taken for change: 29ms
2017-03-29 21-38-30| scheduled save for sector (6:-74), 0x6138470, entities: 832
2017-03-29 21-38-30| saving sector (6:-74)
2017-03-29 21-38-30| sector (6:-74) saved to "C:\Users\tom\AppData\Roaming\Avorion\galaxies\avorion_galaxy\sectors\6_-74"
2017-03-29 21-38-30| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-31| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-32| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-33| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-34| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-35| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-36| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-37| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-38| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-39| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-40| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-41| Server UDP: Error receiving from xxx.xxx.xxx.xxx, error: No connection could be made because the target machine actively refused it, received bytes: 0
2017-03-29 21-38-41|

[MinimumEffort]

When logging out of the server I see this -

Server: connection xxx.xxx.xxx.xxx:64874 was closed by remote

Why is it using port 64874?

EDIT: Check via Wireshark and this is just the local bound port the server assigned to receive communications via port 27000.

[MinimumEffort]

I put my machine in the DMZ on my router and now I'm not getting the Server UDP errors. I have ports 27000 - 27050 forwarded to my machine, so are there other ports I should have opened up?

(Leaving my machine in the DMZ is not a long term solution)

[kaashy]

You shouldn't need any. For outgoing UDP connections a random port is assigned, but you don't have to enable port forwarding for outgoing connections. Here's an article on the wiki which describes how to set up a dedicated server: http://avorion.gamepedia.com/Setting_up_a_server

[MinimumEffort]

I believe I have resolved this. More testing will tell but I was able to play from work today for about 30 minutes with no lag...first time ever!

The fix was to explicitly define each port that I wanted to forward in my router. For example, when it wasn't working I had my router setup to forward ports 27000 - 27050 for both UDP and TCP to my machine. I deleted that rule and added two rules, forward 27000 UDP/TCP and 27003 UDP. With the new rules for ports 27000 and 27003 only everything seems to be working now.

Maybe a bug in my modem/router? It's provided by Spectrum (a terrible cable company) and is running Arris firmware, I'll go check for model # later.

[kaashy]

Glad to hear you resolved it!