[Bug] Exessive logging

[pittbull]

Is this a support request?

• This is not a support request

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Headscale successfully up and running behind Nginx Proxy Manager. Logs in NPM suggests a problem reaching DERP:

[24/Oct/2024:13:54:05 +0200] - 404 404 - GET https <URL> "/derp/latency-check" [Client 178.232.163.94] [Length 0] [Gzip -] [Sent-to unraid.home] "Go-http-client/1.1" "-"
[24/Oct/2024:13:54:05 +0200] - 404 404 - GET https <URL> "/derp/latency-check" [Client 178.232.163.94] [Length 0] [Gzip -] [Sent-to unraid.home] "Go-http-client/1.1" "-"
[24/Oct/2024:13:54:16 +0200] - 404 404 - GET https <URL> "/derp/latency-check" [Client 178.232.163.94] [Length 0] [Gzip -] [Sent-to unraid.home] "Go-http-client/1.1" "-"
[24/Oct/2024:13:54:16 +0200] - 404 404 - GET https <URL> "/derp/latency-check" [Client 178.232.163.94] [Length 0] [Gzip -] [Sent-to unraid.home] "Go-http-client/1.1" "-"
[24/Oct/2024:13:54:16 +0200] - 404 404 - GET https <URL> "/derp/latency-check" [Client 192.168.1.19] [Length 0] [Gzip -] [Sent-to unraid.home] "Go-http-client/1.1" "-"
[24/Oct/2024:13:54:16 +0200] - 404 404 - GET https <URL> "/derp/latency-check" [Client 192.168.1.19] [Length 0] [Gzip -] [Sent-to unraid.home] "Go-http-client/1.1" "-"

This is logged every other second.

Expected Behavior

If this indicates a problem I don't know how to solve it. If not could this logging be disabled?

Steps To Reproduce

Start headscale as normal.

Environment

- OS: Unraid
- Headscale version: 0.23.0
- Tailscale version: 1.76.1

Runtime environment

• Headscale is behind a (reverse) proxy
• Headscale runs in a container

Anything else?

No response

[pittbull]

I temporarily reduced the logging by adding a custom location in nginx, and disabling access logging.

As I use these logfiles to analyze access, this events skewed the numbers.

[nblock]

According to tailscale/tailscale@15fc6cd the routes /derp/probe and /derp/latency-check are the same and different versions of the tailscale client use one or the other endpoint.

Headscale currently only supports /derp/probe (see: https://github.com/juanfont/headscale/blob/main/hscontrol/app.go#L462). We should probably handle /derp/latency-check with the same handler.

[nblock]

Since you are using Nginx Proxy Manager, you might as well add an internal redirect on the exact path /derp/latency-check until a fix is available in headscale. Something like:

location = /derp/latency-check {
  rewrite ^/derp/latency-check$ /derp/probe last;
}

[pittbull]

I had to implement your suggestion like this:

This results in going from a 101 message to a 200.

[nblock]

Right, I was actually on track to workaround http/404 and don't care about the logging as you wrote.

Headscale itself does not log requests to /derp/probe or /derp/latency-check, so the excessive logging is only due to the reverse proxy and should be handled there.

[pittbull]

I see. Thanks for the feedback.