Activating privacy features… done.
https://:2002
https://:2002/resources
WARNING: File descriptor limit 4864 is too low for production servers. At least 8192 is recommended. Fix with “ulimit -n 8192”.
Displaying https://localhost:2002 in chrome results in:
This site can’t provide a secure connection
localhost sent an invalid response.
ERR_SSL_PROTOCOL_ERROR
I’m hardly an expert in this area. Can anyone tell me what the missing piece is here?
As of the latest release (0.11.5), trying to use tls self_signed without a hostname should return an error self-signed: certificate has no names. Caddy no longer serves a certificate at all if no certificate matches the hostname indicated via SNI.
You should be able to use localhost:2002 with tls self_signed for now, if you’re browsing to https://localhost:2002 in your browser.
There’s a PR in the works to have self-signed certificates automaticaly fetch all interfaces for SANs when the hostname is omitted. That should allow for :2002 to be used with the hostname omitted and still be accessible via localhost or any local IP address.