Skip to content

Known Limitations

Ghostly edited this page Jun 8, 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. If the public URL becomes unreachable, GhostlyShare may stop sharing automatically and return the app to Local Only.

Optional link lifetimes can be set up to 40 days, 23 hours, and 59 minutes. Longer automatic lifetimes are not currently accepted.

Network Conditions

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

Sleep, network changes, VPN changes, or interrupted connectivity can also break an existing public link. If that happens, check the local app and start sharing again.

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

Random links usually create a new public URL each time sharing starts. Custom mode reuses the configured hostname, but DNS and Cloudflare readiness can still take a moment after a new start.

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.

Low-confidence ports and generic HTTP endpoints can also be hidden when GhostlyShare does not have enough evidence that they are user-facing development apps.

Platform Differences

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

Linux tray, focus, keyring, startup behavior, and tray window positioning can also vary by desktop environment. Tray window behavior has been tested with Arch Linux KDE Plasma on Wayland, Kali Linux XFCE on X11, and Ubuntu GNOME on Wayland. Other Linux desktops and sessions may work too, but they are not explicitly tested.

Clone this wiki locally