Skip to content

Known Limitations

Nix edited this page May 25, 2026 · 6 revisions

Known Limitations

GhostlyShare is designed for temporary sharing of local development apps. It is not production hosting.

Sharing Requirements

  • The selected local app must keep running.
  • GhostlyShare must keep running.
  • Your computer must stay online.
  • The local app must still answer locally while the public link is active.

If the local app restarts or stops, the public link can show an offline response.

Network Conditions

VPNs, firewalls, proxies, DNS settings, corporate networks, and browser caches can affect public links.

Cloudflare Quick Tunnel readiness can take a moment. Custom domains can take longer because DNS and Cloudflare routing need time to settle.

Rate Limits and Active Tunnels

GhostlyShare allows up to 3 public apps at the same time. If 3 apps are already active, stop one before sharing another.

Random trycloudflare.com links can also be paused locally if Cloudflare reports quick-tunnel rate limiting. GhostlyShare uses cooldowns of 1 hour, then 3 hours, then up to 6 hours for later consecutive rate limits. A successful tunnel start clears the saved cooldown.

See Rate Limits and Sessions for the exact session and cooldown behavior.

Security Limits

Password protection protects the public GhostlyShare link, but users should still avoid exposing sensitive, private, internal, admin, database, or infrastructure services.

Some system and infrastructure ports are intentionally hidden to reduce the risk of accidental exposure.

Platform Differences

Linux app detection can differ from Windows because process metadata, desktop integration, permissions, and service detection work differently.

Linux tray, focus, keyring, and startup behavior can also vary by desktop environment.

Clone this wiki locally