🐛 Tunnel command crashing with "Application error 0x0"

**Describe the bug**
The tunnel command fails intermittently and it crashes showing `Application error 0x0`. I've seen this error several times during short periods of time (~1h), a few times in the last week.

I'm running it from Spain and my connection is fast and stable (1 Gbps).

**To Reproduce**
`cloudflared tunnel --url http://localhost:3000`

If it's an issue with Cloudflare Tunnel:
4. Tunnel ID: no ID
5. cloudflared config: no config

**Expected behavior**
The tunnel should be created and registered, and the command keep open

**Environment and versions**
- OS: MacOS
- Architecture: arm64
- Version: 2023.4.0

**Logs and errors**

cloudflared tunnel --url http://localhost:3000

```
❯ cloudflared tunnel --url http://localhost:3000
2023-04-18T14:06:08Z INF Thank you for trying Cloudflare Tunnel. Doing so, without a Cloudflare account, is a quick way to experiment and try it out. However, be aware that these account-less Tunnels have no uptime guarantee. If you intend to use Tunnels in production you should use a pre-created named tunnel by following: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
2023-04-18T14:06:08Z INF Requesting new quick Tunnel on trycloudflare.com...
2023-04-18T14:06:11Z INF +--------------------------------------------------------------------------------------------+
2023-04-18T14:06:11Z INF | Your quick Tunnel has been created! Visit it at (it may take some time to be reachable): |
2023-04-18T14:06:11Z INF | https://leaving-uncle-instead-copied.trycloudflare.com |
2023-04-18T14:06:11Z INF +--------------------------------------------------------------------------------------------+
2023-04-18T14:06:11Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]
2023-04-18T14:06:11Z INF Version 2023.4.0
2023-04-18T14:06:11Z INF GOOS: darwin, GOVersion: go1.19.8, GoArch: arm64
2023-04-18T14:06:11Z INF Settings: map[ha-connections:1 protocol:quic url:http://localhost:3000]
2023-04-18T14:06:11Z INF cloudflared will not automatically update if installed by a package manager.
2023-04-18T14:06:11Z INF Generated Connector ID: 89a2c6dc-d41e-4c2d-a282-07299021c295
2023-04-18T14:06:11Z INF Initial protocol quic
2023-04-18T14:06:11Z INF ICMP proxy will use 192.168.1.84 as source for IPv4
2023-04-18T14:06:11Z INF ICMP proxy will use fe80::14ad:ef7e:5f7f:2854 in zone en0 as source for IPv6
2023-04-18T14:06:11Z INF Created ICMP proxy listening on 192.168.1.84:0
2023-04-18T14:06:11Z INF Created ICMP proxy listening on [fe80::14ad:ef7e:5f7f:2854%en0]:0
2023-04-18T14:06:11Z INF Starting metrics server on 127.0.0.1:52974/metrics
2023-04-18T14:06:11Z ERR Failed to serve quic connection error="Application error 0x0" connIndex=0 ip=198.41.192.227
2023-04-18T14:06:11Z ERR Serve tunnel error error="Application error 0x0" connIndex=0 ip=198.41.192.227
2023-04-18T14:06:11Z INF Retrying connection in up to 2s connIndex=0 ip=198.41.192.227
2023-04-18T14:06:11Z ERR update check failed error="no release found"
2023-04-18T14:06:11Z INF Tunnel server stopped
2023-04-18T14:06:11Z ERR Initiating shutdown error="Application error 0x0"
2023-04-18T14:06:11Z INF Metrics server stopped
Application error 0x0
```

cloudflared tunnel --url http://localhost:3000 --protocol http2

