PDA

View Full Version : License conflict when connecting to previous game



jaharmi
February 16th, 2022, 12:48
Last Friday night, I had a lot of difficulty connecting a second Fantasy Grounds instance (running on my Mac with “open -n /Applications/SmiteWorks/Fantasy\ Grounds/FantasyGrounds.app”) to the DM instance running on the same computer. I kept getting a license conflict during multiple attempts to connect. It had worked for several weeks in a row.

I tested again on Sunday and was able finally able connect when I searched for my GM name, rather than using the previous connection listed in the Join screen. The previous connection had my name with a red dot next to it, which is normal.

Could this be something about the previous connection info? Or was there another problem, perhaps not related to my system, that interfered?

I’m running on macOS Big Sur v11.6.3. From the computer’s current uptime, I had rebooted in between the last time the connection worked and Friday when it failed. This reboot probably involved updating to macOS 11.6.3 from v11.6.2. The IP address of the computer should not have changed in between, as I have a DHCP reservation from my router. I don’t see that there was an IP address change at my ISP or router level, either. I do generally check for and install updates for FGU each week.

Thanks!

Moon Wizard
February 16th, 2022, 21:04
To avoid the license conflict, the IPv4 and IPv6 internal and external addresses must match exactly between both the GM and the player instance.

I'm not sure why you would get different IP addresses assigned to the two instances; but I am no Mac expert.

You can try running the session as a LAN session; and connecting via "localhost". Otherwise, you'll have to figure out why the Mac is assigning different IP addresses to each app instance.

Regards,
JPG

damned
February 16th, 2022, 21:23
If my host session has been running for a long time... I dont know if long is hours or days (I pretty much always have FG running) I will get a license conflict when I try to connect. Restarting all instances fixes that for me.