New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tailscale-proxy fails with TLS #27
Comments
Downgrading to Caddy v2.6.4 does not resolve the issue. |
I have the same issue. |
willnorris
added a commit
that referenced
this issue
May 16, 2024
Implement reverseproxy.TLSTransport. We go ahead and store the provided TLSConfig object, but for now we only use it to indicate that we should use TLS. We don't actually use any of the provided values to configure the client. Fixes #27
willnorris
added a commit
that referenced
this issue
May 16, 2024
Implement reverseproxy.TLSTransport. We go ahead and store the provided TLSConfig object, but for now we only use it to indicate that we should use TLS. We don't actually use any of the provided values to configure the client. Fixes #27 Signed-off-by: Will Norris <will@tailscale.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you use tailscale-proxy with HTTPS/TLS, it tries to start QUIC and then fails:
This is from inside a container:
Using the command
['/usr/bin/caddy', 'tailscale-proxy', '--from', 'tailscale/myhost:443', '--to', 'backend:7071']
The text was updated successfully, but these errors were encountered: