visitishan/ngrok_unlimited

Use ngrok for more than the 8 hours limit

ngrok_unlimited

If you want to make a personal server or self host a website, but your ISP is on a CG-NAT then the DDNS tools won't help. Since the IP assigned to the ISP is from a shared IP, there's nothing much you can do. After several hours of Googling, I found that there are some reverse tunneling tools which can help in this case. One such tool is "NGROK".

What is NGROK?

Ngrok is a multiplatform tunnelling, reverse proxy software that establishes secure tunnels from a public endpoint such as internet to a locally running network service while capturing all traffic for detailed inspection and replay. Enter ngrok, a very cool, lightweight tool that creates a secure tunnel on your local machine along with a public URL you can use for browsing your local site. When ngrok is running, it listens on the same port that you're local web server is running on and proxies external requests to your local machine.

However, there are few limitations in NGROK as well. The biggest one is that its not completely free. And if you're using the free version of NGROK, the tunnel link expires after every 8 hours, and you'll have to restart the NGROK service again manually, and again the tunnel link will change. So to avoid this, we merged the Dynamic_DNS tool and NGROK tool. The ngrok.py file starts the NGROK service and reads the current tunnel link and sends it to the myserver.php file that is hosted on a free linux web hosting. The myserver.php file saves the current tunnel link to a text file on the server. Whenever the myserver.php file is accessed from internet, it redirects the connection to the current tunnel link. After every 8 hours, the ngrok.py script kills te running ngrok service and re-starts it. And the new tunnel link is sent to the myserver.php file which is then updated in the text file.

If you have a better solution, your contributions are welcomed. :)

ngrok_unlimited's Issues

Link posting idea

Hello, just wanna give my advice on more ideas.

I believe that the people that would want to use this (me included) want a way to make a server public without exposing their identity, so using another server to upload the link might not be perfect.
Ideas i got for this:

• Using a Discord bot
• Using a TOR hidden service

Using Discord makes it easy to call for the server "on demand" and might be worth to look into, tho bots now need a public static address now because of the new API (and because of abusive bots ideas such as mine).

Using TOR on the other hand is almost perfect, as it would hide everything, tho it would bulk the script a bit. I might look into that.