January 17Jan 17 I am getting errors for 2 domains. The containers behind them are no longer running. The certs have also expired.I posted a support ticket on the Lets Encrypt forum (https://community.letsencrypt.org/t/errors-in-npm-log-files/244662/2), but the advice was this is an issue with how NPM handles revoking of expired certs.I deleted these 2 affected proxy hosts from NPM, and also in the Certificates menu, I deleted them.How do I remove them from my NPM config, so no more certbot requests are made?
January 22Jan 22 Did something change with the package/binary in the last release or two? I can't pinpoint exactly when the problems started, but all of my Proxy hosts that are pointed to internal sites are all throwing 502 errors. They all show "online" in the dashboard, so I assume that means they are reachable. The cert is definitely getting renewed, and I can renew it through the UI just fine too.I don't think anything changed on my side that would cause ALL of them to stop working. I'm thinking it's something network-related with the docker container, as I've seen some recent comments on things that might be different there. I'm currently using Custom Br0, and have been for years without issues. I wish the docker CLI had some ping//netcat commands to help troubleshoot network issues, but it looks pretty bare. The single error.log in /var/log/nginx isn't too helpful when the 502 happens. Are there other more detailed logs someplace?I see curl is installed and when I run that from the docker instance it does show correct data when I point it at an internal host, so maybe not specifically network? Edited January 22Jan 22 by yoleska
February 3Feb 3 On 1/22/2026 at 2:41 AM, yoleska said:Did something change with the package/binary in the last release or two? I can't pinpoint exactly when the problems started, but all of my Proxy hosts that are pointed to internal sites are all throwing 502 errors. They all show "online" in the dashboard, so I assume that means they are reachable. The cert is definitely getting renewed, and I can renew it through the UI just fine too.I don't think anything changed on my side that would cause ALL of them to stop working. I'm thinking it's something network-related with the docker container, as I've seen some recent comments on things that might be different there. I'm currently using Custom Br0, and have been for years without issues. I wish the docker CLI had some ping//netcat commands to help troubleshoot network issues, but it looks pretty bare. The single error.log in /var/log/nginx isn't too helpful when the 502 happens. Are there other more detailed logs someplace?I see curl is installed and when I run that from the docker instance it does show correct data when I point it at an internal host, so maybe not specifically network?My setup sounds exactly like yours and I was having the same issue. What fixed it for me was to enable "Host access to custom networks" in the advanced Docker settings which is off by default.
March 11Mar 11 Hello, newbie user to Unraid.I'm trying to set up full remote access to some Docker containers with the end goal of being able to host my own web page, and I'm trying to configure Nginx Proxy Manager.I've downloaded Nginx and tried setting it up, however the web GUI always says the API is unhealthy. Not sure what I'm doing wrong.Checking the logs shows the same result, with updated time stamps: Quote[timestamp] [Global ] › ✖ error Startup Error: Cannot open database because the directory does not exist TypeError: Cannot open database because the directory does not existat new Database (/app/node_modules/better-sqlite3/lib/database.js:65:9)at Client_BetterSQLite3.acquireRawConnection (/app/node_modules/knex/lib/dialects/better-sqlite3/index.js:14:12)at create (/app/node_modules/knex/lib/client.js:262:39)Everything is fully updated, running Unraid 7.2.2
March 22Mar 22 When trying to enable tailscale in this container:Executing Unraid Docker Hook for TailscaleDetecting Package Manager...Detected Advanced Package Tool!Installing packages...Please wait...ERROR: Installing packages!Ign:1 https://deb.nodesource.com/node_22.x nodistro InReleaseIgn:2 http://deb.debian.org/debian bookworm InReleaseIgn:3 http://deb.debian.org/debian bookworm-updates InReleaseIgn:4 http://deb.debian.org/debian-security bookworm-security InReleaseIgn:2 http://deb.debian.org/debian bookworm InReleaseIgn:1 https://deb.nodesource.com/node_22.x nodistro InReleaseIgn:3 http://deb.debian.org/debian bookworm-updates InReleaseIgn:4 http://deb.debian.org/debian-security bookworm-security InReleaseIgn:1 https://deb.nodesource.com/node_22.x nodistro InReleaseIgn:2 http://deb.debian.org/debian bookworm InReleaseIgn:3 http://deb.debian.org/debian bookworm-updates InReleaseIgn:4 http://deb.debian.org/debian-security bookworm-security InReleaseErr:1 https://deb.nodesource.com/node_22.x nodistro InRelease Temporary failure resolving 'deb.nodesource.com'Err:2 http://deb.debian.org/debian bookworm InRelease Temporary failure resolving 'deb.debian.org'Err:3 http://deb.debian.org/debian bookworm-updates InRelease Temporary failure resolving 'deb.debian.org'Err:4 http://deb.debian.org/debian-security bookworm-security InRelease Temporary failure resolving 'deb.debian.org'Reading package lists...W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease Temporary failure resolving 'deb.debian.org'W: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease Temporary failure resolving 'deb.debian.org'W: Failed to fetch http://deb.debian.org/debian-security/dists/bookworm-security/InRelease Temporary failure resolving 'deb.debian.org'W: Failed to fetch https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease Temporary failure resolving 'deb.nodesource.com'W: Some index files failed to download. They have been ignored, or old ones used instead.Reading package lists...Building dependency tree...Reading state information...Package wget is not available, but is referred to by another package.This may mean that the package is missing, has been obsoleted, oris only available from another sourceE: Package 'wget' has no installation candidateEventually:ERROR: Unraid Docker Hook script throw an error! Starting container without Tailscale!I think there's an issue with the container and the pre-defined tailscale script.
March 25Mar 25 On 1/22/2026 at 1:41 AM, yoleska said:Did something change with the package/binary in the last release or two? I can't pinpoint exactly when the problems started, but all of my Proxy hosts that are pointed to internal sites are all throwing 502 errors. They all show "online" in the dashboard, so I assume that means they are reachable. The cert is definitely getting renewed, and I can renew it through the UI just fine too.I don't think anything changed on my side that would cause ALL of them to stop working. I'm thinking it's something network-related with the docker container, as I've seen some recent comments on things that might be different there. I'm currently using Custom Br0, and have been for years without issues. I wish the docker CLI had some ping//netcat commands to help troubleshoot network issues, but it looks pretty bare. The single error.log in /var/log/nginx isn't too helpful when the 502 happens. Are there other more detailed logs someplace?I see curl is installed and when I run that from the docker instance it does show correct data when I point it at an internal host, so maybe not specifically network?Were you abe to resolve this? This just happened to me today and I had to disable my local NPM and point my URLs to my external NPM for traffic to start working again.
May 11May 11 Running into trouble with one of the plugins, and I need to run a pip install to fix it, but I cannot find pip anywhere in the container. I see references to it in the past but it doesn't exist in those locations anymore? Did it get removed?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.