FAQ

FAQ

Does GhostlyShare deploy my app?

No. Your app keeps running locally. GhostlyShare creates a public tunnel to that local app.

Why is my app visible in the browser but not in GhostlyShare?

GhostlyShare does not show every reachable port. It needs enough evidence that the port is a local development app and not a system or infrastructure service.

Add a meaningful <title>, use a common development runtime, or expose a clear API or framework response.

Why are two ports shown as one app?

They probably look like the same app. GhostlyShare merges ports with the same stable app fingerprint, and it often prefers HTTPS over HTTP.

See App Merging.

Why does Go Public show a URL before the link works everywhere?

Cloudflare can report the tunnel URL before every edge route, DNS answer, browser, or local app request is fully ready. Usually this is a short delay. Custom domains can take longer because DNS is involved.

See Going Public.

Does closing GhostlyShare stop Cloudflare?

On normal close, yes. GhostlyShare stops the Cloudflare tunnel processes it started.

If the app is force-killed or the machine shuts down abruptly, cleanup may not run.

Does stopping my local app stop the tunnel process?

Not always immediately. GhostlyShare may keep tunnel processes warm while it is running, but forwarding for the missing app is disabled once the app is detected as gone.

Is Windows or Linux better supported?

The main sharing flow is supported on both Windows and Ubuntu/Debian Linux.

Windows has Microsoft Store integration and DPAPI token storage. Linux has .deb packaging, Secret Service token storage, and desktop behavior that can vary between GNOME, KDE, X11, and Wayland.

What Linux desktops are expected to work?

Ubuntu GNOME on X11 and Wayland are the primary tested Linux environments. Other desktop environments may work, but tray and focus behavior can differ.

Can I use GhostlyShare for production hosting?

No. GhostlyShare is for local development sharing, demos, reviews, and temporary public access.