Hey there, new to the forum but been playing 7Days for a while. I managed to set up a VM running 17.4 with zero problems, but for some reason Alpha 18 is making me tear my hair out. When connecting with the 7Days PC client, with EAC enabled or disabled, I still get "Server Still Initializing" and disconnected.
I see it in the logs, the user connects but the message is displayed then user is kicked. Seeing how I had this working with 17.4, I know it isn't a network problem. My VM is fully bridged to my internal LAN and I can do nslookups and pings just fine from the VM. There is no port-forwarding or NAT happening here.
I tried to confirm the server was completely started by telnetting to localhost within the VM and issuing a command like 'spawnairdrop'. I figured if it wasn't fully ready that would throw an error. I didn't get any when I attempted this. I made sure in the serverconfig.xml to disable SteamNetworking for network protocols. (Though the log will still show complaints it isn't firing up.)
Anyone have an idea why "Server Still Initializing" would be displayed to the client even though the server seems ready to go?
I'd really appreciate it.
Pastebin Links:
https://pastebin.com/1m3E4mHf -- serverconfig.xml
https://pastebin.com/us2scsyS -- output.log
Googling about this problem didn't result in anything actionable, unfortunately.
I see it in the logs, the user connects but the message is displayed then user is kicked. Seeing how I had this working with 17.4, I know it isn't a network problem. My VM is fully bridged to my internal LAN and I can do nslookups and pings just fine from the VM. There is no port-forwarding or NAT happening here.
I tried to confirm the server was completely started by telnetting to localhost within the VM and issuing a command like 'spawnairdrop'. I figured if it wasn't fully ready that would throw an error. I didn't get any when I attempted this. I made sure in the serverconfig.xml to disable SteamNetworking for network protocols. (Though the log will still show complaints it isn't firing up.)
Anyone have an idea why "Server Still Initializing" would be displayed to the client even though the server seems ready to go?
I'd really appreciate it.
Pastebin Links:
https://pastebin.com/1m3E4mHf -- serverconfig.xml
https://pastebin.com/us2scsyS -- output.log
Googling about this problem didn't result in anything actionable, unfortunately.