Has anyone had luck with a self hosted multiplayer server since A17

R

rykon1459918

New member
Not sure if its an issue or if my mate just failing so I wasn't sure if this should go here or the PC help section, so mods move it if you think its in the wrong area.

We had a a16 server all working with no issues.

He went and upgraded to a17 yesterday, internally I could connect to it but form external we just got timeouts, something was happening though as when the 7dtd server was down the external players got immediate error saying could not retrieve server connection but when it was up it was timing out after 15 seconds.

Things we tried and error checking:

Full re-install of the server's 7dtd game.

ran the error checking over of it (some kind of file constancy check I think through steam)

booted up Factorio server (same box) and put it on the 7dtd port (26900) no issue for external people to connect (checking ports and server was accessible)

Changed the 7dtd port.

opened the server to be as public as possible.

but we had no luck with any of this, if the player on his PC (not server) hosted a game himself we had no issue connecting it was just getting to the dedicated server on his network, we are connecting through direct IP if that helps.

If anyone has any suggestions that would be amazing.

 
Details on the host system would be good. Possibly they just ran out of usable RAM.

Logs would be helpful too. Moving this to the Support section. Check out the Sticky threads.

 
we had an issue with having to specify the port number, we didnt have to do that before. serverconfig.xml try specifying the port number (thank you guppycur)

 
Not sure if it's the same problem I had, or if it's something else.

1. Go into the serverconfig.xml file located in C:\Program Files(x86)\Steam\steamapps\common\7 Days to Die Dedicated Server\

2. Locate the line that says <property name="ServerDisabledNetworkProtocols" value="SteamNetworking"/>

3. Clear out the SteamNetworking value ... so it will look like this instead:

<property name="ServerDisabledNetworkProtocols"value=""/>

See if that works.

I had posted this on the b240 experimental bug report thread, someone from their support team got back to me and they were working with one of the devs. They had me do that and it fixed my problem. Even though the comment on that line says the following, it would not work despite my port 26900 being forwarded and those same port forwarding settings working for my a16.4 server: "Networking protocols that should not be used. Separated by comma. Possible values: LiteNetLib, SteamNetworking. Dedicated servers should disable SteamNetworking if there is no NAT router in between your users and the server or when port-forwarding is set up correctly"

I think they're either going to fix the problem or remove that value, but as of the stable build release it was not removed.

 
You must log in or register to reply here.
Back
Top