Quick Installer Sets Incorrect Values for Traefik Causing SSL Cert Renewal Issues #690

New Issue

2025-11-13T12:07:54-06:00

GiteaMirror commented

2025-11-13 12:07:54 -06:00

Originally created by @VashEXE on GitHub (Sep 24, 2025).

Originally assigned to: @oschwartz10612 on GitHub.

Version: v1.9.4
OS: Ubuntu 24.04
linux_amd64
Docker

Using the installer works as expected during setup. All values are entered as requested by Pangolin, but in the Traefik dynamic_config.yml the Host value for all of the rules is entered as:

https://pangolin.my.domain

rather than the correct value:

pangolin.my.domain

The initial installation seems to generate the letsencrypt certs as expected, but when renewal time comes around an error is generated stating:

traefik | {"level":"error","providerName":"letsencrypt.acme","acmeCA":"https://acme-v02.api.letsencrypt.org/directory","providerName":"letsencrypt.acme","ACME CA":"https://acme-v02.api.letsencrypt.org/directory","routerName":"ws-router@file","rule":"Host(`https://pangolin.my.domain`)","error":"unable to generate a certificate for the domains [https://pangolin.my.domain]: acme: error: 400 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Invalid identifiers requested :: Cannot issue for \"https://pangolin.my.domain\": Domain name contains an invalid character","domains":["https://pangolin.my.domain"],"time":"2025-09-24T02:36:49Z","message":"Unable to obtain ACME certificate for domains"}

After manually removing the https:// from all instances of the host name in the dynamic_config.yml the cert generates as expected and works fine. I'm unsure if this is an issue with the installer itself or where this problem is, but I actually documented my installer output and noted that I explicitly entered pangolin.my.domain and not https://pangolin.my.domain , but still ended up having that https:// added in the dynamic config which causes Let's Encrypt cert renewal to fail.

Let me know if there is any other info I can provide on this.

Thanks!

Originally created by @VashEXE on GitHub (Sep 24, 2025). Originally assigned to: @oschwartz10612 on GitHub. **Version:** v1.9.4 **OS:** Ubuntu 24.04 linux_amd64 Docker Using the installer works as expected during setup. All values are entered as requested by Pangolin, but in the Traefik dynamic_config.yml the Host value for all of the rules is entered as: ```https://pangolin.my.domain``` rather than the correct value: ```pangolin.my.domain``` The initial installation seems to generate the letsencrypt certs as expected, but when renewal time comes around an error is generated stating: ``` traefik | {"level":"error","providerName":"letsencrypt.acme","acmeCA":"https://acme-v02.api.letsencrypt.org/directory","providerName":"letsencrypt.acme","ACME CA":"https://acme-v02.api.letsencrypt.org/directory","routerName":"ws-router@file","rule":"Host(`https://pangolin.my.domain`)","error":"unable to generate a certificate for the domains [https://pangolin.my.domain]: acme: error: 400 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Invalid identifiers requested :: Cannot issue for \"https://pangolin.my.domain\": Domain name contains an invalid character","domains":["https://pangolin.my.domain"],"time":"2025-09-24T02:36:49Z","message":"Unable to obtain ACME certificate for domains"}``` After manually removing the https:// from all instances of the host name in the dynamic_config.yml the cert generates as expected and works fine. I'm unsure if this is an issue with the installer itself or where this problem is, but I actually documented my installer output and noted that I explicitly entered ```pangolin.my.domain``` and not ```https://pangolin.my.domain``` , but still ended up having that https:// added in the dynamic config which causes Let's Encrypt cert renewal to fail. Let me know if there is any other info I can provide on this. Thanks!

GiteaMirror added the needs investigating bug labels 2025-11-13 12:07:54 -06:00

GiteaMirror closed this issue

2025-11-13 12:07:55 -06:00

GiteaMirror commented

2025-11-13 12:07:56 -06:00

@miloschwartz commented on GitHub (Sep 26, 2025):

Is this just when installing Crowdsec or is does it happen when doing a fresh install?

@miloschwartz commented on GitHub (Sep 26, 2025): Is this just when installing Crowdsec or is does it happen when doing a fresh install?

GiteaMirror commented

2025-11-13 12:07:56 -06:00

@miloschwartz commented on GitHub (Sep 26, 2025):

I identified and fixed the issue for the Crowdsec in the latest installer for latest release

@miloschwartz commented on GitHub (Sep 26, 2025): I identified and fixed the issue for the Crowdsec in the latest installer for latest release