Gentle DJoss and others,

I am a beginner in self hosting. I succeed to configure few docker apps.

Now I want to expose a blog and limited Nextcloud through the NGINX Proxy Manager. It is an App listed among the unRaid apps, I have chosen the Official one.

I succeeded to configure three proxy. Shoud I configure the NPM itself as one of the proxy? The router point at it.

I wanted to create an Access List to limit the access to Nextcloud and to NPM, but the app doesn't permit to save any ALLOW rule.

Do you have any hint?

6 hours ago, gnuman said:

Gentle DJoss and others,

I am a beginner in self hosting. I succeed to configure few docker apps.

Now I want to expose a blog and limited Nextcloud through the NGINX Proxy Manager. It is an App listed among the unRaid apps, I have chosen the Official one.

 

Probably it was a temporary connection problem. Now everything is working smoth!

greetings fellow organic lifeforms,

 

npm is no longer renewing certificates for me and if i manually renew them in the certificates tab the  log says the following

Command failed: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-8" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation

 

p.s. when booting the container i also get this message "[Migrate  ] › ℹ  info      Current database version: none"

 

anybody know whats going on here?

 

thx Sages,

On 11/26/2023 at 3:24 PM, Sages said:

greetings fellow organic lifeforms,

 

npm is no longer renewing certificates for me and if i manually renew them in the certificates tab the  log says the following

Command failed: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-8" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation

 

p.s. when booting the container i also get this message "[Migrate  ] › ℹ  info      Current database version: none"

 

anybody know whats going on here?

 

thx Sages,

 

Try to renew it via de CLI (see elsewhere in this topic posted it numerous times). There is a --dry-run or a --force-renew flag for certbot. Then see what errors you are getting.

Could I get some help? I forgotten my nginx proxy manager password and wondering if someone can help me with a step by step tutorial on how to get it reset? I am fairly new to these kinds of things.

Edited December 1, 20232 yr by hailinh004

2 hours ago, hailinh004 said:

Could I get some help? I forgotten my nginx proxy manager password and wondering if someone can help me with a step by step tutorial on how to get it reset? I am fairly new to these kinds of things.

 

assuming you are not using a external mariadb container, i googled it for you ...

 

https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/1634

+1 for NPM certificate issues.

Is there a way to downgrade to an earlier version of NPM?

6 hours ago, alturismo said:

assuming you are not using a external mariadb container, i googled it for you ...

 

https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/1634

I followed the instruction and got an error.

On 11/27/2023 at 4:02 PM, mattie112 said:

 

Try to renew it via de CLI (see elsewhere in this topic posted it numerous times). There is a --dry-run or a --force-renew flag for certbot. Then see what errors you are getting.

 that just gives me "certbot is allready running"

Yeah I'm having renewal issues too and if you try to renew you get the error and then whatever docker you have using it is unreachable. Have to restart the dockers.

Just starting getting the error: Internal Error when I go for a new certificate

Log says:

 

[12/4/2023] [8:50:34 PM] [Express  ] › ⚠  warning   Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-33" --agree-tos --authenticator webroot --email "[email protected]" --preferred-challenges "dns,http" --domains "yaddayaddachanged.duckdns.org" 
[app         ] Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
[app         ] Some challenges have failed.

 

 

Any help would be great, have been trying everything, I am on the latest version. 

 

*EDIT* I fixed it, didn't have USA permitted on my Firewall, added it (I am from Canada) and everything works. 

 

 

 

Edited December 5, 20232 yr by kumper33

On 12/5/2023 at 10:39 AM, nxtiak said:

Yeah I'm having renewal issues too and if you try to renew you get the error and then whatever docker you have using it is unreachable. Have to restart the dockers.

I think our issue has to do with this bug in Github:
https://github.com/jlesage/docker-nginx-proxy-manager/issues/306

@nxtiak For you was NPM working fine before the last update/ this issue?

For me everything was working 100% and then around last month it stopped.

 

I also tried to install the official NPM docker container and seem to be getting the exact same error.

