Caddy: Difference between revisions
imported>Malteneuss Add debugging section |
imported>Malteneuss m Add debug subsections |
||
| Line 96: | Line 96: | ||
== Debugging == | == Debugging == | ||
=== Check used ports === | |||
To check if Caddy is running and listening as configured you can run netstat: | To check if Caddy is running and listening as configured you can run netstat: | ||
| Line 109: | Line 110: | ||
The tcp (ipv4) socket port 2019 is Caddy's management endpoint, for when you want manage its config via web REST calls instead of Nix (ignore). | The tcp (ipv4) socket port 2019 is Caddy's management endpoint, for when you want manage its config via web REST calls instead of Nix (ignore). | ||
The tcp6 (an ipv6 socket that also listens on ipv4) socket on port 80 (HTTP) and 443 (HTTPS) indicate that a virtualhost config was used. | The tcp6 (an ipv6 socket that also listens on ipv4) socket on port 80 (HTTP) and 443 (HTTPS) indicate that a virtualhost config was used. | ||
=== Check connections === | |||
You can also use curl to test http(s) calls. However, you must set the "Host" header correctly when testing locally: | You can also use curl to test http(s) calls. However, you must set the "Host" header correctly when testing locally: | ||