You can start an HTTP tunnel to localhost and selfhost any app by using this command:
ssh -p 443 -R0:localhost:8000 a.pinggy.io
(Change port `8000` to your port)
I am looking for feedbacks and suggestions to help me in deciding the future roadmap of the product.
Features - It supports almost all features of ngrok such as:
* TCP / TLS tunnels
* Inspecting HTTP requests through the web debugger
* Basic auth (Bearer token auth coming soon)
* Live header modifications
* Custom domain
We have tried to make the terminal self sufficient by including a basic HTTP traffic inspection tool. The terminal also shows a QR code to make it easy to quickly check a webpage on your phone.
Infrastructure - Currently the servers are located in 3 regions (US, Europe, and Asia). When you connect you are routed to the nearest region. The servers are hosted in AWS.
We plan to expand to more regions soon for faster connectivity. The tunnel link speeds are restricted to 8Mbps for the free tier (unregistered users).
Here are some of the improvements in our pipeline:
1. Bearer token auth
2. IP whitelisting
3. Team plan to share account with other users.
4. Wildcard custom domains
5. OAuth 2.0 authentication for tunnel visitors.
6. Hosting in cheaper infrastructure to allow more tunnel link speed. 7. Open sourcing the core.
Which feature / improvement do you want think is more useful? We are keenly looking for suggestions.
- Custom domain
I would say these two are absolute must haves and I wouldn't use ngrok if they didn't have it. The use case is: I want to test OAuth / 3rd party integrations that require HTTPS and webhooks.
One feature I would love to have is to assign fixed subdomain to each team member effortlessly so they wouldn't need to update 3rd party configurations when they start developing (you can do this with ngrok but it takes time to set it up for each team member). Not sure how exactly this should be solved.