Hi everyone,
I’m new to the networking field as well as caddy. I tried to setup caddy -quic server on one Linux computer (Ubuntu 16.04.3 LTS) and then using chrome on other linux to access to the caddy server on the first computer. At the same time I tried to use Wireshark to capture packets which use QUIC protocol.
Here is the Caddyfile on the first computer, I’m using caddy v1.0.0 :
emuquic.com:443
{
tls {
max_certs 10
}
}
when I type ‘’ caddy-quic" I got this on terminal:
**Dispelk9@server** : **~** $ caddy -quic
Activating privacy features... done.
Serving HTTP on port 80
http://emuquic.com
Serving HTTPS on port 443
https://emuquic.com
When I tried to connect using Chrome on the second computer. It shows that this site cannot be reached (ERR_NAME_NOT_RESOLVED) on tab emuquic.com
and
this site cannot be reached (DNS_PROBE_FINISHED_NXDOMAIN) on tab https://emuquic.com
max_cert tells Caddy to requisition valid certificates from LetsEncrypt whenever someone tries to connect. This is the On-Demand TLS feature. It still requires a valid domain name. It works exactly like regular managed TLS, it just delays the certificate acquisition until client connections come in.
QUIC requires a valid domain name, SNI, and a valid certificate (i.e. not self-signed). You need to get a real domain and point it at your server.