thejduman Posted June 12, 2020 Share Posted June 12, 2020 Can't connect to my dedicated server after update I have been running a dedicated server for me and a few friends for a couple of days now. However, after installing the updates yesterday neither me or my friends can connect to my server. The server does not show up in my favorites list in game and I am unable to connect to it using the Steam server browser. Additionally, I can't connect to it locally. The ports are forwarded correctly. I had recently switched the server to the Crystal Isles map, would that affect anything? Also, after installing the update I noticed that I have been getting the gethostbyname error, but I have been told that this doesn't affect anything. If anyone is able to help me with this issue I would really appreciate it. Link to comment Share on other sites More sharing options...
JoeKeyFar Posted June 13, 2020 Share Posted June 13, 2020 The same problem. I try to join to my dedicated server and get "Joining Failed! Connection Timeout". I use Epic Games Launcher. Ports are opened too. And the same "gethostbyname error" if it affects something. Link to comment Share on other sites More sharing options...
pleinx Posted June 13, 2020 Share Posted June 13, 2020 Same issue here. Since the Update 311.88 (Linux, no RawSockets) i can't connect to my (steam) server. The other Servers with the version 311.87 still works and can join. Link to comment Share on other sites More sharing options...
GyozaGuy Posted June 14, 2020 Share Posted June 14, 2020 I run two Linux servers on my local network and port forward them so my community can join. After the update I had to open extra ports just to be able to connect to my Linux servers within my local network (e.g. used to work with only port 7778, now I have to open 7778 and 7777 for a single server). But they are still inaccessible from anybody outside my local network. Link to comment Share on other sites More sharing options...
JoeKeyFar Posted June 14, 2020 Share Posted June 14, 2020 I solved the same problem with my server. Are you sure you followed these official instructions? "Necessary Server Args: -crossplay (enables Crossplay on Dedicated Server) -epiconly (enables Epic Game Store only players to connect to the Dedicated Server) -UseVivox (enables Vivox on Steam only servers)" So your batch file should contain "-crossplay" at the end of the line. If you cannot access your dedicated server with the same computer, you need to enable a NAT-loopback in addition to port forwarding on router. I could not solve this problem for a very long time and it turned out that the here was point. Link to comment Share on other sites More sharing options...
GyozaGuy Posted June 14, 2020 Share Posted June 14, 2020 Unfortunately the rest of us in this thread are not using the Epic version. Link to comment Share on other sites More sharing options...
thejduman Posted June 15, 2020 Author Share Posted June 15, 2020 22 hours ago, GyozaGuy said: I run two Linux servers on my local network and port forward them so my community can join. After the update I had to open extra ports just to be able to connect to my Linux servers within my local network (e.g. used to work with only port 7778, now I have to open 7778 and 7777 for a single server). But they are still inaccessible from anybody outside my local network. I currently only have my game port forwarded on my router. Should I try forwarding any other ports? Also I am running my server on Windows. 14 hours ago, JoeKeyFar said: I solved the same problem with my server. Are you sure you followed these official instructions? "Necessary Server Args: -crossplay (enables Crossplay on Dedicated Server) -epiconly (enables Epic Game Store only players to connect to the Dedicated Server) -UseVivox (enables Vivox on Steam only servers)" So your batch file should contain "-crossplay" at the end of the line. If you cannot access your dedicated server with the same computer, you need to enable a NAT-loopback in addition to port forwarding on router. I could not solve this problem for a very long time and it turned out that the here was point. Do I need to have any of these arguments in order for my server to show up? All of my friends and I are using the Steam version. I am running the server on a different computer than the one I am playing on, so that's the one I am trying to connect on in my local network. What is a NAT-loopback and would I want to try doing it? Link to comment Share on other sites More sharing options...
JoeKeyFar Posted June 15, 2020 Share Posted June 15, 2020 9 hours ago, thejduman said: I currently only have my game port forwarded on my router. Should I try forwarding any other ports? Also I am running my server on Windows. Do I need to have any of these arguments in order for my server to show up? All of my friends and I are using the Steam version. I am running the server on a different computer than the one I am playing on, so that's the one I am trying to connect on in my local network. What is a NAT-loopback and would I want to try doing it? These arguments help me to see server on my Epic version. IDK about steam. About NAT. Depends on the model of the router. Check your own. In my case, the ability to enable the NAT-loopback is for each port that I open, or/and through the enable DMZ. I do not realy know how the NAT-loopback functions, I don't realy know how the DMZ functions, but it exactly worked in my case. Link to comment Share on other sites More sharing options...
GyozaGuy Posted June 15, 2020 Share Posted June 15, 2020 Be very careful with the DMZ, it stands for "demilitarized zone" and basically what that does is let you put one of your devices outside the router's firewall, out in the open on the internet. If the device is not properly protected it can be very dangerous. Link to comment Share on other sites More sharing options...
JoeKeyFar Posted June 15, 2020 Share Posted June 15, 2020 If you do not see the server in the list from Steam, you can prescribe the IP address of your dedicated server in your "favorites" in steam>view>servers. Do not forget to specify the port 7777. For example, "12.34.567.89:7777". It helped my friend see my server. He's on Steam, I'm in Epic. Link to comment Share on other sites More sharing options...
thejduman Posted June 15, 2020 Author Share Posted June 15, 2020 Just now, JoeKeyFar said: If you do not see the server in the list from Steam, you can prescribe the IP address of your dedicated server in your "favorites" in steam>view>servers. Do not forget to specify the port 7777. For example, "12.34.567.89:7777". It helped my friend see my server. He's on Steam, I'm in Epic. I have already tried this and it says the server is not responding. Link to comment Share on other sites More sharing options...
JDawg35 Posted June 16, 2020 Share Posted June 16, 2020 I'm assuming you're using the Steam view servers>favorites tab. Are you trying external IP or internal IP? If neither are working, then it's either a port forwarding issue, or the server simply isn't set up correctly. RE: NAT loopback (hairpinning): This allows you to access your server via external IP which is important for server clustering. Without it, you won't be able to transfer your character between the servers you're hosting (players outside of your home network will not have this problem since they're already using external IP). A recent update seems to have broken this though. If anyone else has a solution to this issue, please reply. I was hoping latest patch that re-enabled "multihome" would resolve it but no luck here. I'm still only able to connect using the internal IP. Link to comment Share on other sites More sharing options...
GyozaGuy Posted June 16, 2020 Share Posted June 16, 2020 27 minutes ago, JDawg35 said: I'm assuming you're using the Steam view servers>favorites tab. Are you trying external IP or internal IP? If neither are working, then it's either a port forwarding issue, or the server simply isn't set up correctly. RE: NAT loopback (hairpinning): This allows you to access your server via external IP which is important for server clustering. Without it, you won't be able to transfer your character between the servers you're hosting (players outside of your home network will not have this problem since they're already using external IP). A recent update seems to have broken this though. If anyone else has a solution to this issue, please reply. I was hoping latest patch that re-enabled "multihome" would resolve it but no luck here. I'm still only able to connect using the internal IP. I'm experiencing the same thing, no matter what I do I can only access my Linux dedicated servers using the internal IP, but the external IP doesn't work (other than the query port, so it's visible but nobody can connect to it). Link to comment Share on other sites More sharing options...
R0cktf Posted June 17, 2020 Share Posted June 17, 2020 In my case I have the same problem, but it only happened after yesterday's att, at 311,100. My server was working perfectly, but now it appears but always from the expired connection, I tried to put the other ports 7779/7778, 27016/27014, but nothing happened Link to comment Share on other sites More sharing options...
Larkfields Posted June 17, 2020 Share Posted June 17, 2020 When you specify port=7777 Ark will also use the next port up. So in this case you have to port-forward 7777 and 7778 as well as the query port number. Link to comment Share on other sites More sharing options...
thejduman Posted June 17, 2020 Author Share Posted June 17, 2020 2 hours ago, Larkfields said: When you specify port=7777 Ark will also use the next port up. So in this case you have to port-forward 7777 and 7778 as well as the query port number. I added these ports and it fixed the problem! Thank you! Link to comment Share on other sites More sharing options...
GyozaGuy Posted June 17, 2020 Share Posted June 17, 2020 I have those ports opened and can connect on the local network, but the public IP doesn't let anybody connect. Link to comment Share on other sites More sharing options...
GyozaGuy Posted June 18, 2020 Share Posted June 18, 2020 I finally got mine working on Linux by opening ports 7776, 7777, 7778, 27014, 27015, and 27016, and adding the `-UseVivox` option to the command line. Probably overkill, but just opening the extra game port wasn't working. Somehow this does. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.