Ngrok is a multiplatform tunneling, reverse proxy software that establishes secure tunnels from a public end point such as internet to a locally running service capturing all the traffic for detailed inspection and replay.
Before using ngrok, when we needed to expose a localhost application to web (internet) all we were doing is deploying the application in a server running a DMZ or we used to relocate the host to DMZ and configure NATing in the firewall. We also used to make DNS configuration in External DNS where the domain is hosted. In general, DMZ (De-Militarized Zone) is a computer host or small network inserted as a “neutral zone” between a company’s private network and the outside public network. It prevents outside users from getting direct access to a server that has company data. The following are the issues that we were facing before Ngrok deployment:
Unable to expose localhost application directly to internet without DMZ & other network configuration
Unable to demonstrate an application to Client on urgent basis
Unable to share websites for testing purpose
Develop any services which consume Webhooks (HTTP CallBacks)
Can’t share a website temporarily that is running only on our developer machine
Time Consuming on network and DNS configurations
Can’t debug or inspect HTTP Traffic in a precise manner
Can’t run networked services on machines that are firewalled off from the internet
Unable to expose application behind http proxy
Unable to forward non-http and non-local network services
references:
https://vmokshagroup.com/blog/expose-your-localhost-to-web-in-50-seconds-using-ngrok/
Before using ngrok, when we needed to expose a localhost application to web (internet) all we were doing is deploying the application in a server running a DMZ or we used to relocate the host to DMZ and configure NATing in the firewall. We also used to make DNS configuration in External DNS where the domain is hosted. In general, DMZ (De-Militarized Zone) is a computer host or small network inserted as a “neutral zone” between a company’s private network and the outside public network. It prevents outside users from getting direct access to a server that has company data. The following are the issues that we were facing before Ngrok deployment:
Unable to expose localhost application directly to internet without DMZ & other network configuration
Unable to demonstrate an application to Client on urgent basis
Unable to share websites for testing purpose
Develop any services which consume Webhooks (HTTP CallBacks)
Can’t share a website temporarily that is running only on our developer machine
Time Consuming on network and DNS configurations
Can’t debug or inspect HTTP Traffic in a precise manner
Can’t run networked services on machines that are firewalled off from the internet
Unable to expose application behind http proxy
Unable to forward non-http and non-local network services
references:
https://vmokshagroup.com/blog/expose-your-localhost-to-web-in-50-seconds-using-ngrok/
No comments:
Post a Comment