starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

ERR noise upgrade failed error="no next protocol in HTTP request" #316

New Issue
Closed
opened 2025-12-29 01:26:47 +01:00 by adam · 3 comments
adam commented 2025-12-29 01:26:47 +01:00
Owner
Copy Link

Originally created by @rjmalagon on GitHub (Sep 2, 2022).

On v0.17.0-alpha1 , when a linux tailscale 1.30 node try login.

 # Health check:
 #     - not logged in, last login error=register request: Post "https://domain.tld/machine/register": all connection attempts failed > (HTTP: unexpected HTTP response: 301 Moved Permanently, HTTPS: unexpected HTTP response: 400 Bad Request)
 unexpected state: NoState

while the headscale server register this on logs

2022-09-02T16:24:40Z` ERR noise upgrade failed error="no next protocol in HTTP request"
2022/09/02 16:24:40 http: superfluous response.WriteHeader call from github.com/juanfont/headscale.(*Headscale).NoiseUpgradeHandler (noise.go:29)

I got this headscale instance on a podman container (official image), listen on a http port, and exposed to public via a cloudflared reverse proxy

config.yaml extract:

server_url: https://domain.tld:443
listen_addr: 0.0.0.0:8080
Originally created by @rjmalagon on GitHub (Sep 2, 2022). On v0.17.0-alpha1 , when a linux tailscale 1.30 node try login. ``` # Health check: # - not logged in, last login error=register request: Post "https://domain.tld/machine/register": all connection attempts failed > (HTTP: unexpected HTTP response: 301 Moved Permanently, HTTPS: unexpected HTTP response: 400 Bad Request) unexpected state: NoState ``` while the headscale server register this on logs ``` 2022-09-02T16:24:40Z` ERR noise upgrade failed error="no next protocol in HTTP request" 2022/09/02 16:24:40 http: superfluous response.WriteHeader call from github.com/juanfont/headscale.(*Headscale).NoiseUpgradeHandler (noise.go:29) ``` I got this headscale instance on a podman container (official image), listen on a http port, and exposed to public via a cloudflared reverse proxy config.yaml extract: ``` server_url: https://domain.tld:443 listen_addr: 0.0.0.0:8080 ```
adam added the bug label 2025-12-29 01:26:47 +01:00
adam closed this issue 2025-12-29 01:26:47 +01:00
adam commented 2025-12-29 01:26:47 +01:00
Author
Owner
Copy Link

@juanfont commented on GitHub (Sep 4, 2022):

@rjmalagon this is not a bug in Headscale, but a misconfiguration in your reverse proxy.

Headscale >0.17.x requieres proxying WebSockets to Headscale. Can you take a look to your config and come back to us?

@juanfont commented on GitHub (Sep 4, 2022): @rjmalagon this is not a bug in Headscale, but a misconfiguration in your reverse proxy. Headscale >0.17.x requieres proxying WebSockets to Headscale. Can you take a look to your config and come back to us?
adam commented 2025-12-29 01:26:47 +01:00
Author
Owner
Copy Link

@rjmalagon commented on GitHub (Sep 5, 2022):

Thanks, I was the useful idiot to illustrate this particular case.
Cloudflare Tunnel reverse proxy does not support update https to wss on same host, and interfere with mTLS client side validation. So no Cloudflare reverse proxy for this.

@rjmalagon commented on GitHub (Sep 5, 2022): Thanks, I was the useful idiot to illustrate this particular case. Cloudflare Tunnel reverse proxy does not support update https to wss on same host, and interfere with mTLS client side validation. So no Cloudflare reverse proxy for this.
adam commented 2025-12-29 01:26:48 +01:00
Author
Owner
Copy Link

@mannp commented on GitHub (Sep 26, 2022):

Thanks, I was the useful idiot to illustrate this particular case. Cloudflare Tunnel reverse proxy does not support update https to wss on same host, and interfere with mTLS client side validation. So no Cloudflare reverse proxy for this.

Mmh, that is likely my same issue, then :-/ thanks for highlighting it.

@mannp commented on GitHub (Sep 26, 2022): > Thanks, I was the useful idiot to illustrate this particular case. Cloudflare Tunnel reverse proxy does not support update https to wss on same host, and interfere with mTLS client side validation. So no Cloudflare reverse proxy for this. Mmh, that is likely my same issue, then :-/ thanks for highlighting it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#316
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?