Trying to reverse proxy to my domain with caddy - Help - Caddy Community = 40rem)" rel="stylesheet" data-target="chat_desktop" /> = 40rem)" rel="stylesheet" data-target="discourse-reactions_desktop" /> = 40rem)" rel="stylesheet" data-target="poll_desktop" /> = 40rem)" rel="stylesheet" data-target="desktop_theme" data-theme-id="1" data-theme-name="caddy custom"/> Trying to reverse proxy to my domain with caddy Help SYMON (Sidney) August 9, 2026, 9:48pm 1 1. The problem I’m having: I'm trying to set up a reverse proxy using Caddy to forward HTTPS requests for tagged.website to Modlishka running on 127.0.0.1:8081. Modlishka is successfully running and configured to proxy to tagged.com, but Caddy is failing to start with a TLS configuration error. The goal is to have tagged.website serve as a phishing proxy for tagged.com. 2. Error messages and/or full log output: × caddy.service - Caddy Loaded: loaded (/usr/lib/systemd/system/caddy.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sun 2026-08-09 21:09:02 UTC; 1min 0s ago Duration: 1d 21h 24min 18.747s Docs: Welcome — Caddy Documentation Process: 318373 ExecStart=/usr/bin/caddy run --environ --config /etc/caddy/Caddyfile (code=exited, status=1/FAILURE) Main PID: 318373 (code=exited, status=1/FAILURE) Status: "loading new config: loading http app module: provision http: getting tls app: loading tls app module: provision> CPU: 41ms 3. Caddy version: 2.6.2 4. How I installed and ran Caddy: sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg echo "deb [signed-by=/usr/share/keyrings/caddy-stable-archive-keyring.gpg] https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version main" | sudo tee /etc/apt/sources.list.d/caddy-stable.list # Update and install Caddy a. System environment: a. System environment: . System environment: - OS: Linux (CloudVPS) - Architecture: amd64 - Running via systemd b. Command: PASTE OVER THIS HERE IN THIS CODE BLOCK. Please ensure it looks nice. c. Service/unit/compose file: PASTE OVER THIS HERE IN THIS CODE BLOCK. Please ensure it looks nice. d. My complete Caddy config: { auto_https off } tagged.website:443 { reverse_proxy 127.0.0.1:8081 tls /etc/letsencrypt/live/tagged.website/fullchain.pem /etc/letsencrypt/live/tagged.website/privkey.pem } 5. Links to relevant resources: Type here francislavoie (Francis Lavoie) August 10, 2026, 4:03am 2 This is a mismatch. v2.6.2 is extremely old and unsupported. I don’t think you actually ran those install steps, if you did you would have 2.11.4 SYMON (Sidney) August 10, 2026, 11:25pm 3 v2.11.4 is my current version This is what I ran sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https curl -1sLf ‘https://dl.cloudsmith.io/public/caddy/stable/gpg.key’ | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg echo “deb [signed-by=/usr/share/keyrings/caddy-stable-archive-keyring.gpg] https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version main” | sudo tee /etc/apt/sources.list.d/caddy-stable.list sudo apt update sudo apt install caddy The issue I’m encountering now is that when I click on my domain, it redirects to the original website instead of serving the proxied version. It appears that the domain is not being proxied as intended. SYMON (Sidney) August 10, 2026, 11:35pm 4 root@CloudVPS117483:~/Modlishka# curl -I http://127.0.0.1:8081 HTTP/1.1 302 Found Content-Type: text/html; charset=utf-8 Location: http://https://tagged.com Date: Mon, 10 Aug 2026 23:33:59 GMT root@CloudVPS117483:~/Modlishka# curl -I https://tagged.website HTTP/2 200 alt-svc: h3=“:443”; ma=2592000 date: Mon, 10 Aug 2026 23:34:14 GMT via: 1.1 Caddy I think I need to start here