Can not get the lets encrypt part to work. #41

Closed
opened 2025-12-29 01:20:53 +01:00 by adam · 6 comments
Owner

Originally created by @urskog84 on GitHub (Oct 3, 2021).

Hi!

Any one more then me having problem setup ssl?

I get the folowing hint in the log?

headscale    | 2021/10/03 17:05:22 http: TLS handshake error from 192.168.1.1:58247: Get "https://acme-v02.api.letsencrypt.org/directory": x509: certificate signed by unknown authority
---
server_url: https://urskog.ddns.net
listen_addr: 0.0.0.0:443
ip_prefix: 100.64.0.0/10
log_level: debug
private_key_path: private.key
db_type: postgres
db_host: postgres
db_port: 5432
db_name: headscale
db_user: foo
db_pass: bar
derp_map_path: derp.yaml
ephemeral_node_inactivity_timeout: 30m
#tls_cert_path: ""
#tls_key_path: ""
tls_letsencrypt_hostname: urskog.ddns.net
tls_letsencrypt_cache_dir: tls_cache
tls_letsencrypt_challenge_type: HTTP-01
tls_letsencrypt_listen: :http
dns_config:
  nameservers:
    - 1.1.1.1
Originally created by @urskog84 on GitHub (Oct 3, 2021). Hi! Any one more then me having problem setup ssl? I get the folowing hint in the log? ``` headscale | 2021/10/03 17:05:22 http: TLS handshake error from 192.168.1.1:58247: Get "https://acme-v02.api.letsencrypt.org/directory": x509: certificate signed by unknown authority ``` ```yml --- server_url: https://urskog.ddns.net listen_addr: 0.0.0.0:443 ip_prefix: 100.64.0.0/10 log_level: debug private_key_path: private.key db_type: postgres db_host: postgres db_port: 5432 db_name: headscale db_user: foo db_pass: bar derp_map_path: derp.yaml ephemeral_node_inactivity_timeout: 30m #tls_cert_path: "" #tls_key_path: "" tls_letsencrypt_hostname: urskog.ddns.net tls_letsencrypt_cache_dir: tls_cache tls_letsencrypt_challenge_type: HTTP-01 tls_letsencrypt_listen: :http dns_config: nameservers: - 1.1.1.1 ```
adam added the bug label 2025-12-29 01:20:53 +01:00
adam closed this issue 2025-12-29 01:20:53 +01:00
Author
Owner

@cure commented on GitHub (Oct 3, 2021):

This worked for me as recently as yesterday.

It looks like your computer can not establish a TLS handshake with the Let's Encrypt directory endpoint at "https://acme-v02.api.letsencrypt.org/directory". Maybe your local list of CA certificates is out of date?

@cure commented on GitHub (Oct 3, 2021): This worked for me as recently as yesterday. It looks like your computer can not establish a TLS handshake with the Let's Encrypt directory endpoint at "https://acme-v02.api.letsencrypt.org/directory". Maybe your local list of CA certificates is out of date?
Author
Owner

@urskog84 commented on GitHub (Oct 4, 2021):

I use the docker image, from https://hub.docker.com/u/headscale

FROM headscale/headscale:0.9.2

@urskog84 commented on GitHub (Oct 4, 2021): I use the docker image, from https://hub.docker.com/u/headscale FROM headscale/headscale:0.9.2
Author
Owner

@juanfont commented on GitHub (Oct 16, 2021):

@urskog84 are you still having this issue?

@juanfont commented on GitHub (Oct 16, 2021): @urskog84 are you still having this issue?
Author
Owner

@cure commented on GitHub (Oct 16, 2021):

@urskog84 if you are still seeing this, can you try again with the latest Headscale docker image? I suspect the Let's Encrypt root certificate change (https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/) could be causing this.

@cure commented on GitHub (Oct 16, 2021): @urskog84 if you are still seeing this, can you try again with the latest Headscale docker image? I suspect the Let's Encrypt root certificate change (https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/) could be causing this.
Author
Owner

@sinatics commented on GitHub (Oct 26, 2021):

@juanfont I'm getting this error as well, using the docker image headscale/headscale:latest

EDIT: I updated to the image that was pushed recently and it's now working just fine!

@sinatics commented on GitHub (Oct 26, 2021): _@juanfont I'm getting this error as well, using the docker image headscale/headscale:latest_ EDIT: I updated to the image that was pushed recently and it's now working just fine!
Author
Owner

@cure commented on GitHub (Oct 31, 2021):

@juanfont I'm getting this error as well, using the docker image headscale/headscale:latest

EDIT: I updated to the image that was pushed recently and it's now working just fine!

That confirms what I thought; this was caused by the Let's Encrypt root cert change, and the new docker images have the necessary updates. Closing this issue.

@cure commented on GitHub (Oct 31, 2021): > _@juanfont I'm getting this error as well, using the docker image headscale/headscale:latest_ > > EDIT: I updated to the image that was pushed recently and it's now working just fine! That confirms what I thought; this was caused by the Let's Encrypt root cert change, and the new docker images have the necessary updates. Closing this issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#41