Menu
I tried running ngrok in the background with following command:
./ngrok -subdomain test -config=ngrok.cfg 80 & the process is running:
[1] 3866 and the subdomain doesn't work.
It works with:
./ngrok -subdomain test -config=ngrok.cfg 80 Does anyone know what is going wrong here?
Thank you.
775
NGROK is a great tool, but when you are moving to a production environment there are some things to be aware of. Without a license, the NGROK URL will expire after a short period. A single simple tunnel is a single point of failure and can work against you if not managed properly.
Problems using Ngrok One of the new limits is a session expiration time of 2 hours. When an Ngrok connection reaches this length it stops working, and the only way to restore it is by stopping and restarting the ngrok command, which causes a new randomly generated URL to be used.
as explained here
ngrok -log=stdout 80 > /dev/null & If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With