Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen der Seite angezeigt.

--- content:serverbasics:docker-caddy [2024/01/14 15:19] – [Create Caddy Yaml] obel1x
+++ content:serverbasics:docker-caddy [2025/06/05 23:27] (aktuell) – [Create Caddy Yaml] obel1x
@@ Zeile 3: / Zeile 3: @@
 Caddy is a powerful full featured webserver, which is also easy to use and setup.
-In this guide i will show how to use Caddy as SSL- Proxy for your services to deliver them to the internet via name- based virtual hosting.
+In this guide i will show how to use Caddy as SSL- Reverse- Proxy for your services to deliver them to the internet via name- based virtual hosting.
 ===== Prerequisites =====
@@ Zeile 11: / Zeile 11: @@
 ===== DNS- Records =====
-You will also need a domainname like ''my.domain.tld'' and hostnames, that are resolvable for each service, so that ''service.my.domain.tld'' can be resolved from out of - and in the internet to point to your Server. If you do not have them already, read further, which descripbes how to get them.
+You will also need a domainname like ''my.domain.tld'' and hostnames, that are resolvable for each service, so that ''service.my.domain.tld'' can be resolved from out of - and in the internet to point to your Server. If you do not have them already, read here: [[.:network-dyndns|]]
+When your service sucessfully resolves, you can use it in Caddy as written beneath.
-==== Register some Domain ====
-There are many free Domainproviders out there. I chose dynv6 ( [[https://dynv6.com|https://dynv6.com]] ), but this should work with any of them.
-bla (not ready) blah - setup IPV4 , setup IPV6, bla link to [[.:network-dyndns|https://obel1x.de/dokuwiki/doku.php?id=content:serverbasics:network-dyndns|]]
-==== Define services ====
-After that, create an A-Name record (or AAAA- Name for ipv6) per service without specifying the ip, som that the dynamic ip of the domain will be taken. Only paste the servicename, dynv6 will automagically append your domain (service → service.my.domain.tld)
-In our example this would be nice:
-''portainer'' → ''portainer.my.domain.tld''
 ===== Create Caddy Yaml =====
@@ Zeile 37: / Zeile 25: @@
 <file>
-version: "3.8"
 services:
   caddy:
@@ Zeile 54: / Zeile 40: @@
       - NET_ADMIN
     healthcheck:
-      test: "wget --no-verbose --tries=1 --spider https://obel1x.dynv6.net || exit 1"
+      test: "wget --no-verbose --tries=1 --spider https://www.servername.domainname.tld || exit 1"
       interval: "60s"
       timeout: "3s"
@@ Zeile 60: / Zeile 46: @@
       retries: 3
 # Be sure, that docker daemon has access to unprivileged ports (beneath 1024)
-# Thiscan be done by:
+# This can be archived by:
 # setcap cap_net_bind_service=+ep /usr/bin/rootlesskit
 #
-# To access local services take the hostname directly, maybe define it static and add it to /etc/hosts
+# To access local services, take the hostname directly, maybe define it static and add it to /etc/hosts on the host
-# Mind, that the port must be pubilshed by the other containers to the host via ports or expose, or add them to the network
+# Mind, that the ports must be pubilshed by the other containers to the host via ports or expose, or add them to the network
-# e.g. pcserver:9000 !!! NOT !!! localhost:9000 - this is prevented by docker in rootless- mode !
+# e.g. pcserver:9000 !!! NOT: !!! localhost:9000 - this is prevented by docker in rootless- mode !
-    network_mode: "host"
+#Do NOT use networkmode: "host", this will fail (Acme: Connection refused)!
-#    ports:
+#    network_mode: "host"
-#      - "80:80"
+    ports:
-#      - "443:443"
+      - "80:80"
-#      - "443:443/udp"
+      - "443:443"
+      - "443:443/udp"
 volumes:
   caddy_data:
-    driver: local
-    driver_opts:
-      device: ""
-      type: ""
-      o: "umask=0007"
   caddy_config:
-    driver: local
-    driver_opts:
-      device: ""
-      type: ""
-      o: "umask=0007"
   caddy_certs:
-    driver: local
-    driver_opts:
-      device: ""
-      type: ""
-      o: "umask=0007"
   caddy_sites:
-    driver: local
-    driver_opts:
+networks:
-      device: ""
+# Still needs to be defined while without it won't enable ipv6
-      type: ""
+  default:
-      o: "umask=0007"
+    driver: bridge
+    enable_ipv6: true
 </file>
-Also, check that your Firewall has those Ports open on your hosts and that Port Forwarding in your Router is enabled for ipv4 and for ipv6 that the host+ports are not blocked.
+Also, check that your Firewall has those Port 80 + 443 open on your host and that Port Forwarding in your Router is enabled for ipv4 and for ipv6.
@@ Zeile 107: / Zeile 80: @@
 if you omit the Caddyfile, the server will already work, but we can directly Skip those tests and create the file ''Caddyfile'' in that folder too with the following content:
 <file>
 https://portainer.my.domain.tld:443 {
         header Strict-Transport-Security max-age=31536000;
@@ Zeile 114: / Zeile 88: @@
 </file>
-replace mylocalhostname with your actual hostname (can be found out by calling hostname in your terminal).
+replace //mylocalhostname// with your actual hostname (can be found out by calling hostname in your terminal).
 Don't use localhost - see above. If you do not have a clue which hostname you have, better specify some fixed one which you can freely chose and edit ''/etc/hosts'' to have that name point to your local ip.
@@ Zeile 121: / Zeile 95: @@
 Thats all - use ''docker-compose up -d'' to start your container. In the Container- Logs you will see Caddy automagically create SSL- Certificates from lets encrypt if everything was setup the right way. Caddy will take care of renewal without the need to configure anything.
-You now have a powerful proxy, that can transparently deliver your Dockers to the world with SSL- encryption enabled.
+If the Caddy doe not return any Errors, you now have a powerful proxy, that can transparently deliver your Dockers to the world with SSL- encryption enabled.