← glasshosting.com | Game Hosting | Managed Services | Status | Discord

Router and CGNAT Issues Explained Simply for Game Hosts Print

  • 0

Router and CGNAT Issues Explained Simply for Game Hosts

What CGNAT is

Carrier-grade NAT means many homes share public IPv4. Inbound port forwards never reach your PC because you do not have a unique public address to forward.

How to spot it

  • Router WAN IP is a private-looking range
  • ISP says they do not offer inbound ports on your plan
  • Port forward check tools always fail

Simple fix path

Rather than fighting the ISP for a business IP, host the game on GlassHosting and play as a client like everyone else. Keep your home network for playing—not serving.

Measure before you guess

Open the resource graphs on panel.glasshosting.com during a normal play window and during a busy one. Write down approximate CPU and memory percentages alongside how the game felt. That habit turns vague “it lags” reports into actionable upgrades or config tweaks.

If graphs look calm while players stutter, ask whether the issue is client FPS, wifi, or a single loaded farm chunk. If graphs are pegged, stop adding content packs until you either tune view distance/entities or upgrade the GlassHosting plan from the client area.

When to involve GlassHosting support

Open a ticket from billing.glasshosting.com when the platform itself looks wrong: panel cannot start the process, allocations seem missing, or multiple unrelated networks cannot reach the service. Include service name, timestamps, and console excerpts without secrets.

For game-logic questions (plugin conflicts, datapack design), include what you already tried. Skim related knowledgebase articles first—many “outages” are EULA flags, edition mismatches, or whitelist misses.

Why leaving a home PC behind helps

Residential uploads, CGNAT, dynamic addressing, Wi‑Fi interference, and sleep schedules fight always-on multiplayer. Moving the authoritative server to GlassHosting lets everyone—including the former host—play as clients on equal footing.

Bring your world via SFTP, match versions carefully, run a two-player test, then announce the new address. Keep the old PC as a backup archive for a week, not as the live source of truth.

Networking notes for real humans

Friends should connect using the exact address shown in the GlassHosting panel. If one friend fails, have them try a phone hotspot to rule out school/work UDP or TCP filters. Home CGNAT and router forwards are irrelevant for a datacenter-hosted server—you should not be opening ports on your living-room gateway for a GlassHosting world.

Do not publish SFTP credentials, API keys, or admin passwords next to the game IP. Share join info in private channels, and update pinned messages when endpoints change.

Quality bar

Definition of done for any change: server starts clean, two players join, critical plugins load, and a fresh backup exists. If any checkbox fails, roll back before opening the gates wider.

Practical scenario

Imagine ten friends joining after work while two explore brand-new chunks and someone tests a new plugin. That moment is when undersized plans, missing backups, or unclear admin ownership show up. Rehearse your GlassHosting checklist on a quiet afternoon so peak hours stay fun.

Related links: panel.glasshosting.com · billing.glasshosting.com · glasshosting.com.


Was this answer helpful?

« Back