1. My Caddy version (caddy version
):
Version 2
2. How I run Caddy:
caddy.exe start
a. System environment:
Windows 10, No Docker
d. My complete Caddyfile or JSON config:
{
# email to use on Let's Encrypt
email bla
# Uncomment for debug
#acme_ca https://acme-staging-v02.api.letsencrypt.org/directory
#debug
}
# Add gzip compression to requests
(webconf) {
encode gzip
}
# Add forward headers to requests
(theheaders) {
header_up X-Forwarded-Ssl on
header_up Host {host}
header_up X-Real-IP {remote}
header_up X-Forwarded-For {remote}
header_up X-Forwarded-Port {server_port}
header_up X-Forwarded-Proto {scheme}
header_up X-Url-Scheme {scheme}
header_up X-Forwarded-Host {host}
}
example.com, www.example.com {
root * /www/
file_server
import webconf
}
jenkins.example.com {
reverse_proxy http://127.0.0.1:9080 {
import theheaders
}
import webconf
}
3. The problem I’m having:
Caddy could not start because it can not bind port 2019, which is not in use.
4. Error messages and/or full log output:
2020/05/05 09:26:28.881 e[34mINFOe[0m using adjacent Caddyfile
run: loading initial config: loading new config: starting caddy administration endpoint: listen tcp 127.0.0.1:2019: bind: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.
start: caddy process exited with error: exit status 1
5. What I already tried:
Use Adminmode