Unexpected end of JSON input

1. Which version of Caddy are you using (caddy -version)?

Caddy 0.11.4 (non-commercial use only)

2. What are you trying to do?

Running behind a Caddy Reverse Proxy with Free SSL

3. What is your Caddyfile?

[Unit]
Description=Caddy HTTP/2 web server
Documentation=https://caddyserver.com/docs
After=network-online.target
Wants=network-online.target
[Service]
Restart=on-failure
StartLimitInterval=86400
StartLimitBurst=5000
User=www-data
Group=www-data
; Letsencrypt-issued certificates will be written to here in this directory
Environment=CADDYPATH=/etc/ssl/caddy
ExecStart=/usr/local/bin/caddy -log stdout -agree=true -conf=/etc/caddy/Caddyfile -root=/var/tmp
ExecReload=/bin/kill -USR1 $MAINPID
LimitNOFILE=1048576
LimitNPROC=64
PrivateTmp=true
PrivateDevices=true
ProtectHome=true
ProtectSystem=full
ReadWriteDirectories=/etc/ssl/caddy
; The following additional security directives only work with systemd v229 or later.
; They further restrict privileges that can be gained by caddy. Uncomment if you want.
; You may need to add capabilities required by the plugins in use.
;CapabilityBoundingSet=CAP_NET_BIND_SERVICE
;AmbientCapabilities=CAP_NET_BIND_SERVICE
;NoNewPrivileges=true
[Install]
WantedBy=multi-user.target

6. What did you expect to see?

Successfully running caddy service then acquire let’s encrypt

7. What did you see instead (give full error messages and/or log)?

Email address: 2019/02/27 17:09:44 decoding certificate metadata: unexpected end of JSON input
caddy.service: Main process exited, code=exited, status=1/FAILURE
caddy.service: Failed with result 'exit-code'.

it never asks for my email by the way

8. Why is this a bug, and how do you think this should be fixed?

It’s a fresh install of ubuntu 18.04 and caddy. I’m trying to run a Rocket.Chat server on my server with https. Server is running fine locally, my domain is pointing to my server, ports are good but stucked at this errors

Caddyfile

mydomain {
	proxy / 127.0.0.1:3000 {
		header_upstream X-Forwarded-Proto {scheme}
                header_upstream X-Forwarded-For {host}
                header_upstream Host {host}
                websocket
        }
}

Thanks

Looks like it can’t read a saved certificate json file. Did you do any hand editing of the certs in your CADDYPATH?

You could try deleting or renaming the .caddy folder in CADDYPATH and give it another shot?

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