Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Nginx Proxy Manager Docker: Unraid nicht mehr erreichbar

Avenga
in Deutsch

Featured Replies

Hallo, ich habe den Nginx Proxy Manager (NPM) Official installiert und die drei Ports auf 8000er Bereich vor der Installation gesetzt.

Dann installiert, es wurden zig Dateien runter geladen, dann kam nichts mehr. Nach 5min habe ich dann mal auf "Docker" geklickt, da passierte auch nichts.

Seit dem reagiert mein Unraid WebUI gar nicht mehr.

Bitte um Hilfe.

 

 

  • Quote
    • Author

    Entwarnung: nach 15min Warten wieder erreichbar, man ich hab mir schon fast in die Hose gemacht  😶

  • Quote

    Während ein Docker installiert wird, reagiert die WebUI nicht. Wenn du ein etwas langsameres System hast, kann das schon mal was dauern ^^

  • Quote
    • Author

    Eigentlich nicht, die anderen Docker dauerten paar Sekunden zu installieren und nicht über 10min wie Nginx Reverse Proxy.

    Intel® Core™ i5-8400T mit 32GB Ram.

     

    Im Syslog habe ich folgendes entdeckt zu der Uhrzeit: 

    Jan  1 21:19:14 Unraid monitor: Stop running nchan processes
Jan  1 21:29:37 Unraid nginx: 2024/01/01 21:29:37 [error] 7190#7190: *2750427 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.168.4"
Jan  1 21:29:37 Unraid nginx: 2024/01/01 21:29:37 [error] 7190#7190: *2750427 auth request unexpected status: 504 while sending to client, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.168.4"
Jan  1 21:29:58 Unraid nginx: 2024/01/01 21:29:58 [error] 7190#7190: *2750554 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.168.4"
Jan  1 21:29:58 Unraid nginx: 2024/01/01 21:29:58 [error] 7190#7190: *2750554 auth request unexpected status: 504 while sending to client, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.168.4"
Jan  1 21:30:20 Unraid nginx: 2024/01/01 21:30:20 [error] 7190#7190: *2750588 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.168.4"
Jan  1 21:30:20 Unraid nginx: 2024/01/01 21:30:20 [error] 7190#7190: *2750588 auth request unexpected status: 504 while sending to client, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.168.4"
Jan  1 21:30:41 Unraid nginx: 2024/01/01 21:30:41 [error] 7190#7190: *2750618 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.168.4"
Jan  1 21:30:41 Unraid nginx: 2024/01/01 21:30:41 [error] 7190#7190: *2750618 auth request unexpected status: 504 while sending to client, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.168.4"
Jan  1 21:31:02 Unraid nginx: 2024/01/01 21:31:02 [error] 7190#7190: *2750646 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.168.4"
Jan  1 21:31:02 Unraid nginx: 2024/01/01 21:31:02 [error] 7190#7190: *2750646 auth request unexpected status: 504 while sending to client, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.168.4"
Jan  1 21:31:23 Unraid nginx: 2024/01/01 21:31:23 [error] 7190#7190: *2750674 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.168.4"
Jan  1 21:31:23 Unraid nginx: 2024/01/01 21:31:23 [error] 7190#7190: *2750674 auth request unexpected status: 504 while sending to client, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.168.4"
Jan  1 21:40:17 Unraid nginx: 2024/01/01 21:40:17 [error] 7190#7190: *2751393 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.168.4"
Jan  1 21:40:17 Unraid nginx: 2024/01/01 21:40:17 [error] 7190#7190: *2751393 auth request unexpected status: 504 while sending to client, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.168.4"
Jan  1 21:40:38 Unraid nginx: 2024/01/01 21:40:38 [error] 7190#7190: *2751422 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.168.4"
Jan  1 21:40:38 Unraid nginx: 2024/01/01 21:40:38 [error] 7190#7190: *2751422 auth request unexpected status: 504 while sending to client, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.168.4"
Jan  1 21:41:00 Unraid nginx: 2024/01/01 21:41:00 [error] 7190#7190: *2751452 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.168.4"
Jan  1 21:41:00 Unraid nginx: 2024/01/01 21:41:00 [error] 7190#7190: *2751452 auth request unexpected status: 504 while sending to client, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.168.4"
Jan  1 21:41:21 Unraid nginx: 2024/01/01 21:41:21 [error] 7190#7190: *2751483 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.168.4"
Jan  1 21:41:21 Unraid nginx: 2024/01/01 21:41:21 [error] 7190#7190: *2751483 auth request unexpected status: 504 while sending to client, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.168.4"
Jan  1 21:41:42 Unraid nginx: 2024/01/01 21:41:42 [error] 7190#7190: *2751513 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.168.4"
Jan  1 21:41:42 Unraid nginx: 2024/01/01 21:41:42 [error] 7190#7190: *2751513 auth request unexpected status: 504 while sending to client, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.168.4"
Jan  1 21:42:03 Unraid nginx: 2024/01/01 21:42:03 [error] 7190#7190: *2751540 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.168.4"
Jan  1 21:42:03 Unraid nginx: 2024/01/01 21:42:03 [error] 7190#7190: *2751540 auth request unexpected status: 504 while sending to client, client: 192.168.168.20, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.168.4"
Jan  1 21:42:14 Unraid kernel: docker0: port 3(vethd62a554) entered blocking state
Jan  1 21:42:14 Unraid kernel: docker0: port 3(vethd62a554) entered disabled state
Jan  1 21:42:14 Unraid kernel: device vethd62a554 entered promiscuous mode
Jan  1 21:42:15 Unraid kernel: eth0: renamed from vethf833507
Jan  1 21:42:15 Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jan  1 21:42:15 Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd62a554: link becomes ready
Jan  1 21:42:15 Unraid kernel: docker0: port 3(vethd62a554) entered blocking state
Jan  1 21:42:15 Unraid kernel: docker0: port 3(vethd62a554) entered forwarding state

     

    muss ich mir Sorgen machen?

     

  • Quote
    • Author

    Frage: Wie sicher ist der NPM ?

    ich habe NodeRed & Grafana eingerichtet, so dass jeder auf der Welt wie folgt rein kommt: xy.meinedomain.net -> nutzername / abcdefg12

    können das Hacker bzw. Bots einfach per brute force knacken (falls sie meine Subdomain herausfinden) oder gibt es im NPM Sicherheitsmechanismen dagegen? (habe mal was von fail2bann gehört in anderem Zusammenhang)

  • Quote

    • 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.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.