Why the FG Cloud broker drops your campaign handshake and what actually keeps your players in the session
Ready to bypass ISP packet inspection and keep your Fantasy Grounds Unity lobby connected all night?
You spend three days building encounters, setting up line of sight on a massive dungeon map, and tailoring combat stats for tonight's session. Your players hop onto voice chat, grab their dice, and wait for your signal. You select Cloud mode, click Start Server, and wait for the lobby name to publish.
Instead of the green confirmation indicator, the console log stalls out and throws that dreaded red line: "Cloud matchmaking registration failed" or "Could not connect to the cloud server."
You cancel out, restart the Fantasy Grounds Unity client, and try again. Sometimes the lobby finally shows up after three retries, only for two of your players to get stuck on "Acquiring file list" before dropping completely ten minutes into combat. The rest of the table sits there waiting while you scramble through router settings and forum threads trying to figure out why your campaign cannot stay registered with the master broker.
Most GMs immediately assume Fantasy Grounds' master servers are completely down, or that their own local campaign database is somehow corrupted. You back up the campaign folder, verify the Steam install, and reboot your home router.
Yet when you check community status channels, other GMs are running games without a hiccup.
The root issue is almost always how your local internet provider handles persistent UDP handshakes and asymmetric NAT routing.
Unlike the classic version of Fantasy Grounds—which required manual port forwarding on TCP port 1802—Fantasy Grounds Unity introduced a Cloud Matchmaking Broker system. This was supposed to make hosting effortless. In theory, both the GM and the players establish a simultaneous outbound UDP connection to the FG Cloud relay server, allowing traffic to traverse local firewalls without manually opening ports.
The catch is how modern residential internet service providers treat this traffic.
Many consumer ISPs, apartment complexes with shared bulk fiber, and regional broadband carriers put residential lines behind Carrier-Grade NAT (CGNAT) or enforce strict symmetric NAT translation. When your FGU client establishes a registration socket with the lobby broker, a symmetric NAT router constantly rewrites external port assignments for each outgoing packet. Even worse, many ISP edge filters flag continuous, persistent UDP relay traffic that does not look like standard web traffic, classifying it as unauthorized peer-to-peer sharing and silently dropping return keep-alive packets.
The moment the FG Cloud broker misses a couple of successive keep-alive replies, it assumes your host session has died. The broker delists your table from the public matchmaking registry, and any active players relying on the relay suddenly encounter desyncs, broken asset downloads, or outright socket disconnects mid-turn.
When GMs hit this barrier, the initial impulse is often to grab whatever free VPN or cheap public proxy they can find.
That almost always makes game night worse.
Most generic consumer VPNs are designed for downloading files or streaming video, not maintaining bidirectional, low-latency gaming sockets. Free and overcrowded commercial VPNs often restrict custom UDP traversal entirely, or they route traffic through overloaded exit nodes suffering from severe packet jitter. If you host a tabletop session through an unstable VPN node, your players might join the lobby, but downloading combat maps will take fifteen minutes, dice rolls will lag behind voice chat, and the connection will randomly reset every time your VPN client switches internal routes.
What you actually need to host Fantasy Grounds Unity reliably is straightforward: an unthrottled, clean network tunnel that provides an open, stable NAT configuration, eliminates upstream ISP packet inspection, and maintains consistent UDP packet pacing so the FG Cloud broker never drops your campaign session.
This is where ONLYDOGSVPN fits into a GM's prep routine.
ONLYDOGSVPN routes your game traffic through clean, gaming-optimized network backbones that fully support transparent UDP data streams. Instead of allowing your residential ISP's restrictive NAT table or packet filters to drop broker handshakes, your entire host connection tunnels securely through an established, stable gateway. The Fantasy Grounds Unity client registers with the cloud broker on the first click, and your campaign stays published and reachable for the entire duration of the game.
Equally important for running a virtual tabletop is low packet jitter. When you reveal a large battlemap with high-resolution graphics and dynamic lighting masks, your machine must push chunks of asset data to multiple players simultaneously without stalling. ONLYDOGSVPN maintains unmetered, low-overhead transit lines that prevent the buffer bloat and packet drops that typically cause players to freeze on loading screens.
Before jumping in, let us be clear about what a VPN will not fix.
A VPN resolves carrier-grade NAT blocks, aggressive ISP firewall filtering, and dropped broker keep-alive handshakes. It cannot fix a campaign if the central SmiteWorks master server infrastructure is undergoing an official maintenance window or experiencing a legitimate global outage. If the cloud servers are physically down for everyone, no routing adjustment can force them back online.
Similarly, a VPN cannot fix local hardware bottlenecks. If you are trying to share a single uncompressed 200MB image file with five players simultaneously over an old laptop running on weak Wi-Fi, the client will struggle regardless of your network route. Optimizing your asset sizes and hardwiring your GM rig into Ethernet remains good table management.
Your weekend session should be spent running exciting roleplay and tactical combat, not apologizing to a group of friends while staring at a broken server lobby. If your home connection keeps dropping Fantasy Grounds cloud registration, shifting to a clean, UDP-friendly connection clears the routing bottleneck so your table can get straight to rolling dice.