Getting license key conflict error

[darrenan]

I'm trying to connect a second instance of FG to the first instance running in LAN mode, and it's giving me the license key conflict error which I've never seen before in this scenario. Are we no longer allowed to test client side interactions this way? Did something change?

[Zacchaeus]

No, you can still connect two instances on the same computer. Start the first instance in Cloud mode then right click on the FG icon on the task bar and select Fantast Grounds. Click join and try your username into join by dm name. If you start thr first instance as LAN the type localhost into join by IP address. More details here https://fantasygroundsunity.atlassia...+Grounds+Unity

[Zacchaeus]

Just in case you are using two computers then make sure that the second instance has no license key. In other words go to settings and remove the license key and update the client so that it reverts to the demo version. (You can’t have two clients with the same license running at the same time).

[darrenan]

No, you can still connect two instances on the same computer. Start the first instance in Cloud mode then right click on the FG icon on the task bar and select Fantast Grounds. Click join and try your username into join by dm name. If you start thr first instance as LAN the type localhost into join by IP address. More details here https://fantasygroundsunity.atlassia...+Grounds+Unity

Yeah I was trying the latter, running the host in LAN mode on port 1802, and then connecting using 'localhost' and 1802, which has always worked for me in the past. But today, it's giving me a license key conflict error.

I assumed that cloud mode would not work, as the second instance would send the license key thus guaranteeing a license key conflict.

[darrenan]

I shut down both instances and tried again, and now it's working. No clue what was going on there.

[Vass_Dts]

I shut down both instances and tried again, and now it's working. No clue what was going on there.

Yes, this sometimes happens to me as well (and I'm using a single computer). Restarting FG always resolves this. I think it either has something to do with how long the app was open (I sometimes keep it on for days while my computer just goes to sleep) or if at any point I had recently launched a cloud campaign. It's not consistent enough to be able to tell for sure what's going on, and because it always gets fixed with an app restart, I don't find it important enough to experiment in order to hunt down the exact trigger. It's just a minor inconvenience.