setup reverse-proxying for *.staging.diday.org

remove did.hamburg.ccc.de from public-reverse-proxy
configure reverse proxy map explicitly for hostnames
2026-02-27 21:51:09 +01:00 · 2026-02-27 21:51:09 +01:00 · 2026-02-27 21:51:09 +01:00
2 changed files with 2 additions and 4 deletions
--- a/resources/chaosknoten/public-reverse-proxy/nginx/acme_challenge.conf
+++ b/resources/chaosknoten/public-reverse-proxy/nginx/acme_challenge.conf
@ -84,8 +84,6 @@ map $host $upstream_acme_challenge_host {
    local.ccc.de 172.31.17.151:31820;
    acmedns.hamburg.ccc.de acmedns.hosts.hamburg.ccc.de:31820;
    diday.org 172.31.17.151:31820;
-    did.hamburg.ccc.de 172.31.17.151:31820;
-    staging.did.hamburg.ccc.de 172.31.17.151:31820;
    default "";
 }

--- a/resources/chaosknoten/public-reverse-proxy/nginx/nginx.conf
+++ b/resources/chaosknoten/public-reverse-proxy/nginx/nginx.conf
@ -18,6 +18,7 @@ stream {
    resolver 212.12.50.158 192.76.134.90;

    map $ssl_preread_server_name $address {
+        hostnames;
        ccchoir.de ccchoir.hosts.hamburg.ccc.de:8443;
        www.ccchoir.de ccchoir.hosts.hamburg.ccc.de:8443;
        cloud.hamburg.ccc.de cloud.hosts.hamburg.ccc.de:8443;
@ -101,9 +102,8 @@ stream {
        lokal.ccc.de 172.31.17.151:8443;
        local.ccc.de 172.31.17.151:8443;
        acmedns.hamburg.ccc.de acmedns.hosts.hamburg.ccc.de:8443;
-        did.hamburg.ccc.de 172.31.17.151:8443;
        diday.org 172.31.17.151:8443;
-        staging.did.hamburg.ccc.de 172.31.17.151:8443;
+        *.staging.diday.org 172.31.17.151:8443;
    }

    server {
Author	SHA1	Message	Date
lilly	165487884c	setup reverse-proxying for *.staging.diday.org All checks were successful / Ansible Lint (push) Successful in 2m12s Details	2026-02-27 21:51:09 +01:00
lilly	bc9e76b8ed	remove did.hamburg.ccc.de from public-reverse-proxy	2026-02-27 21:51:09 +01:00
lilly	983584a510	configure reverse proxy map explicitly for hostnames	2026-02-27 21:51:09 +01:00