When connecting to my server from a computer on the same network, the VU client tries to connect to 127.0.0.1 rather than hair-pinning correctly (visible in the console.) Has anyone else experienced this and found a workaround?
Expected Behavior
VU connects to the local address (i.e. 192.168.x.x) or external IP
Topology
Router (Edgerouter, required ports forwarded)
└ Switch (192.168.1.1/24)
└ Server (itsteckel/vu:latest)
└ Client (player)
Probably a dupe of Server shows in list, but connections always fail
However, both server and client use the same subnet.
I ran into the same problem. Something goes wrong with Vu’s ip resolving when it is in bridge network mode. Try running your container in host mode if you’re hosting it in your local network. So pass --network host in docker run. See: https://docs.docker.com/network/host/
The container doesn’t need this when you host it in a data center elsewhere. Passing along a -joinaddr to vu.com or vu.exe doesn’t help either by the way.
Close, but different. Your server and client are on the same subnet, while mine are on different subnets; therefore the root cause for “connecting to 127.0.0.1” are different.
Same Subnet Cause:
GitHub Issue #556: Wrong IP when connecting to a server with the same public ip address
VU excludes certain VM network adapters from it’s NAT detection based on their MAC address prefix…
Unfortunately OrfeasZ doesn’t tell us which MAC address prefixes don’t trigger the NAT detection process.
Different Subnet Cause:
GitHub Issue #556: Wrong IP when connecting to a server with the same public ip address
I’ve identified the issue and it will be resolved in an upcoming build (probably live sometime next week). Keep in mind that you’ll need to have hairpinning properly set up in order to be able to connect to your server.
At the time of writing, the current version of VU Server was 17384.
[2020-12-31 14:02:17+00:00] [info] Initializing Venice Unleashed Server (Build 17384)…
[2020-12-31 14:02:17+00:00] [info] Mounting the VU game data File System.
[2020-12-31 14:02:24+00:00] [info] Remote Administration interface is listening on port 0.0.0.0:47200
[2020-12-31 14:02:24+00:00] [info] Successfully read startup configuration data.
[2020-12-31 14:02:24+00:00] [info] Loaded 0 entries from the player banlist file.
[2020-12-31 14:02:24+00:00] [info] Establishing connection to the Zeus Backend…
[2020-12-31 14:02:25+00:00] [info] Venice Unleashed dedicated server initialization finished.
[2020-12-31 14:02:25+00:00] [info] Successfully established connection to the Zeus Backend!
[2020-12-31 14:02:25+00:00] [info] Authenticating server with the Zeus Backend…
[2020-12-31 14:02:25+00:00] [info] Successfully authenticated server with Zeus (Server GUID: e8ff68f1bcc9490692355707c0868149).
[2020-12-31 14:02:25+00:00] [info] Checking for updates…
[2020-12-31 14:02:27+00:00] [info] Update check complete. No new updates available.
I was hoping to avoid host networking mode because I run a docker swarm. 
I’ll give it a shot!
I have the same problem. I am hosing on a windows PC in the network (same subnet) but not on a virtual machine. I can only connect to my own server on the hosting machine itself but not on any other machine on the local network.