fix(infra): serve full TLS chain for epicnabbo.nl to resolve Cloudflare 525
Local Build and Deploy / deploy (push) Successful in 1m2s

Traefik's ACME resolver stored the epicnabbo.nl leaf certificate without
the Let's Encrypt intermediate. With Cloudflare in Full (strict) mode the
origin TLS handshake failed (HTTP 525), breaking every asset and the whole
site layout (JS/CSS chunks, Nitro client, toolbar).

Configure the epicnabbo router to use a file-based certificate that
includes the full chain (leaf + LE YR2 intermediate), referenced from
dynamic/epicnabbo-tls.yml. Add a regeneration script and README.
This commit is contained in:
openhands committed 2026-07-18 18:37:56 +02:00
1 parent 243f8007d9
commit 8292cc8ffb
5 files changed
+138

No files matched your search

+4
View File
@@ -0,0 +1,4 @@
tls:
certificates:
- certFile: /etc/traefik/dynamic/epicnabbo-fullchain.pem
keyFile: /etc/traefik/dynamic/epicnabbo-key.pem
+22
View File
@@ -0,0 +1,22 @@
http:
routers:
epicnabbo:
entryPoints:
- websecure
rule: "Host(`epicnabbo.nl`) || Host(`www.epicnabbo.nl`)"
service: epicnabbo-svc
middlewares:
- default-security-headers
tls: {}
services:
epicnabbo-svc:
loadBalancer:
passHostHeader: true
serversTransport: epicnabbo-transport
servers:
- url: "https://172.21.0.1:9443"
serversTransports:
epicnabbo-transport:
insecureSkipVerify: true