Frequently Asked Questions

wsgrok is a secure HTTP tunneling service that allows you to expose your local development server to the internet. It's perfect for testing webhooks, sharing your work with clients, or accessing your local environment from anywhere.

wsgrok establishes a secure connection between your local machine and the servers in your selected region.

1. You run the wsgrok client on your machine, pointing it to your local port (e.g., localhost:3000)
2. The client establishes a secure connection to our servers
3. We assign you a public URL (e.g., myapp.wsgrok.com)
4. When someone visits that URL, we forward the request through the tunnel to your local server
5. Your local server processes the request and sends the response back through the tunnel

Ngrok is designed for enterprises and organizations. It’s well known but somewhat pricey, and many features require an additional fee. For example, region pinning is free in wsgrok , while Ngrok charges $300 per month for the same feature.wsgrok, on the other hand, is built specifically for individual developers. It is lightweight, affordable, and designed to give you the same power without the enterprise price tag.

1. Sign up for a free account at https://wsgrok.com
2. Download the wsgrok client for your platform (Windows, macOS, or Linux)
3. Get your authentication token from the Console
4. Run: wsgrok -subdomain myapp -port 3000
5. Access your local server at myapp.region.wsgrok.com

It’s free while our cloud credits last. We may introduce a paid tier in the future to help keep the service running.

Yes! You can choose your own subdomain (e.g., myapp.region.wsgrok.com) and it will be reserved for your account. Your subdomain persists across sessions, so you can share the same URL with teammates or clients without it changing.

wsgrok offers multiple authentication options:

• No authentication: Public access (default setting, though not recommended)
• Basic Auth: Username and password protection
• API Key: Custom header-based authentication
• IP Allowlist: Restrict access to specific IP addresses

You can configure these settings in the Console for each tunnel individually.

We currently support multiple regions for optimal performance:

• 🇺🇸 US West (Portland, OR)
• 🇺🇸 US Central (Omaha, NE)
• 🇺🇸 US East (Atlanta, GA)
• 🇺🇸 US South (Dallas, TX)

Your tunnel is routed to the pinned region to suit your needs. If a request comes from a different region, we redirect to the appropriate server.

wsgrok comprehensive analytics through the following dashboards:

• HTTP Inspect: Real-time request/response inspection with headers and body
• Request Logs: Geographic visualization of traffic with world map, filtering by route, IP, and location
• Usage: Bandwidth tracking (egress/ingress), request counts, and month-over-month comparisons

All data is stored in the database with a 120-day retention period, providing you with powerful analytical capabilities.

Ngrok offers 5 GB, while we provide 20 GB (10 GB ingress and 10 GB egress). This should be more than enough for most use cases.

Currently, wsgrok supports only HTTPS traffic. Please share your use case, and we will do our best to accommodate it.

We retain your request logs and usage data for 120 days. This gives you ample time to analyze traffic patterns, debug issues, and track historical usage. Request/response bodies shown in HTTP Inspect are cached for 1 hour for performance reasons, then automatically deleted. Tunnel configurations and account settings are retained indefinitely while your account is active.

If you're having connection issues, try these steps:

1. Verify your authentication token is correct (copy from Console → Settings)
2. Check that your local server is running (e.g., visit localhost:3000 in your browser)
3. Ensure the subdomain isn't already taken
4. Check your firewall
5. Try a different region with the --region flag
6. Check the client logs for specific error messages

Still having issues? Contact support with your client logs and we'll help troubleshoot.

Several factors can affect tunnel performance:

• Distance: Try connecting to the closest region
• Local server: Ensure your local server is responding quickly
• Bandwidth: Large files or responses will take time to transfer
• Compression: Enable gzip compression on your local server
• Network: Check your internet connection and firewall settings

Pro tip: Use our HTTP Inspect tool to see actual response times and identify bottlenecks.

Security is our top priority. All connections are protected with TLS/SSL encryption, and we never share your data.

For more details, see our Security Policy at /legal/security

We're here to help:

• Email: Loading... (24-48 hour response time)
• Documentation: Visit /docs for comprehensive guides
• GitHub: Report bugs or request features on our GitHub repository

When contacting support, please include your client logs and a description of the issue for faster resolution.