aglyons Posted June 14, 2023 Share Posted June 14, 2023 5 hours ago, TeKo said: I'm getting this error: Is there something I can do to fix this? AFAIK, Are these set in the config? And what are the read/write permissions on the ..../appdata/Nginx-Proxy-Manager-Official/data/logs files? Make sure that they are set to this Quote Link to comment
TeKo Posted June 14, 2023 Share Posted June 14, 2023 3 hours ago, aglyons said: AFAIK, Are these set in the config? And what are the read/write permissions on the ..../appdata/Nginx-Proxy-Manager-Official/data/logs files? Make sure that they are set to this I added both variables to my config and set the permissions. Looks like the error is gone. Thanks a lot. Quote Link to comment
kasuke Posted June 16, 2023 Share Posted June 16, 2023 (edited) Hello, I got an issue, it's been a while that I didn't modify/add a host. I wanted to change a local ip of a host because my DHCP assign other IP address but on every hosts that I tried to change I got this kind of error : 16/06/2023 16:47:39 [app ] [6/16/2023] [4:47:39 PM] [SSL ] › ✖ error Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-22/fullchain.pem -subject -noout 16/06/2023 16:47:39 [app ] Can't open /etc/letsencrypt/live/npm-22/fullchain.pem for reading, No such file or directory 16/06/2023 16:47:39 [app ] 22733364558664:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-22/fullchain.pem','r') 16/06/2023 16:47:39 [app ] 22733364558664:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76: 16/06/2023 16:47:39 [app ] unable to load certificate 16/06/2023 16:47:39 [app ] ) and it just appears offline in the GUI. I don't get the error, here this is only because it doesn't find a specific file, but can it just not recreate it ? And why the others are working fine, the one that I didn't edit. I don't know what to search and what to do If you need more info from me tell me Thanks Edited June 16, 2023 by kasuke Quote Link to comment
Lucas319315 Posted June 16, 2023 Share Posted June 16, 2023 (edited) Any one know why this is limited to 1GiB? I have other docker images and they are all set to 15.3GiB. Nginx-Proxy-Manager-Officil or jc21/nginx-proxy-manager is the only docker image limited. Edited June 16, 2023 by Lucas319315 Quote Link to comment
Kilrah Posted June 16, 2023 Share Posted June 16, 2023 Some templates have a max RAM amount set in the extra parameters (can see it in advanced mode) 1 Quote Link to comment
mgutt Posted June 23, 2023 Author Share Posted June 23, 2023 On 6/16/2023 at 7:49 PM, Lucas319315 said: Any one know why this is limited to 1GiB? All my container templates have a RAM limit set to avoid server crashes if a container goes wild. 1 Quote Link to comment
Joshwaaa Posted June 25, 2023 Share Posted June 25, 2023 I finally updated unRAID to the latest version and now nginx doesn't have a web ui? How do I get that back? Quote Link to comment
Joshwaaa Posted June 25, 2023 Share Posted June 25, 2023 Disregard. A reboot didn't fix it so I went to the template, deleted one number, and then typed the same number I deleted and installed it again. That fixed it. Now I have a new problem. My WEB UI is going to a WAN site and not my LAN IP. It's a config issue. What usually causes that? Quote Link to comment
Kilrah Posted June 25, 2023 Share Posted June 25, 2023 (edited) Check that the WebUI label didn't get mangled. Edited June 25, 2023 by Kilrah Quote Link to comment
pallalino Posted June 26, 2023 Share Posted June 26, 2023 Hi, I've receicently upgraded to Unraid 6.12.0 and now I recognize that my Vaultwarden (only locally) is no longer running. DB docke ris started and I also tried to start Nginx-Proxy-Manager-Official (where I've forgotten that this is needed for Vaultwarden). I upgraded Nginx to the latest version now, too. When I start the docker a popup appears: " Execution error Server error" Afterwards I changed the network type to a different entry and then back to the previous one but in both cases I get the following message: -- Removing container: Nginx-Proxy-Manager-Official Successfully removed container 'Nginx-Proxy-Manager-Official' Command executiondocker run -d --name='Nginx-Proxy-Manager-Official' --net='nasnet' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="nas" -e HOST_CONTAINERNAME="Nginx-Proxy-Manager-Official" -e 'DB_SQLITE_FILE'='/data/database.sqlite' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:81]' -l net.unraid.docker.icon='https://nginxproxymanager.com/icon.png' -p '81:81/tcp' -p '1880:80/tcp' -p '443:443/tcp' -p '3000:3000/tcp' -v '/mnt/user/appdata/Nginx-Proxy-Manager-Official/data':'/data':'rw' -v '/mnt/user/appdata/Nginx-Proxy-Manager-Official/letsencrypt':'/etc/letsencrypt':'rw' -v '/tmp/Nginx-Proxy-Manager-Official/var/log':'/var/log':'rw' --memory=1G --no-healthcheck 'jc21/nginx-proxy-manager' WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. c5b435d10b345c7f7c50f0e544899c76432501c76142950a74e49a4efc402a84 docker: Error response from daemon: driver failed programming external connectivity on endpoint Nginx-Proxy-Manager-Official (7dc6fe7dbfef257df73e8e872aa05f22ef768e5a91eb77520dcbf0d7f32ee77c): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use. The command failed. --- Any idea what I could do to solve the issue? Thank you Quote Link to comment
mgutt Posted June 26, 2023 Author Share Posted June 26, 2023 1 hour ago, pallalino said: listen tcp4 0.0.0.0:443: bind: address already in use. There is already something listening on port 443. Did you enable SSL for unRAID and does unRAID use 443? Disable SSL and change unRAIDs ports to 5000 and 5001. Quote Link to comment
pallalino Posted June 26, 2023 Share Posted June 26, 2023 Port 443 is not used in another docker. I only find this port for unRAID, but ssl is not enabled, too. Should I still change the ports to 5000/5001? Strange is, that I haven't changed/installed somethign new recently, only updated all dockers etc. Quote Link to comment
pallalino Posted June 26, 2023 Share Posted June 26, 2023 I changed it....it's now working fine. Thank you Quote Link to comment
mgutt Posted June 26, 2023 Author Share Posted June 26, 2023 Ok. Then maybe this is a new behavior of the recent unRAID version. Quote Link to comment
kasuke Posted July 3, 2023 Share Posted July 3, 2023 (edited) recently updated too but now I got this error : 03/07/2023 15:19:54 [nginx ] nginx: [emerg] still could not bind() 03/07/2023 15:19:55 [supervisor ] service 'nginx' exited (with status 1). 03/07/2023 15:19:55 [supervisor ] restarting service 'nginx'. 03/07/2023 15:19:55 [supervisor ] starting service 'nginx'... 03/07/2023 15:19:55 [nginx ] nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/24.conf:111 03/07/2023 15:19:55 [nginx ] nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/27.conf:111 03/07/2023 15:19:55 [nginx ] nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/30.conf:83 03/07/2023 15:19:55 [nginx ] nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/37.conf:111 03/07/2023 15:19:55 [nginx ] nginx: [emerg] bind() to 0.0.0.0:8181 failed (98: Address in use) 03/07/2023 15:19:56 [nginx ] nginx: [emerg] bind() to 0.0.0.0:8181 failed (98: Address in use) 03/07/2023 15:19:56 [nginx ] nginx: [emerg] bind() to 0.0.0.0:8181 failed (98: Address in use) 03/07/2023 15:19:57 [nginx ] nginx: [emerg] bind() to 0.0.0.0:8181 failed (98: Address in use) 03/07/2023 15:19:57 [nginx ] nginx: [emerg] bind() to 0.0.0.0:8181 failed (98: Address in use) 03/07/2023 15:19:58 [nginx ] nginx: [emerg] still could not bind() 03/07/2023 15:19:58 [supervisor ] service 'nginx' exited (with status 1). 03/07/2023 15:19:58 [supervisor ] restarting service 'nginx'. 03/07/2023 15:19:58 [supervisor ] starting service 'nginx'... but I got nothing that run on port 8181 on my server And now nothing at all is working --- I tried to use host network type and despite setting other WebUI/HTTP/HTTPS ports, it only use 4443, 8080, 8181 no matter what I do ... Edited July 4, 2023 by kasuke Quote Link to comment
kasuke Posted July 6, 2023 Share Posted July 6, 2023 re installation solve all my issue Quote Link to comment
explosionhole Posted July 6, 2023 Share Posted July 6, 2023 6th July 2023 Updated Unraid to 6.12.2 last week. Upon reboot, I cannot start my core container, NPM. My other core containers do start, such as a database container, password vault container, etc. I see in the system logs, NPM wants port 443, but is in use. I never had this problem before. There is an O/S-level Nginx instance running that is using 443. If it isn't created by the Unraid UI, I do not know what it is. Nor why the config changed to take this port. This would affect anyone attempting to bind this port to a Docker platform running inside the core O/S. It is an O/S-native service, by my initial view. If I try to manually start the NPM container, it prompts "Execution error" Updated Unraid to 6.12.2 this past week. Upon reboot, I cannot start my core container, NPM. My other core containers do start, such as a database container, password vault container, etc. I see in the system logs, NPM wants port 443, but is in use. I never had this problem before. There is an O/S-level Nginx instance running that is using 443. If it isn't created by the Unraid UI, I do not know what it is. Nor why the config changed to take this port. This would affect anyone attempting to bind this port to a Docker platform running inside the core O/S. It is an O/S-native service, by my initial view. If I try to manually start the NPM container, it prompts "Execution error". Forum posts from many years ago suggest editing a `/config/go` but the parameter no longer exists. tower-diagnostics-20230705-2341.zip Quote Link to comment
mgutt Posted July 7, 2023 Author Share Posted July 7, 2023 18 hours ago, explosionhole said: NPM wants port 443, but is in use. Yes, this seems to be a new behavior of unRAID. See the other posts. unRAID opens Port 443 by default, now. Quote Link to comment
Nothingtoxic Posted July 7, 2023 Share Posted July 7, 2023 noticed this morning i had issues with unraid and after noticing that my dockers werent seen externally checked npm and getting these error ❯ Starting nginx ... nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-18/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-18/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) its like overnight its just deleted my nginx files ? as it was fully working when i went to sleep Quote Link to comment
mgutt Posted July 7, 2023 Author Share Posted July 7, 2023 2 hours ago, Nothingtoxic said: its like overnight its just deleted my nginx files ? Are you using an old version of unRAID? There was a bug until 6.11 with moving symbolic links from and to the array. Quote Link to comment
Nothingtoxic Posted July 7, 2023 Share Posted July 7, 2023 4 minutes ago, mgutt said: Are you using an old version of unRAID? There was a bug until 6.11 with moving symbolic links from and to the array. had 6.11.5 before and had this error, update to 6.12.2 and still same error, seems somehow that my nginx docker deleted my cert folder/files for w/e reason so had to remake those files and then remake all my cloduflare certs and now its working as it was before why i have no idea as unraid was not reveresed proxied Quote Link to comment
Joshwaaa Posted July 12, 2023 Share Posted July 12, 2023 I have a brand new setup of unRAID 6.11.5 and I'm only running nginx and nextcloud and pihole. 'm using a cloudflare tunnel. When I'm away from home I am frequently getting a cloudflare host error screen. After a few refreshes I can eventually reach NC. These are the errors from this evening. Any ideas what they mean and how can I solve them? 2023/07/11 16:13:45 [error] 1291#1291: *14225 open() "/var/www/html/index.php" failed (2: No such file or directory), client: 213.109.202.66, server: localhost-nginx-proxy-manager, request: "GET /index.php?s=/Index/\think\app/invokefunction&function=call_user_func_array&vars[0]=md5&vars[1][]=HelloThinkPHP21 HTTP/1.1", host: "50.82.174.108:80" 2023/07/11 17:41:16 [error] 1319#1319: *14744 open() "/var/www/html/manager/text/list" failed (2: No such file or directory), client: 107.170.242.12, server: localhost-nginx-proxy-manager, request: "GET /manager/text/list HTTP/1.1", host: "50.82.174.108" 2023/07/11 17:44:07 [warn] 1319#1319: 512 worker_connections are not enough, reusing connections 2023/07/11 17:44:07 [alert] 1319#1319: 512 worker_connections are not enough 2023/07/11 17:44:07 [error] 1319#1319: *15536 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: localhost-nginx-proxy-manager, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "mealie712.duckdns.org" 2023/07/11 18:24:59 [error] 1347#1347: *15810 "/var/www/html/console/index.html" is not found (2: No such file or directory), client: 213.109.202.66, server: localhost-nginx-proxy-manager, request: "GET /console/ HTTP/1.1", host: "50.82.174.108:80" 2023/07/11 19:18:07 [error] 1375#1375: *16152 open() "/var/www/html/client/get_targets" failed (2: No such file or directory), client: 159.65.119.51, server: localhost-nginx-proxy-manager, request: "GET /client/get_targets HTTP/1.1", host: "50.82.174.108" 2023/07/11 19:18:08 [alert] 1375#1375: 512 worker_connections are not enough 2023/07/11 19:18:08 [error] 1376#1376: *16922 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: localhost-nginx-proxy-manager, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "50.82.174.108" 2023/07/11 19:18:09 [error] 1375#1375: *16924 open() "/var/www/html/1.php" failed (2: No such file or directory), client: 159.65.119.51, server: localhost-nginx-proxy-manager, request: "GET /1.php HTTP/1.1", host: "50.82.174.108" 2023/07/11 19:18:10 [alert] 1375#1375: 512 worker_connections are not enough 2023/07/11 19:18:10 [error] 1375#1375: *17757 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: localhost-nginx-proxy-manager, request: "GET /bundle.js HTTP/1.1", upstream: "http://127.0.0.1:8080/bundle.js", host: "50.82.174.108" 2023/07/11 19:18:12 [error] 1375#1375: *17761 "/var/www/html/files/index.html" is not found (2: No such file or directory), client: 159.65.119.51, server: localhost-nginx-proxy-manager, request: "GET /files/ HTTP/1.1", host: "50.82.174.108" 2023/07/11 21:15:35 [error] 1458#1458: *19372 open() "/var/www/html/actuator/gateway/routes" failed (2: No such file or directory), client: 213.109.202.66, server: localhost-nginx-proxy-manager, request: "GET /actuator/gateway/routes HTTP/1.1", host: "50.82.174.108:80" 2023/07/11 21:18:27 [error] 1458#1458: *19574 "/var/www/html/HNAP1/index.html" is not found (2: No such file or directory), client: 223.130.30.57, server: localhost-nginx-proxy-manager, request: "POST /HNAP1/ HTTP/1.0", host: "50.82.174.108:80" Quote Link to comment
mgutt Posted July 12, 2023 Author Share Posted July 12, 2023 3 hours ago, Joshwaaa said: These are the errors from this evening Where did you found them? Those are not the usual NPM logs. I would say these are random access tries from bots, which are not relevant. 3 hours ago, Joshwaaa said: cloudflare tunnel Does your tunnel work without interruptions? Side note: It's against the Cloudflare TOS to forward non-html traffic through their proxy (which happens with Nextcloud). Quote Link to comment
armin0012002 Posted July 12, 2023 Share Posted July 12, 2023 hi running nginx on unraid I can access app.domain.com from inside my network but cant get access from outside any pointer ? Quote Link to comment
Joshwaaa Posted July 12, 2023 Share Posted July 12, 2023 4 hours ago, mgutt said: Where did you found them? Those are not the usual NPM logs. @mgutt Network/server/appdata/nginxproxymanager/logs/fallback_error 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.