mattie112 Posted March 8, 2023 Share Posted March 8, 2023 Try it from a different PC / browser. Try to 'ping' it to see if it resolves correctly. Does not look like a NPM problem to me as NPM has nothing to do with DNS. Quote Link to comment
upsidedownlemon Posted March 9, 2023 Share Posted March 9, 2023 Ran into this error after upgrading recently - wondering if anyone has ideas / a fix? [supervisor ] service 'nginx' failed to be started: could not forkNo space left on device. Diags look OK to me - thanks tower-diagnostics-20230309-2141.zip Quote Link to comment
mattie112 Posted March 9, 2023 Share Posted March 9, 2023 35 minutes ago, upsidedownlemon said: Ran into this error after upgrading recently - wondering if anyone has ideas / a fix? [supervisor ] service 'nginx' failed to be started: could not forkNo space left on device. Diags look OK to me - thanks tower-diagnostics-20230309-2141.zip 479.24 kB · 0 downloads Well the error is that your disk is full. At your docker settings (advanced) you can see how much space there is left in your docker volume. I would suggest to check that first. Quote Link to comment
Mark G Posted March 23, 2023 Share Posted March 23, 2023 Hi All, not sure why I'm getting this error, my log file is filling up with this Increase nchan_max_reserved_memory. Mar 22 04:40:02 STD nginx: 2023/03/22 04:40:02 [error] 5238#5238: *5724215 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/notify?buffer_length=1 HTTP/1.1", host: "localhost" Mar 22 04:40:02 STD nginx: 2023/03/22 04:40:02 [error] 5238#5238: MEMSTORE:00: can't create shared message for channel /notify Mar 22 04:40:04 STD nginx: 2023/03/22 04:40:04 [crit] 5238#5238: ngx_slab_alloc() failed: no memory Mar 22 04:40:04 STD nginx: 2023/03/22 04:40:04 [error] 5238#5238: shpool alloc failed Mar 22 04:40:04 STD nginx: 2023/03/22 04:40:04 [error] 5238#5238: nchan: Out of shared memory while allocating message of size 4162. [11:32 AM] can anyone help me to fix this issue? Quote Link to comment
tazire Posted March 27, 2023 Share Posted March 27, 2023 Just wondering if anyone has tried to get crowdsec running with NPM? I'm just starting to look into it and seen that there is another container that has included the crowdsec bouncer. I'd rather try add this to my existing container if its possible? Quote Link to comment
antagon Posted March 27, 2023 Share Posted March 27, 2023 (edited) Hi after reinstalling npm, I got 10 out of 12 redirections to my containers running properly. I´m stuck with those two and I don´t understand why. Any idea whats the problem here? Links are available outside my network, I get a "deceptive site ahead" or "NET::ERR_CERT_AUTHORITY_INVALID" message NPM_log_cleanedup.txt Edited March 27, 2023 by antagon Quote Link to comment
Gragorg Posted March 29, 2023 Share Posted March 29, 2023 (edited) Currently I'm using Swag and I setup all the subdomains I want to use on a single duckdns domain. So for example bitwarden.mydomain.duckdns.org or nextcloud.mydomain.duckdns.org. How can I do this on NPM without a Cname? I use mydomain.duckdns.org for all my dockers. Want to switch to NPM and add Authentik. Edited March 29, 2023 by Gragorg Quote Link to comment
mattie112 Posted March 31, 2023 Share Posted March 31, 2023 On 3/27/2023 at 6:27 PM, antagon said: Hi after reinstalling npm, I got 10 out of 12 redirections to my containers running properly. I´m stuck with those two and I don´t understand why. Any idea whats the problem here? Links are available outside my network, I get a "deceptive site ahead" or "NET::ERR_CERT_AUTHORITY_INVALID" message NPM_log_cleanedup.txt 17.66 kB · 0 downloads The log file lists it already: "detail": "DNS problem: NXDOMAIN looking up A for dom.main-name.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for dom.main-name.com - check that a DNS record exists for this domain", Please confirm that your DNS is correctly set-up. Quote Link to comment
mattie112 Posted March 31, 2023 Share Posted March 31, 2023 On 3/29/2023 at 11:55 PM, Gragorg said: Currently I'm using Swag and I setup all the subdomains I want to use on a single duckdns domain. So for example bitwarden.mydomain.duckdns.org or nextcloud.mydomain.duckdns.org. How can I do this on NPM without a Cname? I use mydomain.duckdns.org for all my dockers. Want to switch to NPM and add Authentik. All domains must point to your IP. You can use a CNAME or an A record. This is unrelated to NPM. So what exactly is your question/problem? Quote Link to comment
Serijag Posted April 1, 2023 Share Posted April 1, 2023 On 3/8/2023 at 12:08 PM, crabsticks said: Hello, I have been accessing several containers on unraid using nginx proxy manager with no issues. Suddenly today I get and error page stating "DNS address could not be found. DNS_PROBE_POSSIBLE In Ngnix webgui all the redirects are listed as online and have valid certificates. All the containers are accessible through the local ip address. I have no idea what suddenly caused this and would appreciate advice on how to diagnose and fix the error. In the logs for nginx is does say that some things are depreciated if that's relevant Thanks in advance I'm having this same issue did you ever figure out what was going on? Quote Link to comment
mattie112 Posted April 2, 2023 Share Posted April 2, 2023 9 hours ago, Serijag said: I'm having this same issue did you ever figure out what was going on? Confirm that your DNS is set-up correctly with a tool like: https://www.whatsmydns.net/ Confirm that your PC resolved the domain to the correct IP (for example by doing a ping or traceroute). Try it from a different device -> if it works there check your local PC for firewall for issues Try it from a different internet connection -> if it works check your modem/router firewall for issues Quote Link to comment
Serijag Posted April 2, 2023 Share Posted April 2, 2023 6 hours ago, mattie112 said: Confirm that your DNS is set-up correctly with a tool like: https://www.whatsmydns.net/ Confirm that your PC resolved the domain to the correct IP (for example by doing a ping or traceroute). Try it from a different device -> if it works there check your local PC for firewall for issues Try it from a different internet connection -> if it works check your modem/router firewall for issues Thanks, I ended up figuring it out pretty much following these steps. Firewall\router rules weren't working correctly after a modem reboot and had to readd the port forwarding rules for NPM. Never had that before so hopefully it was just a fluke. Thanks Quote Link to comment
Reptar Posted April 11, 2023 Share Posted April 11, 2023 Did anyone else have issues with the most recent update (v23.04.1)? seems to have broken things for me. all of my sites return 502 and I had to revert to v23.03.2 Quote Link to comment
Magaman Posted April 17, 2023 Share Posted April 17, 2023 On 4/10/2023 at 8:29 PM, Reptar said: Did anyone else have issues with the most recent update (v23.04.1)? seems to have broken things for me. all of my sites return 502 and I had to revert to v23.03.2 Same boat everything is broken at the moment, How did you revert back? Quote Link to comment
mattie112 Posted April 17, 2023 Share Posted April 17, 2023 Just use any of the older tags: https://hub.docker.com/r/jlesage/nginx-proxy-manager/tags 2 Quote Link to comment
masterdot Posted May 2, 2023 Share Posted May 2, 2023 On 1/28/2021 at 9:12 PM, ufo56 said: Has anyone been able to get NPM work with matrix federation ? https://github.com/matrix-org/synapse/blob/master/docs/reverse_proxy.md#nginx Did you get it running? I do have the same problem with my setup Quote Link to comment
ufo56 Posted May 3, 2023 Share Posted May 3, 2023 14 hours ago, masterdot said: Did you get it running? I do have the same problem with my setup custom locations listen 8448 ssl; location / { proxy_pass http://192.168.1.211:8008; proxy_set_header X-Forwarded-For $remote_addr; } location /.well-known/matrix/client { return 200 '{"m.homeserver": {"base_url": "https://matrix.domain.com"}}'; default_type application/json; add_header Access-Control-Allow-Origin *; } location /.well-known/matrix/server { return 200 '{"m.server": "matrix.domain.com:443" }'; default_type application/json; add_header Access-Control-Allow-Origin *; } Quote Link to comment
masterdot Posted May 4, 2023 Share Posted May 4, 2023 Hmm... I did transfer it, but now the proxy manager is showing up the domain as offline. Seems to be a problem with my changes... Quote Link to comment
Nebur692 Posted May 31, 2023 Share Posted May 31, 2023 Can it be updated to version 2.10.3? Quote Link to comment
plantsandbinary Posted June 1, 2023 Share Posted June 1, 2023 I just tried to generate a wildcard cert using Cloudfare API token DNS challenge and the app spontaneously killed itself completely whilst doing it: [cert_cleanup] ---------------------------------------------------------- [cert_cleanup] Let's Encrypt certificates cleanup - 2023/06/01 23:16:59 [cert_cleanup] ---------------------------------------------------------- [cert_cleanup] 0 file(s) kept. [cert_cleanup] 0 file(s) deleted. [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info Current database version: none [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] auth Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] user Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] user_permission Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] proxy_host Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] redirection_host Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] dead_host Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] stream Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] access_list Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] certificate Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] access_list_auth Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] audit_log Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [websockets] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [websockets] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [forward_host] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [forward_host] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [http2_support] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [http2_support] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [http2_support] redirection_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [http2_support] dead_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [forward_scheme] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [forward_scheme] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [disabled] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [disabled] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [disabled] redirection_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [disabled] dead_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [disabled] stream Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [custom_locations] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [custom_locations] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [hsts] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [hsts] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [hsts] redirection_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [hsts] dead_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [settings] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [settings] setting Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [access_list_client] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [access_list_client] access_list_client Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [access_list_client] access_list Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [access_list_client_fix] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [access_list_client_fix] access_list Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [pass_auth] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [pass_auth] access_list Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [redirection_scheme] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [redirection_scheme] redirection_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [redirection_status_code] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [redirection_status_code] redirection_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [stream_domain] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [stream_domain] stream Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [stream_domain] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Setup ] › ℹ info Creating a new JWT key pair... [supervisor ] all services started. [app ] [6/1/2023] [11:17:01 PM] [Setup ] › ℹ info Wrote JWT key pair to config file: /opt/nginx-proxy-manager/config/production.json [app ] [6/1/2023] [11:17:01 PM] [Setup ] › ℹ info Creating a new user: [email protected] with password: changeme [app ] [6/1/2023] [11:17:02 PM] [Setup ] › ℹ info Initial admin setup completed [app ] [6/1/2023] [11:17:02 PM] [Setup ] › ℹ info Default settings added [app ] [6/1/2023] [11:17:02 PM] [Setup ] › ℹ info Logrotate Timer initialized [app ] [6/1/2023] [11:17:02 PM] [Setup ] › ℹ info Logrotate completed. [app ] [6/1/2023] [11:17:02 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [app ] [6/1/2023] [11:17:02 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [app ] [6/1/2023] [11:17:02 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [app ] [6/1/2023] [11:17:02 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [app ] [6/1/2023] [11:17:02 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [app ] [6/1/2023] [11:17:02 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [app ] [6/1/2023] [11:17:02 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [app ] [6/1/2023] [11:17:02 PM] [Global ] › ℹ info Backend PID 417 listening on port 3000 ... [app ] [6/1/2023] [11:17:02 PM] [Nginx ] › ℹ info Reloading Nginx [app ] [6/1/2023] [11:17:02 PM] [SSL ] › ℹ info Renew Complete [app ] [6/1/2023] [11:18:01 PM] [SSL ] › ℹ info Testing http challenge for *.xtu.icu [app ] Uncaught SyntaxError: Unexpected end of JSON input [app ] FROM [supervisor ] service 'app' exited (got signal SIGILL). [supervisor ] service 'app' exited, shutting down... [supervisor ] stopping service 'nginx'... [supervisor ] service 'nginx' exited (with status 0). [finish ] executing container finish scripts... [finish ] all container finish scripts executed. ** Press ANY KEY to close this window ** Obviously this is not supposed to happen... Quote Link to comment
plantsandbinary Posted June 1, 2023 Share Posted June 1, 2023 Actually it seems to kill itself any time it does an HTTP challenge: [app ] 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 [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ⬤ debug Could not delete file: { [app ] "errno": -2, [app ] "syscall": "unlink", [app ] "code": "ENOENT", [app ] "path": "/data/nginx/proxy_host/1.conf" [app ] } [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ⬤ debug Could not delete file: { [app ] "errno": -2, [app ] "syscall": "unlink", [app ] "code": "ENOENT", [app ] "path": "/data/nginx/proxy_host/1.conf" [app ] } [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf.err [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ⬤ debug Could not delete file: { [app ] "errno": -2, [app ] "syscall": "unlink", [app ] "code": "ENOENT", [app ] "path": "/data/nginx/proxy_host/1.conf.err" [app ] } [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ℹ info Reloading Nginx [app ] [6/1/2023] [11:24:14 PM] [SSL ] › ℹ info Testing http challenge for xtu.icu [app ] Uncaught SyntaxError: Unexpected end of JSON input [app ] FROM [supervisor ] service 'app' exited (got signal SIGILL). [supervisor ] service 'app' exited, shutting down... [supervisor ] stopping service 'nginx'... [supervisor ] service 'nginx' exited (with status 0). [finish ] executing container finish scripts... [finish ] all container finish scripts executed. ** Press ANY KEY to close this window ** Quote Link to comment
mattie112 Posted June 2, 2023 Share Posted June 2, 2023 You can try to run certbot manually to get some more debugging info. Quote Link to comment
RackIt Posted June 2, 2023 Share Posted June 2, 2023 In the event this helps anyone else... I placed FileBrowser behind NGM. My test file is 73GB. I was able to upload this file in FileBrowser without NGM but it would fail with NGM. I noticed docker throwing a space warning. NGM was buffering the upload within the docker container. I am now able to successfully upload my test file after adding the following Custom Nginx Configuration. Some settings might not be needed but it works and at least is a starting point. proxy_request_buffering off; proxy_buffering off; proxy_set_header Host $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_max_temp_file_size 0; client_max_body_size 0; Quote Link to comment
debit lagos Posted June 2, 2023 Share Posted June 2, 2023 (edited) 1 hour ago, RackIt said: In the event this helps anyone else... I placed FileBrowser behind NGM. My test file is 73GB. I was able to upload this file in FileBrowser without NGM but it would fail with NGM. I noticed docker throwing a space warning. NGM was buffering the upload within the docker container. I am now able to successfully upload my test file after adding the following Custom Nginx Configuration. Some settings might not be needed but it works and at least is a starting point. proxy_request_buffering off; proxy_buffering off; proxy_set_header Host $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_max_temp_file_size 0; client_max_body_size 0; Did you add these to custom location or to the actual proxy files for that host? Edited June 2, 2023 by debit lagos Quote Link to comment
Recommended Posts
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.