7 Days to Die

7 Days to Die

View Stats:
Synergistics Dec 24, 2017 @ 8:14pm
Server Issues
Keep in mind, everything was working last night.

When trying to join my friends server, it comes up with the message "remote system is not running the game". Also, when trying to find his server in the populated server listings, it comes up with 192.168.1.7 which is a local/generic ip and not his actual ip and I think that is where the issue is coming from. Any ideas as to what would have changed over night to cause these issues?
< >
Showing 1-8 of 8 comments
Sullear Dec 25, 2017 @ 2:28am 
Is he running the game from his own system or a dedicated server? From what you described it sounds like he rins it on his own pc and you join in. If that is the case then you cannot join unless he has the game loaded and running. Otherwise if it is a dedicated server he needs to either restart the server or contact his host support.
Synergistics Dec 25, 2017 @ 5:51pm 
He is running it from his own machine but he is running the dedicated server program. Also, he (the host) is the only one out of our friends that are trying to join that IS able to join (a.k.a. he has the game running as well). We have restarted/redownloaded multiple times as well as restarting the computer to see if there was an issue with a server instance loading in the background that may have been interrupting things.

We just tried to have him set up a peer to peer server and I am able to connect. The peer to peer server has his correct IP connection listed 75.xxx.xxx.xxx but as i said, when he launched his dedicated server it populates his IP as 192.168.1.7 which is a local network IP. Any ideas as to what needs to be changed in the server settings to properly allow it to network out? as well as what would have changed over night to cause this issue?
Synergistics Dec 25, 2017 @ 6:08pm 
Update: My buddy is an idiot and I told him a x5 to check his port forwarding. We have no idea why it worked the first night but his port forwarding was only set up for TCP and not TCP/UDP which was causing the connection to not fully connect.

Issue Resolved
Ludi Jan 6, 2018 @ 5:09am 
We had the same problem. It worked at first but later we had the mentioned error message. Opening the ports at 26900 (standard value that is set in the serverconfig.xml by default) for TCP and UDP solved the problem for us too. Your last message helped us finding the solution. So thanks for the update.
QcMetalHead Aug 19, 2018 @ 1:15pm 
hello guys, sorry to revive an old thread but i have this same exact problem, i setup a server last night on my own pc, and played with a friend all night.
today it's not working, i tried all of the above (port fowarding) with not avail.
the only thing that changed since last night is that i downloaded the dedicated server from steam whereas last night i was just starting a server from the dedicatedserver .BAT file.
i did this because every time i started the server, i had to re-edit the serverconfig file.
any help would be appreciated.
QcMetalHead Aug 19, 2018 @ 1:18pm 
also my friend doesn't see my server in his favorites tab
QcMetalHead Aug 19, 2018 @ 1:43pm 
took me 2h 20min to figure but now it seems to be working!!!
i just edited this line in the serverconfig file to add ''SteamNetworking''

<property name="ServerDisabledNetworkProtocols" value="UNET, SteamNetworking"/>
Furstukin Dec 2, 2018 @ 2:40pm 
Originally posted by {Qc}MetalHead:
took me 2h 20min to figure but now it seems to be working!!!
i just edited this line in the serverconfig file to add ''SteamNetworking''

<property name="ServerDisabledNetworkProtocols" value="UNET, SteamNetworking"/>

This worked for me as well thanks so much for the tip
< >
Showing 1-8 of 8 comments
Per page: 1530 50

Date Posted: Dec 24, 2017 @ 8:14pm
Posts: 8