1. My Caddy version (caddy -version
):
v2.0.0-beta11 h1:NVHnPAdZPt6OUBMltUMe2DWVsyYRbeE6NxhCm3AjGT8=
2. How I run Caddy:
a. System environment:
Windows 10
b. Command:
caddy2_beta11_windows_amd64.exe start
c. My complete Caddyfile:
{
"apps": {
"http": {
"servers": {
"srv0": {
"listen": [
":2019"
],
"routes": [
{
"handle": [
{
"handler": "subroute",
"routes": [
{
"handle": [
{
"handler": "rewrite",
"rehandle": false,
"strip_path_prefix": "/docker"
},
{
"handler": "reverse_proxy",
"transport": {
"protocol": "http",
"read_buffer_size": 4096,
"tls": {
"insecure_skip_verify": true
}
},
"upstreams": [
{
"dial": "localhost:32773"
}
]
}
],
"match": [
{
"path": [
"/docker"
]
}
]
},
{
"handle": [
{
"handler": "reverse_proxy",
"transport": {
"protocol": "http",
"read_buffer_size": 4096
},
"upstreams": [
{
"dial": "192.168.*.*:17185"
}
]
}
],
"match": [
{
"path": [
"/"
]
}
]
}
]
}
]
}
]
}
}
}
}
}
3. The problem I’m having:
I would like to run the caddy 2 and admin endpoints both on the same port i.e 2019. The behaviour what is happening currently with the above caddy file is reverse-proxy is working fine but admin endpoints are not working as a result reload, config list and load is not working. If there is a way this can be handled.