🐛 Weird logging on high loglevel

[svenvg93]

Describe the bug
Incomplete logging when using warn or error loglevel

To Reproduce
I have step up the log file and log leve. When using the standard the info I can the tunnels connects and gets config

{"level":"info","time":"2024-07-01T18:40:32Z","message":"GOOS: linux, GOVersion: go1.22.2-devel-cf, GoArch: amd64"}
{"level":"info","time":"2024-07-01T18:40:32Z","message":"Settings: map[no-autoupdate:true]"}
{"level":"info","time":"2024-07-01T18:40:32Z","message":"Environmental variables map[TUNNEL_LOGFILE:/tmp/tunnel.log TUNNEL_LOGLEVEL:info TUNNEL_METRICS:0.0.0.0:60123 TUNNEL_TOKEN:*****]"}
{"level":"info","time":"2024-07-01T18:40:32Z","message":"Generated Connector ID: 41d24395-55a0-4112-9240-04e3c371fb5c"}
{"level":"info","time":"2024-07-01T18:40:32Z","message":"Initial protocol quic"}
{"level":"info","time":"2024-07-01T18:40:32Z","message":"ICMP proxy will use 192.168.48.4 as source for IPv4"}
{"level":"info","time":"2024-07-01T18:40:32Z","message":"ICMP proxy will use ::1 in zone lo as source for IPv6"}
{"level":"info","time":"2024-07-01T18:40:32Z","message":"Starting metrics server on [::]:60123/metrics"}
{"level":"info","event":0,"connection":"bef070b1-8b85-4142-867c-813715d493e2","connIndex":0,"location":"ams06","ip":"198.41.200.63","protocol":"quic","time":"2024-07-01T18:40:32Z","message":"Registered tunnel connection"}
{"level":"info","event":0,"connection":"098b7cda-045a-49fa-b7a9-a86aa8c49ff9","connIndex":1,"location":"ams15","ip":"198.41.192.227","protocol":"quic","time":"2024-07-01T18:40:33Z","message":"Registered tunnel connection"}
{"level":"info","event":0,"connection":"a771a871-6ca0-4ec8-8fca-055212d4e6f0","connIndex":2,"location":"ams01","ip":"198.41.200.233","protocol":"quic","time":"2024-07-01T18:40:34Z","message":"Registered tunnel connection"}
{"level":"info","event":0,"connection":"8f3df6dc-1ffa-4ffd-8f10-8ec58f8de966","connIndex":3,"location":"ams08","ip":"198.41.192.37","protocol":"quic","time":"2024-07-01T18:40:34Z","message":"Registered tunnel connection"}
{"level":"info","version":4,"config":"{\"ingress\":[{\"hostname\":\"stt.example.com\",\"originRequest\":{},\"service\":\"http://speedtest-tracker\"},{\"service\":\"http_status:404\"}],\"warp-routing\":{\"enabled\":false}}","time":"2024-07-01T18:40:36Z","message":"Updated to new configuration"}

Then I set the level to warn or error
I dont see that the tunnels connects and gets a config just a termination

{"level":"error","event":0,"ip":"198.41.200.73","connIndex":3,"error":"Application error 0x0 (remote)","time":"2024-07-01T18:44:16Z","message":"Failed to serve quic connection"}
{"level":"error","event":0,"ip":"198.41.200.73","connIndex":3,"error":"Application error 0x0 (remote)","time":"2024-07-01T18:44:16Z","message":"Serve tunnel error"}
{"level":"error","event":0,"ip":"198.41.192.57","connIndex":2,"error":"Application error 0x0 (remote)","time":"2024-07-01T18:44:16Z","message":"Failed to serve quic connection"}
{"level":"error","event":0,"ip":"198.41.192.57","connIndex":2,"error":"Application error 0x0 (remote)","time":"2024-07-01T18:44:16Z","message":"Serve tunnel error"}
{"level":"error","event":0,"ip":"198.41.192.227","connIndex":1,"error":"Application error 0x0 (remote)","time":"2024-07-01T18:44:16Z","message":"Failed to serve quic connection"}
{"level":"error","event":0,"ip":"198.41.192.227","connIndex":1,"error":"Application error 0x0 (remote)","time":"2024-07-01T18:44:16Z","message":"Serve tunnel error"}
{"level":"error","event":0,"ip":"198.41.200.33","connIndex":0,"error":"Application error 0x0 (remote)","time":"2024-07-01T18:44:16Z","message":"Failed to serve quic connection"}
{"level":"error","event":0,"ip":"198.41.200.33","connIndex":0,"error":"Application error 0x0 (remote)","time":"2024-07-01T18:44:16Z","message":"Serve tunnel error"}
{"level":"error","time":"2024-07-01T18:44:16Z","message":"no more connections active and exiting"}
{"level":"error","error":"context canceled","time":"2024-07-01T18:44:16Z","message":"icmp router terminated"}

In all scenario’s the tunnel is up and works. Just the logging that does not seem to reflect what is happening in higher levels.

If it's an issue with Cloudflare Tunnel:
5. Tunnel ID : a5b80d6a-ba3f-40d6-9825-09e75a0e73e5
6. cloudflared config:

Expected behavior
A clear and concise description of what you expected to happen.

Environment and versions

• OS: Ubuntu server 24.04
• Architecture: AMD
• Version: 2024.6.1 in Docker

Logs and errors
See above

Additional context
Add any other context about the problem here.