Caddy fails to start activating privacy features unexpected end of JSON input

Seeing the following error in /var/log/syslog:

Apr 15 18:31:28 ip-172-31-26-148 caddy[25722]: Activating privacy features… 2018/04/15 18:31:28 unexpected end of JSON input

We are using On-Demand TLS with the ask directive. Any ideas? Thankfully we have two nodes and the other is running which is strange because they share a common NFS share for CADDYPATH.

Nevermind, somehow AWS EFS unmounted itself on that instance. Sigh!

Would be awesome is Caddy logged which json file it failed reading.

Glad you figured it out. I think that depends on lumberjack, which manages the log files for Caddy. Might be a request for enhancement on lumberjack! But I’m mobile and going off memory.

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