Closed EvanR-Dev closed 1 month ago
Checking our logs
The tunnel timed out after about over an hour (which is expected):
From this the site name was: vrdmr-python310-2048-sea-1 Narrowing it down to the pod here:
On 2024-08-28T19:09:50.2991866Z, Healthy pod found for Limelight tunnel amusing-mountain-xcccv9b.asse: 49a359d2-638604689694387602 (pod id)
2024-08-28T19:09:56.1139958Z, Limelight tunnel amusing-mountain-xcccv9b.asse host connection is established and ready for clients to connect. Updated status to Healthy
2024-08-28T20:15:33.7985769Z, the tunnel is deleted because max timeout is reached
All of this is once again expected behavior. Therefore it is a client issue/DevTunnels service reliability issue. This will be added to a list of "bad tunnels"
Function app name
No response
Tunnel ID (if available)
amusing-mountain-xcccv9b.asse
Expected Behavior *
Timeout after 1 hr
Actual Behavior *
Timed out before 1 hr (~40 min)
Steps to Reproduce
No response
Environment
No response
Additional Information
No response
Screenshots
No response
Error Logs
No response
Suggested Fix
No response
Priority
Low (happening rarely)