```
❯ cloudflared tunnel --url http://localhost:3000 --protocol http2
2023-04-18T14:06:46Z INF Thank you for trying Cloudflare Tunnel. Doing so, without a Cloudflare account, is a quick way to experiment and try it out. However, be aware that these account-less Tunnels have no uptime guarantee. If you intend to use Tunnels in production you should use a pre-created named tunnel by following: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
2023-04-18T14:06:46Z INF Requesting new quick Tunnel on trycloudflare.com...
2023-04-18T14:06:49Z INF +--------------------------------------------------------------------------------------------+
2023-04-18T14:06:49Z INF | Your quick Tunnel has been created! Visit it at (it may take some time to be reachable): |
2023-04-18T14:06:49Z INF | https://buffalo-marco-cardiff-motel.trycloudflare.com |
2023-04-18T14:06:49Z INF +--------------------------------------------------------------------------------------------+
2023-04-18T14:06:49Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]
2023-04-18T14:06:49Z INF Version 2023.4.0
2023-04-18T14:06:49Z INF GOOS: darwin, GOVersion: go1.19.8, GoArch: arm64
2023-04-18T14:06:49Z INF Settings: map[ha-connections:1 p:http2 protocol:http2 url:http://localhost:3000]
2023-04-18T14:06:49Z INF Generated Connector ID: cded8449-3cc8-4331-bf5d-9589ca52c439
2023-04-18T14:06:49Z INF cloudflared will not automatically update if installed by a package manager.
2023-04-18T14:06:49Z INF Initial protocol http2
2023-04-18T14:06:49Z INF ICMP proxy will use 192.168.1.84 as source for IPv4
2023-04-18T14:06:49Z INF ICMP proxy will use fe80::14ad:ef7e:5f7f:2854 in zone en0 as source for IPv6
2023-04-18T14:06:49Z INF Created ICMP proxy listening on 192.168.1.84:0
2023-04-18T14:06:49Z INF Created ICMP proxy listening on [fe80::14ad:ef7e:5f7f:2854%en0]:0
2023-04-18T14:06:49Z INF Starting metrics server on 127.0.0.1:53135/metrics
2023-04-18T14:06:49Z ERR update check failed error="no release found"
2023-04-18T14:06:49Z ERR failed to serve incoming request error="Cloudflared reached the Cloudflare edge, but there was an unknown error registering the connection"
2023-04-18T14:06:49Z ERR Register tunnel error from server side error="Cloudflared reached the Cloudflare edge, but there was an unknown error registering the connection" connIndex=0 ip=198.41.192.47
2023-04-18T14:06:49Z INF Retrying connection in up to 2s connIndex=0 ip=198.41.192.47
2023-04-18T14:06:50Z INF Tunnel server stopped
2023-04-18T14:06:50Z ERR Initiating shutdown error="Cloudflared reached the Cloudflare edge, but there was an unknown error registering the connection"
2023-04-18T14:06:50Z INF Metrics server stopped
Cloudflared reached the Cloudflare edge, but there was an unknown error registering the connection
```

cloudflared tunnel --url http://localhost:3000 --loglevel debug (with version 2022.8.2)

