1. Caddy version (caddy version):
v2.4.6
2. How I run Caddy:
a. System environment:
WSL 1, Ubuntu-20.04
b. Command:
sudo caddy run
c. Service/unit/compose file:
Paste full file contents here.
Make sure backticks stay on their own lines,
and the post looks nice in the preview pane.
d. My complete Caddyfile or JSON config:
duckwithdafro.bulbe.rocks {
reverse_proxy /api* 192.198.1.59:9000
reverse_proxy 192.168.1.59:8080
}
http://192.168.1.59:80 {
reverse_proxy /api* 192.198.1.59:9000
reverse_proxy 192.168.1.59:8080
}
3. The problem I’m having:
i am not getting any response from caddy, like the title says, and evident by curl:
Myuser@MY-COMPUTER:/mnt/c/Users/myuser$ curl -v http://192.168.1.59
* Trying 192.168.1.59:80...
* TCP_NODELAY set
* Connected to 192.168.1.59 (192.168.1.59) port 80 (#0)
> GET / HTTP/1.1
> Host: 192.168.1.59
> User-Agent: curl/7.68.0
> Accept: */*
>
* Empty reply from server
* Connection #0 to host 192.168.1.59 left intact
curl: (52) Empty reply from server
Myuser@MY-COMPUTER:/mnt/c/Users/myuser$ curl -v http://192.168.1.59/api
* Trying 192.168.1.59:80...
* TCP_NODELAY set
* Connected to 192.168.1.59 (192.168.1.59) port 80 (#0)
> GET /api HTTP/1.1
> Host: 192.168.1.59
> User-Agent: curl/7.68.0
> Accept: */*
>
* Empty reply from server
* Connection #0 to host 192.168.1.59 left intact
curl: (52) Empty reply from server
4. Error messages and/or full log output:
$ sudo caddy run
2022/02/25 00:48:36.970 INFO using adjacent Caddyfile
2022/02/25 00:48:36.971 WARN input is not formatted with 'caddy fmt' {"adapter": "caddyfile", "file": "Caddyfile", "line": 2}
2022/02/25 00:48:36.973 INFO admin admin endpoint started {"address": "tcp/localhost:2019", "enforce_origin": false, "origins": ["localhost:2019", "[::1]:2019", "127.0.0.1:2019"]}
2022/02/25 00:48:36.973 INFO http server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS {"server_name": "srv0", "https_port": 443}
2022/02/25 00:48:36.973 INFO http enabling automatic HTTP->HTTPS redirects {"server_name": "srv0"}
2022/02/25 00:48:36.973 INFO http server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server {"server_name": "srv1", "http_port": 80}
2022/02/25 00:48:36.973 INFO tls cleaning storage unit {"description": "FileStorage:/root/.local/share/caddy"}
2022/02/25 00:48:36.973 INFO tls.cache.maintenance started background certificate maintenance {"cache": "0xc00032c7e0"}
2022/02/25 00:48:36.973 DEBUG http starting server loop {"address": "[::]:443", "http3": false, "tls": true}
2022/02/25 00:48:36.974 DEBUG http starting server loop {"address": "[::]:80", "http3": false, "tls": false}
2022/02/25 00:48:36.974 INFO http enabling automatic TLS certificate management {"domains": ["duckwithdafro.bulbe.rocks"]}
2022/02/25 00:48:36.974 DEBUG tls loading managed certificate {"domain": "duckwithdafro.bulbe.rocks", "expiration": "2022/05/24 23:10:49.000", "issuer_key": "acme-v02.api.letsencrypt.org-directory", "storage": "FileStorage:/root/.local/share/caddy"}
2022/02/25 00:48:36.974 INFO tls finished cleaning storage units
2022/02/25 00:48:36.975 DEBUG tls.cache added certificate to cache {"subjects": ["duckwithdafro.bulbe.rocks"], "expiration": "2022/05/24 23:10:49.000", "managed": true, "issuer_key": "acme-v02.api.letsencrypt.org-directory", "hash": "removing this to be safe", "cache_size": 1, "cache_capacity": 10000}
2022/02/25 00:48:36.975 INFO autosaved config (load with --resume flag) {"file": "/root/.config/caddy/autosave.json"}
2022/02/25 00:48:36.975 INFO serving initial configuration
5. What I already tried:
at first some services couldn’t get to my computer, so i turned off windows firewall. it fixed that issue but now this issue is here.
additional info: i am not using docker, and the reason for http://192.168.1.59 is because its a work around for me not being able to access duckwithdafro.bulbe.rocks and i am currently self-hosting this and in my apps running it shows no signs of any request being made to it.
