dedicated server not connecting to EOS
Submitted
Hello support
I'm trying to self host an instance of the dedicated server but having hard times doing so in a virtual environment:
I've managed to get an instance running on a fresh Windows 11 PC, with Console Compatibility set to True and Network Type set to EOS. It starts (tried with no admin rights and as a service with admin rights, both work) and me and friends are able to join the server and play from PS5.
Whenever I set up a fresh VM with Windows 11 (as did with the physical PC) the server does not starts, returning this error:
2025-02-21 11:24:07.777: Bind IP : 0.0.0.0:27016 2025-02-21 11:24:22.987: Server connect failure (User connect failed.) 2025-02-21 11:24:22.987: Error: No IP assigned. Server was stopped .Starting the server as local instance or as a service does not change the result. I've tried many VMs with different hypervisors located in different datacenters with different WAN connections with always the same result: bare metal works, virtualized not. I'm quite sure I'm missing something because I've been able to fire an instance from a docker version but it has really poor performances , at least in my case.
Has anyone ever faced this? I can't belive SP like nitrado are running each instance on bare metal server ahah
I have the same bug
Hello!
Thank you for contacting us. Since this is a bug report, I'm moving your ticket to our support page, where our QA team will take care of you.
Kind Regards
Keen Software House
Hello!
Thank you for contacting us. Since this is a bug report, I'm moving your ticket to our support page, where our QA team will take care of you.
Kind Regards
Keen Software House
Replies have been locked on this page!