Skip to content
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

Open
jamie-at-arkifi opened this issue Dec 28, 2023 · 2 comments
Open

tailscale-proxy fails with TLS #27

jamie-at-arkifi opened this issue Dec 28, 2023 · 2 comments

Comments

@jamie-at-arkifi
Copy link

When you use tailscale-proxy with HTTPS/TLS, it tries to start QUIC and then fails:

{"level":"warn","ts":1703777283.5945904,"logger":"admin","msg":"admin endpoint disabled"}
{"level":"info","ts":1703777283.620156,"logger":"http.auto_https","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"proxy","https_port":443}
{"level":"info","ts":1703777283.620855,"logger":"http.auto_https","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"proxy"}
{"level":"info","ts":1703777283.620443,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc00021e000"}
{"level":"warn","ts":1703777283.6335611,"logger":"tls","msg":"storage cleaning happened too recently; skipping for now","storage":"FileStorage:/data/caddy","instance":"7f43f41d-9b67-4aae-a7dc-563d96f88d7b","try_again":1703863683.63346,"try_again_in":86399.99999947}
{"level":"info","ts":1703777283.635115,"logger":"tls","msg":"finished cleaning storage units"}
{"level":"info","ts":1703777283.676397,"logger":"http","msg":"enabling HTTP/3 listener","addr":"franklin:443"}
{"level":"info","ts":1703777283.6845386,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc00021e000"}
Error: loading new config: http app module: start: starting HTTP/3 QUIC listener: listen udp 100.84.250.36:443: bind: cannot assign requested address

This is from inside a container:

ARG CADDY_VERSION=latest

FROM docker.io/library/caddy:builder AS build
ENV XCADDY_SKIP_CLEANUP=1
RUN xcaddy build \
    --with github.com/tailscale/caddy-tailscale \
    $CADDY_VERSION

FROM docker.io/library/caddy
COPY --from=build /usr/bin/caddy /usr/bin/caddy

Using the command ['/usr/bin/caddy', 'tailscale-proxy', '--from', 'tailscale/myhost:443', '--to', 'backend:7071']

@jamie-at-arkifi
Copy link
Author

Downgrading to Caddy v2.6.4 does not resolve the issue.

@Keyruu
Copy link

Keyruu commented Jan 23, 2024

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>
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 #25
Fixes #27

Signed-off-by: Will Norris <will@tailscale.com>
willnorris added a commit that referenced this issue May 17, 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 #25
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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants