Earlier quoted context omitted.
It's absolutely possible. Admittedly I'm still running 2.1.18, but I just tested it there and it still works. https://ngrok.com/docs#subdomain edit: Just in case, I updated to 2.2.4 (newest) and it's still possible to use custom subdomains.
This doesn't work. I just checked. Tunnel session failed: Only paid plans may bind custom subdomains. Failed to bind the custom subdomain 'blahblahblah' for the account xxx
Ngrok: Secure tunnels to localhost
161–170 of 195 posts
Re: Ngrok: Secure tunnels to localhost
#162Re: Ngrok: Secure tunnels to localhost
#163Earlier quoted context omitted.
Surely ngrok doesn't access repo directory and only acts as port forwarding tool. Haven't used it to be sure though, but that's what i'm getting from it.
This is correct. You still need to have a service listening on the port you have mapped ngrok to. So simply using ngrok is not a security risk.
your laptop is a very different environment from production: there are probably different protections, firewalls, monitoring, etc in place. additionally, while your laptop (hopefully) doesn't have direct access to production databases, you probably have stuff lying around that you wouldn't want an attacker to get their hands on: sensitive work documents, your Chrome cookies just sitting in a sqlite database somewhere, source code for all the repositories you have checked out locally (not just the one app that has the exploit).
I don't agree that "using ngrok is not a security risk".
Re: Ngrok: Secure tunnels to localhost
#164Earlier quoted context omitted.
Happy paying customer :-) Can you speak to security? I love using ngrok to test stuff in dev that requires SSL without having to setup up SSL. Of course that means it's running through your cert. Obviously one shouldn't run anything protected through your system, but what is your visibility into that traffic?
Why not just setup SSL in your development environment? It's seriously not that difficult at all, there's zero reason to use Ngrok (although I'm sure it does what it does very well), plus asking this question after you're already paying is kind of silly.
That assumes this is my only use case for using ngrok :-)
Re: Ngrok: Secure tunnels to localhost
#165Earlier quoted context omitted.
You're both right. If the dev team needs something like ngrok, the security team has failed to provide proper tools. If the dev team goes ahead and uses ngrok without consulting the security team, the dev team has likely committed an awful security breach. The dev team and the security team need to think of each other as being on the same team, and talk to each every day about what they want and need.
Pretty sure a lot of people using this don't even have a "security team." They likely have corporate IT that takes 2 weeks to add a DNS entry. Something complex like mapping a public IP to a dev server would take an act of $DEITY.
just don't use your company's name in the domain name, make it something obscure.
Re: Ngrok: Secure tunnels to localhost
#166Earlier quoted context omitted.
Did the free option go away? (On my phone now so I can't try it out.)
Below the paid options: Free Plan For quick demos and other simple tunneling needs. * HTTP/TCP tunnels on random URLs/ports * 1 online ngrok process * 4 tunnels per ngrok process * 40 connections / minute
Re: Ngrok: Secure tunnels to localhost
#167Earlier quoted context omitted.
> ngrok can not possibly be easier than port forwarding. Oh come on, of course it can. I use port forwarding myself, but ngrok literally makes testing remote webhooks as simple as running "ngrok". That's it. It's definitely what I recommend coworkers who just want a quick solution to test out 3rd party service integrations.
Um, just signing up for ngrok - 10 times more effort than port forwarding. Then you have to learn how to ngrok. And thats that's before actually figuring out what ngrok really is, how sensible it is to route data through a third party etc. etc. etc. For people without public IPs - why not just learn how to setup an SSH tunnel instead? Similar effort , save it as a script. Boom, you actually learned something useful t…
So it's not similar effort, especially given that I use it on my corporate network where doing port forwarding more assuredly would be difficult and problematic.
Re: Ngrok: Secure tunnels to localhost
#168Earlier quoted context omitted.
How does this compare to https://localtunnel.github.io/www/ ?
I stopped used ngrok because after opening the tunneled URL a few times it started saying "too many HTTP requests" on a Wordpress project. It is common for those to have many images/scripts/styles so throttling by number of requests makes ngrok unusable, now a happy localtunnel user.
Re: Ngrok: Secure tunnels to localhost
#169Earlier quoted context omitted.
How does this compare to https://localtunnel.github.io/www/ ?
I stopped used ngrok because after opening the tunneled URL a few times it started saying "too many HTTP requests" on a Wordpress project. It is common for those to have many images/scripts/styles so throttling by number of requests makes ngrok unusable, now a happy localtunnel user.
Re: Ngrok: Secure tunnels to localhost
#170Ngrok is one of the most valuable development tools in my toolbox.