On 12/5/2023 at 2:39 AM, nxtiak said:

Yeah I'm having renewal issues too and if you try to renew you get the error and then whatever docker you have using it is unreachable. Have to restart the dockers.

i doubt that is my issue . i turn of my unraid box every night to save some power(lunar panels don't exist sadly) and boot it up in the morning

Check the SSL certificates tab. If any are for domains that are not targeted at NPM anymore remove them. 

Renewing certificates is working for me now!

3 hours ago, nxtiak said:

Renewing certificates is working for me now!

Did you have to do something special to get them to renew? When I try to manually renew them I still get the attached error.

I also tried to delete certificates are re-create them and get this error:


When I try to 'Test Server Reachability' from the SSL page of NPMPM I get the error 'Communication with the API failed, is NPM running correctly?' and it also causes the NPMPM Docker container to stop.

I would be happy to share whatever logs I have but I'm not sure what I can share to help diagnose this. NPMPM was working fine for at least a month and has only had issues recently.

I also get the 'Communication with the API failed, is NPM running correctly?' when trying to add a new ssl cert manually. If I try to generate it while adding the proxy host, I get internal error.

On 12/6/2023 at 6:07 PM, What's_a_Computer? said:

I also tried to delete certificates are re-create them and get this error:


When I try to 'Test Server Reachability' from the SSL page of NPMPM I get the error 'Communication with the API failed, is NPM running correctly?' and it also causes the NPMPM Docker container to stop.

I would be happy to share whatever logs I have but I'm not sure what I can share to help diagnose this. NPMPM was working fine for at least a month and has only had issues recently.

 

Same thing for me. Docker container just shuts down

using lasted version in Docker in Unraid + Authelia+Cloudflare .

After last update have a lot of warnings For Every Proxy hosts:

 

[warn] 464#464: *60 using uninitialized "test" variable, client: 162.158.x.x, server: sub.mysite.com, request: "GET /api/sync HTTP/2.0", host: "sub.mysite.com"

 

and also vaultwarden have this :

 

   an upstream response is buffered to a temporary file /var/tmp/nginx/proxy/2/35/0000001352 while reading upstream, client: x.x.x.x, server: sub.mysite.com, request: "GET /api/sync HTTP/2.0", upstream: "http://192.168.0.199:4743/api/sync", host: "sub.mysite.com"

 

Am getting a certbot route53 error again in the logs and am unable to log in to the gui (since itself relies on ssl certificate!) - log is showing the following repeatedly:

 

[app         ] [12/29/2023] [11:33:43 AM] [Global   ] › ✖  error     Command failed: pip install --no-cache-dir certbot-dns-route53==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') 
[app         ] The 'certbot_dns_route53.authenticator' plugin errored while loading: cannot import name 'DEFAULT_CIPHERS' from 'urllib3.util.ssl_' (/usr/lib/python3.10/site-packages/urllib3/util/ssl_.py). You may need to remove or update this plugin. The Certbot log will contain the full error details and this should be reported to the plugin developer.
[app         ] Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-ul_q9vn7/log or re-run Certbot with -v for more details.
[app         ] ERROR: Could not find a version that satisfies the requirement certbot-dns-route53== (from versions: 0.15.0.dev0, 0.15.0, 0.16.0, 0.17.0, 0.18.0, 0.18.1, 0.18.2, 0.19.0, 0.20.0, 0.21.0, 0.21.1, 0.22.0, 0.22.1, 0.22.2, 0.23.0, 0.24.0, 0.25.0, 0.25.1, 0.26.0, 0.26.1, 0.27.0, 0.27.1, 0.28.0, 0.29.0, 0.29.1, 0.30.0, 0.30.1, 0.30.2, 0.31.0, 0.32.0, 0.33.0, 0.33.1, 0.34.0, 0.34.1, 0.34.2, 0.35.0, 0.35.1, 0.36.0, 0.37.0, 0.37.1, 0.37.2, 0.38.0, 0.39.0, 0.40.0, 0.40.1, 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0, 1.10.1, 1.11.0, 1.12.0, 1.13.0, 1.14.0, 1.15.0, 1.16.0, 1.17.0, 1.18.0, 1.19.0, 1.20.0, 1.21.0, 1.22.0, 1.23.0, 1.24.0, 1.25.0, 1.26.0, 1.27.0, 1.28.0, 1.29.0, 1.30.0, 1.31.0, 1.32.0, 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.8.0)
[app         ] ERROR: No matching distribution found for certbot-dns-route53==
[app         ] [12/29/2023] [11:33:44 AM] [Migrate  ] › ℹ  info      Current database version: none

 

Unfortunately the fix before doesn't seem to be working - anyone know how to fix this once and for all? (may be a recent update issue since only just started reoccurring again)

 

EDIT: So the only way I was able to fix this error was to run the following command and download urllib manually:

pip install 'urllib3<2'

 

Nginx Proxy Manager then loaded and unsuccessfully failed to auto-renew the certificates - after this, I was able to manually renew the certificates from the UI.

 

Strangely, if I reboot the container than the original error re-occurs and I have to manually execute the above command again...

 

Anyone else encountering the same or can suggest a permanent fix? Many thanks

 

 

Edited December 29, 20232 yr by Ptolemyiv

Hello I am getting this error on Docker startup and then it aborts startup:

 

 

 

SOLVED: This was related to data corruption solved by xfs_repair

Edited January 5, 20242 yr by JannikGHG

Hey guys, just getting started with unraid and loving it so far!

 

I've set up my domain, cloudflare, and nginx up properly to use http for all of my dockers (I've also created SSL certificates for each of them from the SSL tab). What I am trying to do now is change them to https, the issue is that whenever I update the "scheme" from http to https, the site gives me a "too many redirects" error. I have a feeling that there is something else I should be doing, but I have no clue where to start.

 

