July 12, 20232 yr Author 10 hours ago, armin0012002 said: hi running nginx on unraid I can access app.domain.com from inside my network but cant get access from outside any pointer ? Read the first page or view some YouTube Tutorials.
July 13, 20232 yr 13 hours ago, mgutt said: Read the first page or view some YouTube Tutorials. i did and watched to many videos problem is cant get trough nginx from outside asked my isp 2 times already if port 80 and 443 is close and they said not blocking any ports
July 13, 20232 yr 1 hour ago, armin0012002 said: i did and watched to many videos problem is cant get trough nginx from outside asked my isp 2 times already if port 80 and 443 is close and they said not blocking any ports Did your ISP put you on CGNAT?
July 13, 20232 yr 1 hour ago, flosken said: Did your ISP put you on CGNAT? not sure so I manage run my services with cloudflare tunnel and and redirect my cache from tunnel . i reckon thats time for new internet provider
July 14, 20232 yr Hi, I got the following setup: Pi-Hole custom network br0 fixed IP adress 192.168.178.100 NPM custom network br0 fixed IP address 192.168.178.101 I think I made a mistake in my configuration but I can't see what's wrong. When I call the domain I get a 502: 2023/07/14 12:34:12 [error] 22183#22183: *9 connect() failed (113: No route to host) while connecting to upstream, client: 192.168.178.2, server: jellyfin.nas, request: "GET / HTTP/1.1", upstream: "http://192.168.178.3:8096/", host: "jellyfin.nas"
July 14, 20232 yr 28 minutes ago, Kilrah said: And what's Jellyfin on? It's on 192.168.178.3:8096 like it's shown in the proxy host.
July 14, 20232 yr Author 1 hour ago, dunn said: like it's shown in the proxy host. He asked for the network type. Bridge, Host, custom, br0... Some networks can't reach each other.
July 14, 20232 yr 2 hours ago, mgutt said: He asked for the network type. Bridge, Host, custom, br0... Some networks can't reach each other. It's bridged but with host it's the same. But it seems you are right, I can't reach 192.168.178.3 from the NPM container. Is there a way to make it reachable from the container? Edit: Ok I found it. I changed to macvlan and granted host access to custom networks. It now works Edited July 14, 20232 yr by dunn
July 27, 20232 yr I also have NGINX Proxy Manager on a second Unraid. Option "Force SSL" break websites/unreachable. Does anyone know the problem?
July 28, 20232 yr Hi is there an Issue with VNC support? I just moved from SWAG to NginX Proxy.. everything workes perfect, SSL Certificate, Nextcloud.. boom.. realy Nice ! only my Doccers with VNC have some issues.. i am able to reach the First site.. than click on vnc.html <-- no Connection possible.. if i change it to HTTPS, i get an 5xx error.. What is the Issue i am doing wrong? Edited July 28, 20232 yr by eLpresidente
July 28, 20232 yr Author 1 hour ago, eLpresidente said: What is the Issue i am doing wrong? At first: It is not a good idea to make this public as this VNC connection has access to the BIOS of the VM. So if it restarts, someone could be able to open the boot manager and kill the VM and/or access sensible data inside the VM or even install own stuff. It is like to leave a Notebook at the next bus station while hoping nothing will go wrong. It would be better to install a remote access software inside the VM (Teamviewer, Real VNC, Chrome Remote Desktop. etc) which work without port forwarding. Or join the server to a virtual network like Zerotier. Or setup a VPN connection to your router. I'm using for example Wireguard to connect to my router. 1 hour ago, eLpresidente said: no Connection possible Did you enable Websocket support for the NoVNC proxy host? This is required. Did you check your browser network developer tools? Maybe it returns an error message.
July 28, 20232 yr 18 minutes ago, mgutt said: At first: It is not a good idea to make this public as this VNC connection is it enough to protect it with Accesslist from NPM ? if not i can do it with Wireshark, its already setup 18 minutes ago, mgutt said: Did you enable Websocket support for the NoVNC proxy host? Thx, that was the solution to this
August 14, 20232 yr Hi I am getting this error from time to time: unraid nginx EHOSTUNREACH 42.88.72.3:443 I don't know why or what it fixes. I have had this for about 3 weeks. Suddenly the server is louder than usual and I can't get on it. Not via GUI, not via SSH. One time I was able to access the server via SSH and saw through "top" that nginx ate the whole CPU. So I have to turn the server off hard and on again. After that I get this message on NGINX. Sometimes it goes away when I disable the Docker services and enable them again. But sometimes it doesn't, then I completely rebuild nginx Docker and set up everything for it again too.... Since I have to shut down the server hard, I can't get to the logs at that moment either. Does anyone know what could be the reason for this? I thought it was because of my DNS, I changed it especially for this, but it didn't work. The other containers ran without problems
August 22, 20232 yr Hey all, I bought a new domain to use for internal-only routing... to prettify urls to internal services. I am using Unifi with a PiHole as DNS server and I set up NGINX Proxy Manager. Publically, I set the A-Record for my domain to be the internal IP of the PiHole server. On PiHole, I created a record for domainname.com -> {Internal IP of NPM}. When I ping my domain internally, I get the NPM servers IP and I can navigate to the NPM server using the domain name. I was able to use NPM to get a cert for *.domainname.com with little issue (a bit of troubleshooting needed.) I set a host entry for watch.domainname.com and set the IP:Port to be for my Jellyfin server. When I navigate to it, I get ERR_CONNECTION_REFUSED though. I'm really at a loss for how to troubleshoot this further. The one thing I am wondering though is: Does NPM and other docker containers need to all be in the same docker network? NPM is in a network where it gets a unique IP on network while all my other containers just use {UnraidIP}:{UniquePort}. Any advice would be greatly appreciated.
August 23, 20232 yr If it's internal only you can use whatever domain name you want over http without even buying it. Containers on br0 cannot reach the server's IP unless you enable "Host access to custom networks" in Docker settings. You typically want NPM either on a bridge with the other containers it needs to route to or on Host for it to be able to access everything, for local access the latter, which requires you to change the ports for unraid's GUI. Edited August 23, 20232 yr by Kilrah
August 27, 20232 yr I'm having an issue with accessing Frigate via NPM with IOS devices. It works perfectly with Windows and Android after I enter my credentials. On the other hand with IOS it endlessly asks for my credentials on both Safari and Chrome. I've tested 2 iphones. Any suggestions?
August 27, 20232 yr 2 hours ago, BlackAndChrome said: On the other hand with IOS it endlessly asks for my credentials on both Safari and Chrome. I've tested 2 iphones. Any suggestions? throw the ios devices away just kidding ... well, as you figured its an ios issue only, i would suggest to open a ticket at NPM ... like here https://github.com/NginxProxyManager/nginx-proxy-manager
August 27, 20232 yr Author 4 hours ago, BlackAndChrome said: On the other hand with IOS it endlessly asks for my credentials on both Safari and Chrome Try to disable the privacy option which sets random Mac Adresses in your home wifi. Maybe you get very often a new IP Adress from your router?! Or are you using a local DNS / AdBlock service which could influence this? Did you try with incognito tab?
August 27, 20232 yr 8 hours ago, alturismo said: throw the ios devices away just kidding ... well, as you figured its an ios issue only, i would suggest to open a ticket at NPM ... like here https://github.com/NginxProxyManager/nginx-proxy-manager I keep telling my wife/mother that but no luck so far. Instead I get things working on my hardware and wind up spending 3x as much time troubleshooting a platform that I didn't choose, don't know how to use proficiently, and prefer not to even look at 😩. I'll dig through the issues and see if anything rings a bell. 6 hours ago, mgutt said: Try to disable the privacy option which sets random Mac Adresses in your home wifi. Maybe you get very often a new IP Adress from your router?! Or are you using a local DNS / AdBlock service which could influence this? Did you try with incognito tab? May be worth noting that I have this issue both from LAN and WAN. In pfSense the DHCP lease seems to be pretty standard for local. No indication that the traffic is getting blocked by pf blocker or snort. I tried incognito and no luck. The more I look at it the more it seems to be related to the live streams. I can log into the main interface (enter credentials twice initially), click on a camera to view live, cancel or enter creds (results in feed or no feed), navigate to events (even view old event footage) or back to the main page, but as soon as I go to a camera live feed (even the same one as before) it prompts again.
September 3, 20232 yr Ran into an issue after the Unraid upgrade to 6.12.4 with Nginx. When I try to browse to the local installation, I get 'ERR_CONNECTION_REFUSED' in all browsers. It's the only docker that's giving me this issue but I cannot get it to come back online. I tried restoring a backup but it was unsuccessful. I've attached a screenshot of my config, and a screenshot of the docker log. Any and all help would be appreciated. Edited September 4, 20232 yr by jackfalveyiv
September 4, 20232 yr I hope that this is the correct forum. My guess is that I am using wrong NPM setting this is why... Just migrated from SWAG to NPM, all guides on page #1 have been read and the tests went well. DDNS and DNS settings (CNAME) are managed by all-inkl.com. I can reach calibre and emby dockers by using e.g. emby.mynetwork.com. Nextcloud is accessible under mynetwork.com. I have defined collabora.mynetwork.com but I can't open any files. This is not a surprise because Nextcloud isn't accepting the address collabora.mynetwork.com (Es konnte keine Verbindung zum Collabora Online-Server hergestellt werden). Some details: Nextcloud is the lsio docker which is based on alpine, hence can't use the integrated COLLABORA CODE. NPM - I was using the advanced setting from here: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/70 Collabora docker is showin OK by using entering collabora.mynetwork.com All dockers are BRIDGE Has anyone a well running setup using the same dockers? Nextcloud error: [richdocuments] Fehler: GuzzleHttp\Exception\ConnectException: cURL error 28: Connection timed out after 45001 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://collabora.mynetwork.com:9980/hosting/capabilities at <<closure>> 0. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php line 158 GuzzleHttp\Handler\CurlFactory::createRejection("*** sensitive parameters replaced ***") 1. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php line 110 GuzzleHttp\Handler\CurlFactory::finishError() 2. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Handler/CurlHandler.php line 47 GuzzleHttp\Handler\CurlFactory::finish() 3. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Middleware.php line 137 GuzzleHttp\Handler\CurlHandler->__invoke() 4. /app/www/public/lib/private/Http/Client/DnsPinMiddleware.php line 114 GuzzleHttp\Middleware::GuzzleHttp\{closure}("*** sensitive parameters replaced ***") 5. /app/www/public/3rdparty/guzzlehttp/guzzle/src/PrepareBodyMiddleware.php line 35 OC\Http\Client\DnsPinMiddleware->OC\Http\Client\{closure}("*** sensitive parameters replaced ***") 6. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Middleware.php line 31 GuzzleHttp\PrepareBodyMiddleware->__invoke() 7. /app/www/public/3rdparty/guzzlehttp/guzzle/src/RedirectMiddleware.php line 71 GuzzleHttp\Middleware::GuzzleHttp\{closure}("*** sensitive parameters replaced ***") 8. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Middleware.php line 63 GuzzleHttp\RedirectMiddleware->__invoke() 9. /app/www/public/3rdparty/guzzlehttp/guzzle/src/HandlerStack.php line 75 GuzzleHttp\Middleware::GuzzleHttp\{closure}("*** sensitive parameters replaced ***") 10. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Client.php line 331 GuzzleHttp\HandlerStack->__invoke() 11. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Client.php line 168 GuzzleHttp\Client->transfer() 12. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Client.php line 187 GuzzleHttp\Client->requestAsync("*** sensitive parameters replaced ***") 13. /app/www/public/lib/private/Http/Client/Client.php line 226 GuzzleHttp\Client->request() 14. /config/www/nextcloud/apps/richdocuments/lib/Service/CapabilitiesService.php line 135 OC\Http\Client\Client->get() 15. /config/www/nextcloud/apps/richdocuments/lib/Service/CapabilitiesService.php line 73 OCA\Richdocuments\Service\CapabilitiesService->refetch() 16. /config/www/nextcloud/apps/richdocuments/lib/AppInfo/Application.php line 90 OCA\Richdocuments\Service\CapabilitiesService->getCapabilities() 17. /app/www/public/lib/private/AppFramework/Bootstrap/FunctionInjector.php line 45 OCA\Richdocuments\AppInfo\Application->OCA\Richdocuments\AppInfo\{closure}("*** sensitive parameters replaced ***") 18. /app/www/public/lib/private/AppFramework/Bootstrap/BootContext.php line 50 OC\AppFramework\Bootstrap\FunctionInjector->injectFn() 19. /config/www/nextcloud/apps/richdocuments/lib/AppInfo/Application.php line 89 OC\AppFramework\Bootstrap\BootContext->injectFn() 20. /app/www/public/lib/private/AppFramework/Bootstrap/Coordinator.php line 200 OCA\Richdocuments\AppInfo\Application->boot() 21. /app/www/public/lib/private/App/AppManager.php line 437 OC\AppFramework\Bootstrap\Coordinator->bootApp() 22. /app/www/public/lib/private/App/AppManager.php line 216 OC\App\AppManager->loadApp() 23. /app/www/public/lib/private/legacy/OC_App.php line 126 OC\App\AppManager->loadApps() 24. /app/www/public/ocs/v1.php line 58 OC_App::loadApps() 25. /app/www/public/ocs/v2.php line 23 require_once("/app/www/public/ocs/v1.php") GET /ocs/v2.php/apps/notifications/api/v2/notifications from 194.191.235.184 by oliver at 2023-09-04T13:05:01+02:00 I fixed my Nextcloud/Collabora integration issues with the guide I found here: https://help.nextcloud.com/t/nextcloud-collabora-integration/151879 Edited September 11, 20232 yr by EdgarWallace Solved
September 4, 20232 yr 23 hours ago, jackfalveyiv said: Ran into an issue after the Unraid upgrade to 6.12.4 with Nginx. When I try to browse to the local installation, I get 'ERR_CONNECTION_REFUSED' in all browsers. It's the only docker that's giving me this issue but I cannot get it to come back online. I tried restoring a backup but it was unsuccessful. I've attached a screenshot of my config, and a screenshot of the docker log. Any and all help would be appreciated. Some additional context in the attached screenshot. I see what looks like an IP address conflict, but I can't see one in my docker allocations, either for port or IP.
September 4, 20232 yr 3 hours ago, jackfalveyiv said: Some additional context in the attached screenshot. I see what looks like an IP address conflict, but I can't see one in my docker allocations, either for port or IP. Just following up in case anyone has an issue like mine. I don't have an explanation for why this worked, but I wiped out the nginx docker and installed another instance, pointing to the same appdata directory, and things are working just as they had been before. If anyone has upgraded the OS, or downgraded, and runs into this, try my fix and see if that helps.
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.