Error: adapting config using caddyfile: parsing caddyfile tokens for 'tls': wrong argument count or unexpected line ending after {mysecrettoken}

Help
1

1. The problem I’m having:

I am trying to set up a Plex reverse proxy using desec.io as a dynamic DNS.

2. Error messages and/or full log output:

-- Boot 759b62feea424b7583d615407fd56faa --
Nov 18 21:47:35 caddy systemd[1]: Starting caddy.service - Caddy...
Nov 18 21:47:35 caddy caddy[135]: {"level":"info","ts":1763524055.4541254,"msg":"maxprocs: Leaving GOMAXPROCS=1: CPU quota undefined"}
Nov 18 21:47:35 caddy caddy[135]: {"level":"info","ts":1763524055.4552145,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":14795746099,"previous":9223372036854775807}
Nov 18 21:47:35 caddy caddy[135]: caddy.HomeDir=/var/lib/caddy
Nov 18 21:47:35 caddy caddy[135]: caddy.AppDataDir=/var/lib/caddy/.local/share/caddy
Nov 18 21:47:35 caddy caddy[135]: caddy.AppConfigDir=/var/lib/caddy/.config/caddy
Nov 18 21:47:35 caddy caddy[135]: caddy.ConfigAutosavePath=/var/lib/caddy/.config/caddy/autosave.json
Nov 18 21:47:35 caddy caddy[135]: caddy.Version=v2.10.2 h1:g/gTYjGMD0dec+UgMw8SnfmJ3I9+M2TdvoRL/Ovu6U8=
Nov 18 21:47:35 caddy caddy[135]: runtime.GOOS=linux
Nov 18 21:47:35 caddy caddy[135]: runtime.GOARCH=amd64
Nov 18 21:47:35 caddy caddy[135]: runtime.Compiler=gc
Nov 18 21:47:35 caddy caddy[135]: runtime.NumCPU=1
Nov 18 21:47:35 caddy caddy[135]: runtime.GOMAXPROCS=1
Nov 18 21:47:35 caddy caddy[135]: runtime.Version=go1.25.4
Nov 18 21:47:35 caddy caddy[135]: os.Getwd=/
Nov 18 21:47:35 caddy caddy[135]: LANG=en_US.UTF-8
Nov 18 21:47:35 caddy caddy[135]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Nov 18 21:47:35 caddy caddy[135]: NOTIFY_SOCKET=/run/systemd/notify
Nov 18 21:47:35 caddy caddy[135]: HOME=/var/lib/caddy
Nov 18 21:47:35 caddy caddy[135]: LOGNAME=caddy
Nov 18 21:47:35 caddy caddy[135]: USER=caddy
Nov 18 21:47:35 caddy caddy[135]: INVOCATION_ID=82207eba818346a78d0d78054cbdfd0c
Nov 18 21:47:35 caddy caddy[135]: JOURNAL_STREAM=9:13331276
Nov 18 21:47:35 caddy caddy[135]: SYSTEMD_EXEC_PID=135
Nov 18 21:47:35 caddy caddy[135]: {"level":"info","ts":1763524055.4570298,"msg":"using config from file","file":"/etc/caddy/Caddyfile"}
Nov 18 21:47:35 caddy caddy[135]: {"level":"info","ts":1763524055.457576,"msg":"maxprocs: No GOMAXPROCS change to reset"}
Nov 18 21:47:35 caddy caddy[135]: Error: adapting config using caddyfile: parsing caddyfile tokens for 'tls': wrong argument count or unexpected line ending after '{mysecrettoken}', at /etc/caddy/Caddyfile:8
Nov 18 21:47:35 caddy systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE
Nov 18 21:47:35 caddy systemd[1]: caddy.service: Failed with result 'exit-code'.
Nov 18 21:47:35 caddy systemd[1]: Failed to start caddy.service - Caddy.

3. Caddy version:

v2.10.2 h1:g/gTYjGMD0dec+UgMw8SnfmJ3I9+M2TdvoRL/Ovu6U8=

4. How I installed and ran Caddy:

Caddy has been installed on Proxmox 9 using: Proxmox VE Helper-Scripts

a. System environment:

Proxmox 9

b. Command:

xcaddy build --with github.com/caddy-dns/desec
cp caddy /usr/bin/

d. My complete Caddy config:

{
        debug
}       

plex.friesen.dedyn.io {
    reverse_proxy 192.168.1.12:32400
    tls {
        dns desec {myscrettoken}
    }
}

5. Links to relevant resources:

2

Check the README of the desec module. This is how they expect it to be configured:

tls {
	dns desec {
		token "YOUR_TOKEN"
	}
}
2 Likes
3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.