```
❯ cloudflared tunnel --url http://localhost:3000 --loglevel debug
2023-04-18T13:01:14Z INF Thank you for trying Cloudflare Tunnel. Doing so, without a Cloudflare account, is a quick way to experiment and try it out. However, be aware that these account-less Tunnels have no uptime guarantee. If you intend to use Tunnels in production you should use a pre-created named tunnel by following: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
2023-04-18T13:01:14Z INF Requesting new quick Tunnel on trycloudflare.com...
2023-04-18T13:01:16Z INF +--------------------------------------------------------------------------------------------+
2023-04-18T13:01:16Z INF | Your quick Tunnel has been created! Visit it at (it may take some time to be reachable): |
2023-04-18T13:01:16Z INF | https://heather-asin-transit-offered.trycloudflare.com |
2023-04-18T13:01:16Z INF +--------------------------------------------------------------------------------------------+
2023-04-18T13:01:16Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]
2023-04-18T13:01:16Z INF Version 2022.8.2
2023-04-18T13:01:16Z INF GOOS: darwin, GOVersion: go1.19, GoArch: arm64
2023-04-18T13:01:16Z INF Settings: map[loglevel:debug protocol:quic url:http://localhost:3000]
2023-04-18T13:01:16Z INF Generated Connector ID: 18672d3b-4aa8-420d-b3ee-2e715bc615b4
2023-04-18T13:01:16Z INF cloudflared will not automatically update if installed by a package manager.
2023-04-18T13:01:16Z INF Initial protocol quic
2023-04-18T13:01:16Z DBG looking up edge SRV record domain=_v2-origintunneld._tcp.argotunnel.com
2023-04-18T13:01:16Z INF Starting metrics server on 127.0.0.1:61416/metrics
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.192.167:7844 UDP:198.41.192.167:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.192.57:7844 UDP:198.41.192.57:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.192.7:7844 UDP:198.41.192.7:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.192.27:7844 UDP:198.41.192.27:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.192.77:7844 UDP:198.41.192.77:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.192.37:7844 UDP:198.41.192.37:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.192.227:7844 UDP:198.41.192.227:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.192.107:7844 UDP:198.41.192.107:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.192.67:7844 UDP:198.41.192.67:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.192.47:7844 UDP:198.41.192.47:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a0::7]:7844 UDP:[2606:4700:a0::7]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a0::8]:7844 UDP:[2606:4700:a0::8]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a0::10]:7844 UDP:[2606:4700:a0::10]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a0::9]:7844 UDP:[2606:4700:a0::9]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a0::3]:7844 UDP:[2606:4700:a0::3]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a0::5]:7844 UDP:[2606:4700:a0::5]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a0::1]:7844 UDP:[2606:4700:a0::1]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a0::2]:7844 UDP:[2606:4700:a0::2]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a0::4]:7844 UDP:[2606:4700:a0::4]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a0::6]:7844 UDP:[2606:4700:a0::6]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.200.33:7844 UDP:198.41.200.33:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.200.113:7844 UDP:198.41.200.113:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.200.43:7844 UDP:198.41.200.43:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.200.23:7844 UDP:198.41.200.23:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.200.73:7844 UDP:198.41.200.73:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.200.233:7844 UDP:198.41.200.233:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.200.53:7844 UDP:198.41.200.53:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.200.13:7844 UDP:198.41.200.13:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.200.63:7844 UDP:198.41.200.63:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:198.41.200.193:7844 UDP:198.41.200.193:7844 IPVersion:4}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a8::4]:7844 UDP:[2606:4700:a8::4]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a8::10]:7844 UDP:[2606:4700:a8::10]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a8::1]:7844 UDP:[2606:4700:a8::1]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a8::6]:7844 UDP:[2606:4700:a8::6]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a8::7]:7844 UDP:[2606:4700:a8::7]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a8::5]:7844 UDP:[2606:4700:a8::5]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a8::8]:7844 UDP:[2606:4700:a8::8]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a8::2]:7844 UDP:[2606:4700:a8::2]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a8::3]:7844 UDP:[2606:4700:a8::3]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG Edge Address: {TCP:[2606:4700:a8::9]:7844 UDP:[2606:4700:a8::9]:7844 IPVersion:6}
2023-04-18T13:01:16Z DBG edgediscovery - GetAddr: Giving connection its new address connIndex=0 ip=198.41.200.73
2023-04-18T13:01:16Z DBG rpcconnect: tx (bootstrap = (questionId = 0, deprecatedObjectId = ))
2023-04-18T13:01:16Z DBG rpcconnect: tx (call = (questionId = 1, target = (promisedAnswer = (questionId = 0, transform = [])), interfaceId = 17804583019846587543, methodId = 0, allowThirdPartyTailCall = false, params = (content = , capTable = []), sendResultsTo = (caller = void)))
2023-04-18T13:01:16Z DBG rpcconnect: rx (return = (answerId = 0, releaseParamCaps = false, results = (content = , capTable = [(senderHosted = 0)])))
2023-04-18T13:01:16Z DBG rpcconnect: tx (finish = (questionId = 0, releaseResultCaps = false))
2023-04-18T13:01:16Z ERR update check failed error="no release found"
2023-04-18T13:01:17Z DBG rpcconnect: rx error: Application error 0x0
2023-04-18T13:01:17Z ERR Failed to serve quic connection error="failed to accept QUIC stream: Application error 0x0" connIndex=0 ip=198.41.200.73
2023-04-18T13:01:17Z ERR Serve tunnel error error="failed to accept QUIC stream: Application error 0x0" connIndex=0 ip=198.41.200.73
2023-04-18T13:01:17Z INF Retrying connection in up to 2s seconds connIndex=0 ip=198.41.200.73
2023-04-18T13:01:17Z INF Tunnel server stopped
2023-04-18T13:01:17Z ERR Initiating shutdown error="failed to accept QUIC stream: Application error 0x0"
2023-04-18T13:01:17Z INF Metrics server stopped
failed to accept QUIC stream: Application error 0x0
```