Fresh install -> Demo doesn't work
austingreisman opened this issue · 5 comments
Problem/Motivation
Demo example does not work.
Expected behavior
Simple HTTP Proxy host works when clicked.
Actual behavior
This site can’t be reached. "DNS_PROBE_FINISHED_NXDOMAIN"
FROM
2024/03/23 14:05:21 [error] 284#284: *57 upstream prematurely closed connection while reading response header from upstream, client: 172.30.32.1, server: nginxproxymanager, request: "GET /api/nginx/certificates/test-http?domains=%5B%2210.0.0.35%22%5D HTTP/1.1", upstream: "http://127.0.0.1:3000/nginx/certificates/test-http?domains=%5B%2210.0.0.35%22%5D", host: "homeassistant.local:81", referrer: "http://homeassistant.local:81/nginx/certificates"
JSON.parse (<anonymous>)IncomingMessage.<anonymous> (/opt/nginx-proxy-manager/internal/certificate.js:1178:31)IncomingMessage.emit (node:events:529:35)endReadableNT (node:internal/streams/readable:1400:12)process.processTicksAndRejections (node:internal/process/task_queues:82:21)[14:05:21] INFO: Service Nginx Proxy Manager exited with code 256 (by signal 5)
[14:05:22] INFO: Starting the Manager...
[3/23/2024] [2:05:23 PM] [Global ] › ℹ info Using Sqlite: /config/database.sqlite
[3/23/2024] [2:05:23 PM] [Migrate ] › ℹ info Current database version: none
[3/23/2024] [2:05:23 PM] [Setup ] › ℹ info Logrotate Timer initialized
[3/23/2024] [2:05:23 PM] [Setup ] › ℹ info Logrotate completed.
[3/23/2024] [2:05:23 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services...
[3/23/2024] [2:05:23 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[3/23/2024] [2:05:24 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4
[3/23/2024] [2:05:24 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6
[3/23/2024] [2:05:25 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized
[3/23/2024] [2:05:25 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[3/23/2024] [2:05:25 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized
[3/23/2024] [2:05:25 PM] [Global ] › ℹ info Backend PID 295 listening on port 3000 ...
[3/23/2024] [2:05:25 PM] [Nginx ] › ℹ info Reloading Nginx
[3/23/2024] [2:05:25 PM] [SSL ] › ℹ info Renew Complete
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
[3/23/2024] [2:06:02 PM] [Nginx ] › ⬤ debug Deleting file: /config/nginx/proxy_host/1.conf
[3/23/2024] [2:06:02 PM] [Nginx ] › ℹ info Reloading Nginx
[3/23/2024] [2:07:49 PM] [Nginx ] › ⬤ debug Deleting file: /config/nginx/proxy_host/1.conf
[3/23/2024] [2:07:49 PM] [Nginx ] › ℹ info Reloading Nginx
[3/23/2024] [2:08:32 PM] [Nginx ] › ⬤ debug Deleting file: /config/nginx/proxy_host/2.conf
[3/23/2024] [2:08:32 PM] [Nginx ] › ⬤ debug Could not delete file: {
"errno": -2,
"syscall": "unlink",
"code": "ENOENT",
"path": "/config/nginx/proxy_host/2.conf"
}
[3/23/2024] [2:08:32 PM] [Nginx ] › ℹ info Reloading Nginx
[3/23/2024] [2:17:06 PM] [Nginx ] › ⬤ debug Deleting file: /config/nginx/proxy_host/2.conf
[3/23/2024] [2:17:06 PM] [Nginx ] › ℹ info Reloading Nginx
Steps to reproduce
Follow GIF demo.
Proposed changes
Unknown. Don't know enough about the backend.
Can you confirm if you used "homeassistant" or "homeassistant.local"?
I used "homeassistant" also the static IP as an attempt
Then please post the full startup logs for the addon, including your configuration.
I should add, DNS_PROBE_FINISHED_NXDOMAIN would suggest that your DNS server cannot resolve whatever you are accessing on.
I'll be away from my server for a week, so I will post this when I have access again
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!