2017/06/11 08:55:46 http: TLS handshake error from 14.153.125.238:51203: tls: client offered an unsupported, maximum protocol version of 301
2017/06/11 09:04:44 http2: server: error reading preface from client 1.12.158.135:37804: timeout waiting for client preface
2017/06/11 09:13:45 http: TLS handshake error from 151.255.15.161:5987: EOF
2017/06/11 09:20:20 [INFO] SIGHUP: Hanging up
2017/06/11 09:20:20 http: Server closed
2017/06/11 09:20:20 http: Server closed
2017/06/11 09:20:21 http: Server closed
Hi @polaris1119,
Looks like Caddy received a SIGHUP signal.
Almost any number of circumstances could have resulted in Caddy receiving a SIGHUP. It’s entirely dependant on the environment and method you use to run Caddy.
One common reason is if you run Caddy in a terminal window and then close the window, it will send a SIGHUP.
Matthew’s right, something in your system is sending SIGHUP. You can absorb that by running Caddy with nohup.
Thank you!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.