User interaction when DNS errors occur Planned
Noted during a tunnel outage that DNS failures prompted this log entry
[31m2025-01-21T08:37:12-05:00 [error] E-CNT_000024 failed to sent request error: get "https://user.timuscloud.com/users/19469/agent": dial tcp 104.26.5.195:443: connectex: a connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.[0m
It would be great to see some popup, or some interaction to the user that the tunnel is having problems at that moment.
I would also expect the tunnel to somehow be resilient enough to reset itself, if all attempts at DNS fail.
perhaps the interaction to the user could be a button that initiates the “refresh connection” routine so the user doesn't have to search for it in the taskbar.
Comments
4 comments
Thank you for the request. We're happy to let you know this is already on our roadmap for this year and will be introduced in upcoming gateway releases. We'll keep you posted as things move forward.
When this occurs, the agent should generate an event in the admin console. When tunnel or gateways have issues, administrative alerts, SIEM events need to be generated.
Yes Jeremy, I have not checked, but as I found the log entry in the agent log, I assume it is added to the Admin alerts and SEIM events, which are not available to the user. My request is for more user-friendly method within the Agent on the endpoint. Users that require the VPN to operate (Conditional Access to sites) want to know when their VPN is down so they can get IT involved for the correct problem.
I look forward to seeing this post go from “not planned” to “planned” :)
Please sign in to leave a comment.