-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
No. Your app keeps running locally. GhostlyShare creates a public tunnel to that local app.
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.
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.
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.
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.
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.
Only while ghs share is running. The CLI is not a background daemon and does not
have separate ghs stop or ghs list commands. Press Ctrl+C to stop sharing and
clean up.
You can also add --expires-after, for example ghs share 5173 --expires-after 15m, to stop sharing automatically after the selected lifetime.
Yes. Use Link Lifetime in the desktop app, or use --expires-after in the CLI.
The allowed range is 1 minute to 40 days, 23 hours, and 59 minutes. today keeps
the link online until the end of the current local day.
GhostlyShare can also stop a live public link automatically if the public URL is no longer reachable. This can happen after sleep, network changes, VPN changes, or tunnel connectivity problems. Start sharing again after checking your local app and network.
Requests count public HTTP requests, not page visits. One browser visit can load HTML, scripts, styles, images, API calls, icons, and framework connections.
For regular web pages and APIs, Active is based on recent public activity. If no new request arrives for about one minute, the visitor is no longer shown as active. WebSockets, server-sent events, and streaming responses stay active while the connection is open.
The default successful visitor password session is 30 minutes. The desktop app lets
you choose 5 minutes, 15 minutes, 30 minutes, 1 hour, 4 hours, or 24 hours. The CLI
can set 5 to 1440 minutes with --password-session-minutes.
Random trycloudflare.com links use Cloudflare quick tunnels. If Cloudflare rejects
new quick tunnels because too many were created recently, GhostlyShare waits locally
before trying again. See Rate Limits and Sessions.
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.
Ubuntu GNOME on X11 and Wayland are the primary tested Linux environments. Other desktop environments may work, but tray and focus behavior can differ.
No. GhostlyShare is for local development sharing, demos, reviews, and temporary public access.
Use the public bug report form:
Anyone with a GitHub account can open an issue. Please remove Cloudflare API tokens, passwords, private URLs, and other secrets before posting.
Use the public feature request form:
Feature requests should describe the user problem and expected behavior.
- Home
- Installation
- Getting Started
- Command Line Interface
- Security and Privacy
- App Detection
- App Merging
- Going Public
- Traffic Statistics
- Link Lifetime
- Password Protection
- Rate Limits and Sessions
- Custom Domains
- Cleanup and Uninstall
- Known Limitations
- Windows and Linux
- Troubleshooting
- Report Bugs / Request Features
- Testing Checklist
- FAQ