You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ngrok can sometimes be blocked by corporate firewalls https://ngrok.com/docs/guides/other-guides/running-behind-firewalls/
We can have people test their connection when we see they have specific errors in their logs, but it would be nice if the helm chart could test this for you when installing it.
You can run the diagnose command in the ngrok agent container easily like this
This feels like a great first step. Yes, and....we should get something added long term which has ngrok network checks as a first class citizen and does them periodically as DNS and network segments can have intermittent issues.
This feels like a great first step. Yes, and....we should get something added long term which has ngrok network checks as a first class citizen and does them periodically as DNS and network segments can have intermittent issues.
Yeah, are you thinking something like ngrok-go has functions available for these checks that we can then wire up to the operator's readiness probe?
Description
ngrok can sometimes be blocked by corporate firewalls https://ngrok.com/docs/guides/other-guides/running-behind-firewalls/
We can have people test their connection when we see they have specific errors in their logs, but it would be nice if the helm chart could test this for you when installing it.
You can run the diagnose command in the ngrok agent container easily like this
We should include this as a helm
pre-install
andpre-upgrade
hooks as well as a helm test that could then be ran ad-hoc viahelm test ngrok-operator
Use Case
Inform users quickly of a specific network issue rather than them installing it and having to debug the logs to find network errors
Related issues
No response
The text was updated successfully, but these errors were encountered: