Players cannot connect

Check the panel first

Observed power must read running. A desired state of running is not enough: the node reports observed power after the guest actually starts. If the two disagree for more than a short job, the start has not completed.

Then copy the join address from the overview or Ports. That string is the host IP, the port, and the protocol. Give players that exact string, not a hostname you invented and not the guest container port.

1. Confirm observed power is running.
2. Copy address from the instance overview or Ports.
3. Check that the player is using the same protocol and port.
4. Check that the client version matches the pack version.
5. Read Console for a bind error, a whitelist rejection, or a crash.

Ports and remaps

Several customers share one IPv4. When a pack port is configurable, the host port may differ from the guest port. Players must use the host IP:port shown in the panel. When bind is fixed, the two ports match. Ports lists both next to each other so a remap is visible.

If Ports shows UnavailablePanel, inventory has not assigned an allocation. That is not a client-side problem and no firewall rule on your side will create a port.

Names and DNS

Foxcore does not publish DNS for your instance. A name only works if you own the zone and point an A record at the allocation IP. The port is still required for almost every game. Minecraft Java can hide it with an SRV record; Bedrock and most other titles cannot.

The panel hostname is HTTP on Cloudflare and is not a proxy for game UDP or the game TCP port. A name that only exists in a chat message is not a join host.

When to open a ticket

Open Support with the instance id, the join host, observed power, the player’s client version, and what you already tried. If Console shows a bind failure or the node never reports, staff can match the id to jobs and nodes. They cannot debug a player’s local client from the panel.