1. Caddy version (caddy version):
latest
2. How I run Caddy:
home.howardgb.com {
reverse_proxy /pihole* 10.0.0.2:8013
}
a. System environment:
PRETTY_NAME=“Raspbian GNU/Linux 9 (stretch)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“9”
VERSION=“9 (stretch)”
VERSION_CODENAME=stretch
ID=raspbian
ID_LIKE=debian
b. Command:
caddy run -config /home/pi/Caddyfile
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:
home.howardgb.com {
reverse_proxy /pihole* 10.0.0.2:8013
}
3. The problem I’m having:
When I run caddy I get this error:
ERROR: ld.so: object ‘/usr/lib/arm-linux-gnueabihf/libarmmem.so’ from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
2021/12/06 19:48:19.667 INFO using provided configuration {“config_file”: “/home/pi/Caddyfile”, “config_adapter”: “”}
2021/12/06 19:48:19.728 INFO admin admin endpoint started {“address”: “tcp/localhost:2019”, “enforce_origin”: false, “origins”: [“localhost:2019”, “[::1]:2019”, “127.0.0.1:2019”]}
2021/12/06 19:48:19.730 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}
2021/12/06 19:48:19.730 INFO tls.cache.maintenance started background certificate maintenance {“cache”: “0x2e380a0”}
2021/12/06 19:48:19.730 INFO http enabling automatic HTTP->HTTPS redirects {“server_name”: “srv0”}
2021/12/06 19:48:19.733 INFO tls.cache.maintenance stopped background certificate maintenance {“cache”: “0x2e380a0”}
run: loading initial config: loading new config: http app module: start: tcp: listening on :443: listen tcp :443: bind: permission denied
4. Error messages and/or full log output:
ERROR: ld.so: object ‘/usr/lib/arm-linux-gnueabihf/libarmmem.so’ from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
2021/12/06 19:48:19.667 INFO using provided configuration {“config_file”: “/home/pi/Caddyfile”, “config_adapter”: “”}
2021/12/06 19:48:19.728 INFO admin admin endpoint started {“address”: “tcp/localhost:2019”, “enforce_origin”: false, “origins”: [“localhost:2019”, “[::1]:2019”, “127.0.0.1:2019”]}
2021/12/06 19:48:19.730 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}
2021/12/06 19:48:19.730 INFO tls.cache.maintenance started background certificate maintenance {“cache”: “0x2e380a0”}
2021/12/06 19:48:19.730 INFO http enabling automatic HTTP->HTTPS redirects {“server_name”: “srv0”}
2021/12/06 19:48:19.733 INFO tls.cache.maintenance stopped background certificate maintenance {“cache”: “0x2e380a0”}
run: loading initial config: loading new config: http app module: start: tcp: listening on :443: listen tcp :443: bind: permission denied
5. What I already tried:
I’ve tried running sudo netstat -tulpn | grep 443. to see if anything is using port 443 but nothing is