dev-tunnels icon indicating copy to clipboard operation
dev-tunnels copied to clipboard

Persistent ERR_CONNECTION_TIMED_OUT & ERR_SSL_PROTOCOL_ERROR errors with devtunnels

Open lmbrandon opened this issue 2 months ago • 2 comments

Haven't been able to use devtunnels.

trying different browsers. I've tried switching clusters. trying on a different pc - mac and windows. Even tried with different projects - python flask & next.js I use the -v flag and i see no issues but when i visit the site i always get a ERR_CONNECTION_TIMED_OUT error.

I also get ERR_SSL_PROTOCOL_ERROR's when i go to the https://{random-string}-PORT.use.devtunnels.ms url I'd appreciate some help with this.

lmbrandon avatar Oct 29 '25 21:10 lmbrandon

I've been running into the same issue

Repro

  1. Run through the devtunnel quickstart
# Start a http server on port 8080
> devtunnel echo http -p 8080

Echo server listening at http://127.0.0.1:8080/ (ws://127.0.0.1:8080/)
# Tunnel port 8080
> devtunnel host -p 8080
Hosting port: 8080
Connect via browser: https://{LABEL}.use.devtunnels.ms:8080, https://{LABEL}-8080.use.devtunnels.ms
Inspect network activity: https://{LABEL}-8080-inspect.use.devtunnels.ms

Ready to accept connections for tunnel: peaceful-ant-grl2mxg.use

Expected outcome

Using either URL (https://{LABEL}.use.devtunnels.ms:8080 or https://{LABEL}-8080.use.devtunnels.ms) should allow me to connect to the devtunnel

Actual outcome

  • Trying to connect to https://{LABEL}.use.devtunnels.ms:8080
    • Causes my browser to load for a while, eventually timing out
  • Trying to connect to https://{LABEL}-8080.use.devtunnels.ms fails with an ssl error
    • My browser claims that the website has no certificate
    • curl shows the following
      *   Trying XXX.XXX.XX.XXX:443...
      * Connected to {LABEL}.use.devtunnels.ms (XXX.XXX.XX.XXX) port 443 (#0)
      * ALPN, offering h2
      * ALPN, offering http/1.1
      *  CAfile: /etc/ssl/certs/ca-certificates.crt
      *  CApath: /etc/ssl/certs
      * TLSv1.0 (OUT), TLS header, Certificate Status (22):
      * TLSv1.3 (OUT), TLS handshake, Client hello (1):
      * TLSv1.2 (IN), TLS header, Unknown (21):
      * TLSv1.3 (IN), TLS alert, close notify (512):
      * error:0A0003E8:SSL routines::reason(1000)
      * Closing connection 0
      curl: (35) error:0A0003E8:SSL routines::reason(1000)
      
  • I am able to hit an auth page with either url if I use http instead of https

kdestin avatar Oct 30 '25 21:10 kdestin

I have the same issue. I've tried it on macOS and windows, same experience with either. Attempting to load the URL results in ERR_SSL_PROTOCOL_ERROR. If I attempt to view the cert, it shows the following message, "This site does not have a certificate."

The steps that @kdestin mentioned are the same nes I raun into. Even attempting to view the "Inspect network activity" URL fails to load.

Any updates on this issue?

ihcnet avatar Nov 11 '25 17:11 ihcnet