You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
4. How did you run Caddy (give the full command and describe the execution environment)?
With command: caddy -conf caddy.conf
5. Please paste any relevant HTTP request(s) here.
Tried in Chrome and Firefox: https://localhost and https://192.168.0.15
6. What did you expect to see?
Static website served for both requests.
7. What did you see instead (give full error messages and/or log)?
https://localhost works just fine, but https://192.168.0.15 results in ERR_SSL_PROTOCOL_ERROR for Chrome and for Firefox in:
An error occurred during a connection to 192.168.0.15. Peer reports it experienced an internal error.
Error code: SSL_ERROR_INTERNAL_ERROR_ALERT
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
8. How can someone who is starting from scratch reproduce the bug as minimally as possible?
I generated self-signed certificates with help of mkcert. And the point is that I've also tried to serve the same website with http-server (based on NodeJS) server with the following command (by default it serves from all available interfaces, thus on localhost and 192.168.0.15 included):
And it worked well for both requests (localhost and 192.168.0.15). That's why I thought that it might be a bug in Caddy and I haven't found anything related to this bug.
The text was updated successfully, but these errors were encountered:
1. What version of Caddy are you using (
caddy -version
)?Caddy 0.11.1
2. What are you trying to do?
Serve a static website on
https://localhost:443
andhttps://192.168.0.15:443
.3. What is your entire Caddyfile?
4. How did you run Caddy (give the full command and describe the execution environment)?
With command:
caddy -conf caddy.conf
5. Please paste any relevant HTTP request(s) here.
Tried in Chrome and Firefox:
https://localhost
andhttps://192.168.0.15
6. What did you expect to see?
Static website served for both requests.
7. What did you see instead (give full error messages and/or log)?
https://localhost
works just fine, buthttps://192.168.0.15
results in ERR_SSL_PROTOCOL_ERROR for Chrome and for Firefox in:8. How can someone who is starting from scratch reproduce the bug as minimally as possible?
I generated self-signed certificates with help of mkcert. And the point is that I've also tried to serve the same website with
http-server
(based on NodeJS) server with the following command (by default it serves from all available interfaces, thus on localhost and 192.168.0.15 included):And it worked well for both requests (localhost and 192.168.0.15). That's why I thought that it might be a bug in Caddy and I haven't found anything related to this bug.
The text was updated successfully, but these errors were encountered: