Captain Contagious

Your last update broke something, pings are ridiculous in some grids and it seems to have something to do with anchored ships near tames and bases. It would be bloody nice if you addressed it and fixed it instead of all of this fluff.

@chriswkf - In windows 10 you need to open windows defender firewall with advanced security, go to inbound rules and create 2 new rules, one for ATLAS TCP and one for ATLAS UDP. You enter your ports where you see the 0's using either single port (5765, 5768, etc) or a range (12345-12350 just an example). Enter the ports that you have in your bat file. Hope this helps!

@koosh22 - did you fix your issue? I resolved mine and am happy to share the solution to see if it will help you if you still need it?

@chriswkf - the ports need to be open on TCP and UDP in both the windows firewall (assuming you are using windows) and in your router settings as well. As far as your second question goes, the first will solve it. If your ports aren't forwarded properly you will not be able to see your server in the list.

Have you installed a loopback adapter and set it to your external IP address? Try 127.0.0.1 as your homeserver IP address and your external ip as the other grids address. It should resolve once you have the adapter installed. I am able to play on my own server hosted on my machine using this method

@Jordiii - Not sure about that one mate, you might like to try logging on to the discord and seeing if someone with more knowledge could help you troubleshoot it. Sorry I couldn't help you

Have you tried setting your home server IP to the same as the redis server? In my case, my home server needed to be on 127.0.0.1 and my second grid was 192.168.0.11. I was able to relog into the second grid without issues once that was changed. Hope that helps!

@Nelson Sandalwood did you get this sorted? I managed to stumble upon a solution to mine and seeing as how ours were quite similar I thought it might work for you also

Bump. Really need a hand if someone is willing, I am still having the same issue with the database not being populated.

No mate, just a continual query error every single time =/ I can get back in using join new server, however, I am dead and back in the middle of the home server map while my raft is on the border.

I am having almost the exact same problem except unable to join back even using the steam favourites.

I managed to solve my issue of not being able to relogin with some help from JetFox on the discord channel. For anyone else that gets disconnected once they have travelled from their home server to another grid and can no longer log back into their server the following helped me. Set your homeserver IP to the same IP address that your redis server is connecting to. In my case that was 127.0.0.1. Change that in the json file as well as under seamlessip in the bat file. My second grid is running off 192.168.0.11 and I can log in without issue now. I am still having an issue with the redis DB not being populated properly though. I have no playerinfo DB. I am unsure how this will impact me at at later stage. This is how it looks:

So after playing around with rates etc I have discovered an issue with my second grid server and I am not sure what the issue could be. I can log in and out when I am located in the home server and use the rejoin or join new to get back in. When I enter the second grid and log out I am unable to reconnect at all using rejoin or join new. I get a Network Failure Message: Unable to query server info for invite. Both servers are still running in the steam favourites and I can still see my server listed in the Atlas server list. Any ideas..please, please?

Please delete this topic mods, upon further testing I realise the problem is much bigger and it is actually an issue with relogging into the second server after you log out.

Does fish oil work in this instance?