1. Which version of Caddy are you using ( caddy -version )?
Caddy 0.11.5
2. What are you trying to do?
after update to 0.11.5 1 site still working, 2 site get error
3. What is your Caddyfile?
site.com {
root /var/www/html/site
tls {
dns cloudflare
}
log /var/log/caddy/site.log
errors /var/log/caddy/site_errors.log
gzip
# PHP-FPM Configuration for Caddy
fastcgi / /run/php/php7.2-fpm.sock php {
ext .php
split .php
index index.php
}
rewrite {
if {path} not_match ^\/wp-admin
to {path} {path}/ /index.php?_url={uri}
}
}
4. How did you run Caddy (give the full command and describe the execution environment)?
install from “One-step installer script”
5. Please paste any relevant HTTP request(s) here.
curl -Iv https://site.com/
* Trying xxx.xxx.xxx.200...
* TCP_NODELAY set
* Connected to rsite.com (xxx.xxx.xxx.200) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=site.com
* start date: Mar 20 08:35:46 2019 GMT
* expire date: Jun 18 08:35:46 2019 GMT
* subjectAltName: host "site.com" matched cert's "site.com"
* issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55e01b030840)
> HEAD / HTTP/2
> Host: site.com
> User-Agent: curl/7.58.0
> Accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 500
HTTP/2 500
< content-type: text/html; charset=UTF-8
content-type: text/html; charset=UTF-8
< server: Caddy
server: Caddy
< status: 500 Internal Server Error
status: 500 Internal Server Error
< date: Wed, 20 Mar 2019 09:53:15 GMT
date: Wed, 20 Mar 2019 09:53:15 GMT
6. What did you expect to see?
worked site
7. What did you see instead (give full error messages and/or log)?
2001:xxx:xxxx:xxx:440b:a8ff:fe49:2d01 - - [20/Mar/2019:21:22:16 +0300] "GET / HTTP/2.0" 500 23
xxx.xxx.xxx.108 - - [21/Mar/2019:01:29:52 +0300] "GET / HTTP/1.1" 500 23
8. Why is this a bug, and how do you think this should be fixed?
9. What are you doing to work around the problem in the meantime?
10. Please link to any related issues, pull requests, and/or discussion.
Bonus: What do you use Caddy for? Why did you choose Caddy?
test dev