0cyris

The only thing Digital Ocean was able to offer was it might be picking up the anchor IP use for their floating IP feature. Doesn't seem like much can be done without being able to configure IP address binding. As I said before Linode works great and has similar pricing so that my solution for now.

Setup a node on linode and it works fine so it must be something specific to Digital Ocean. I'll try contacting them since it means I have to use their competitor and post if I get an answer.

Just tried disabling them with the same result. The only other thing I've notice is in netstat with the address it's sending connections from when someone attempts to connect. netstat -atunp | grep Project tcp 0 0 10.13.0.5:55174 0.0.0.0:* LISTEN 3063/./ProjectZombo tcp 0 1 10.13.0.5:54385 192.168.0.10:52870 SYN_SENT 3063/./ProjectZombo tcp 0 1 10.13.0.5:49918 192.168.56.1:52871 SYN_SENT 3063/./ProjectZombo tcp6 0 0 :::27015 :::* LISTEN 3063/./ProjectZombo udp 0 0 10.13.0.5:51419 0.0.0.0:* 3063/./ProjectZombo udp 0 0 10.13.0.5:55068 0.0.0.0:* 3063/./ProjectZombo udp 0 0 0.0.0.0:16261 0.0.0.0:* 3063/./ProjectZombo udp 0 0 10.13.0.5:51188 0.0.0.0:* 3063/./ProjectZombo udp 0 0 0.0.0.0:8766 0.0.0.0:* 3063/./ProjectZombo Does it create some kind of tunnel? I know I don't have any interface up with an IP of 10.13.0.5 and since it's a non-routable address that's the only thing I can think of.

Server is running CentOS 7.2 x64 hosted by Digital Ocean have also tried Debian and Ubuntu. Every time someone tries to connect it fails with "onP2PSessionConnectFail" even without a firewall of any kind. I've tried just about everything I can think of and haven't been able to find anyone else with a working solution.