Cyber

On 2/4/2019 at 2:58 AM, dtmaster said:

you have set on two grids 57561

Oh.. my bad... I've just wrote wrong. I mean 57561, 57565, 57571, 57575. 

There is no conflicting port. 

Let me enum all the steps that I'm understanding to be necessary: 

1. ServerGrid.json: port, gamePort and seamlessDataPort must be setted as unique ports with at least two "spaces number" 
 for gamePort and four for seamlessDataPort, to each grid server. IP I was point to ddns.net hostname that points to my public server IP. 

2. ServerGrid.json and Lauch Scripts (.bat) must match the same gridX and gridY ((0,0) (0,1) and so on), query port (e.g. 55561), gamePort (e.g. 5561) and SeamlessIP to public IP (using dns here again)

3. One process (.bat) for each grid/server;

4. Firewall inbound rules free those ports (I've been disabled the firewall and have tested adding those ports too except RCON ports)

5. In DefaultGameUserSettings.ini: was configured as SeamlessDataSocketPort=27000,27005,27010,27015

Please.. What am I missing?

Notice that there aren't any red wall at grid boundaries, so we know that instances are having the "conversation" properly. It seems that only clients can't migrate the connection to next grid. 

Hello folks,

I've been having that same problem in a 2x2 private server.

I've also set all ports like 57561/5761/27000, 57565/5765/27005, 57561/5771/27010 and 57575/5775/27015, added in the firewall inbound rules, (later have tried to turn firewall offl), my ServerGrid.json is matching  with these settings and startup .bat's files too. Unfortunatly I've still been stuck in travelling grid.

I don't know what else can I do. Can anybody please lead me a tip?

Thanks