I followed this guide previously and was able to access homeassistant securely on my local network with the domain xyz.duckdns.org
what should I do to correct this issue?
. A screenshot from my previous setup
I had an issue with HA and had to restore from a backup but somehow my settings weren’t preserved.
I followed the guide again but cannot access the homeassistant using Duckdns on the local network.
configuration.yaml
http:
use_x_forwarded_for: true
trusted_proxies:
- 172.30.0.0/16
status of NPM
NPM logs
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun manager (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
s6-rc: info: service legacy-services successfully started
[11/29/2023] [10:29:55 AM] [Global ] › ℹ info Manual db configuration already exists, skipping config creation from environment variables
[11/29/2023] [10:30:01 AM] [Migrate ] › ℹ info Current database version: 20211108145214
[11/29/2023] [10:30:28 AM] [Setup ] › ℹ info Added Certbot plugins certbot-dns-duckdns~=0.9
[11/29/2023] [10:30:28 AM] [Setup ] › ℹ info Logrotate Timer initialized
[11/29/2023] [10:30:28 AM] [Setup ] › ℹ info Logrotate completed.
[11/29/2023] [10:30:28 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services...
[11/29/2023] [10:30:28 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
2023/11/29 10:30:28 [error] 296#296: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.18.126, server: nginxproxymanager, request: "POST /api/tokens HTTP/1.1", upstream: "http://127.0.0.1:3000/tokens", host: "homeassistant.local:81", referrer: "http://homeassistant.local:81/login"
[11/29/2023] [10:30:29 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4
[11/29/2023] [10:30:29 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6
[11/29/2023] [10:30:29 AM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized
[11/29/2023] [10:30:29 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[11/29/2023] [10:30:29 AM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized
[11/29/2023] [10:30:29 AM] [Global ] › ℹ info Backend PID 276 listening on port 3000 ...
`QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
`QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0
QueryBuilder#omit is deprecated. This method will be removed in version 3.0
Model#$omit is deprected and will be removed in 3.0.
[11/29/2023] [10:31:41 AM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
Failed to renew certificate npm-2 with error: File not found: /etc/letsencrypt/credentials/credentials-2
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/npm-2/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
at ChildProcess.exithandler (node:child_process:400:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1093:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0
[11/29/2023] [10:45:17 AM] [Nginx ] › ℹ info Reloading Nginx