Skip to content

v1.6.1 — Fix Tailscale binding and CORS

Choose a tag to compare

@yoavmagor yoavmagor released this 02 Apr 09:45
· 315 commits to main since this release

What's fixed

  • Server binding: The service now correctly binds to 0.0.0.0 when tailscaleHostname is configured, restoring Tailscale access after the v1.6.0 refactor.
  • CORS for raw Tailscale IP: The server detects the local Tailscale IP at startup (tailscale ip -4) and adds it to the allowed origins, so accessing wolfpack via the raw 100.x.x.x address no longer returns 403 origin not allowed.

Both issues were regressions introduced in the almogdepaz#43 refactor. See PR almogdepaz#104 on the upstream repo.