Any help would be appreciated!

On 1/8/2024 at 5:29 AM, CopesaCola said:

Hey guys, just getting started with unraid and loving it so far!

 

I've set up my domain, cloudflare, and nginx up properly to use http for all of my dockers (I've also created SSL certificates for each of them from the SSL tab). What I am trying to do now is change them to https, the issue is that whenever I update the "scheme" from http to https, the site gives me a "too many redirects" error. I have a feeling that there is something else I should be doing, but I have no clue where to start.

 

Any help would be appreciated!

This could be a lan routing issue - try accessing the site externally (e.g. via mobile) and see if you get the same too many redirects error.

 

If not, in your router you need to find somewhere to configure a static dns hostname - so if e.g. your external domain is www.yoursite.co.uk and your nginx docker ip address is 192.168.1.2 then you would map that domain to that IP - any internal nginx requests would then be routed directly and avoid this infinite routing loop issue you are experiencing. I use a Unifi UDM Pro router and they finally added this feature last year for instance..

 

(For external access you'll also need to forward any incoming port 443 traffic on your router to the nginx IP)

Edited January 12, 20242 yr by Ptolemyiv

Hello Friends,

I've recently had an issue with my server SSD and my docker.img got corrupted.

After I deleted the old docker.img file, I re-installed all my docker apps from the previously installed templates.

And now I'm able to use most apps I previously had with their previous appdata intact.

Unfortunately though, I'm having a strange issue when using the NginxProxyManager container. When I set the container to use a custom network type I created, the app's webui loads, but I can't log into NPM's control dashboard. Nothing happens when I press "sign in" and I'm using the correct email/password combination.

However, if I change the network type to Host, I am able to sign in using the webui into the control dashboard, but then non of my other docker apps (which I configured to work with NPM for external internet access with my domain name) are available when I try to use them the sub-domain addresses I created for them.

Is this issue familiar to someone?

I will appreciate any help solving this issue 🙏

 

Update: after disabling Unraid's Use UPnP under Management Access, I'm now able to log into the NPM dashboard when using a custom network type. However, I still can't reach any of my docker services that use the external domain addresses I defined in NPM with let's encrypt certificates.

 

 

Edited January 12, 20242 yr by mjeshurun