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.

Docker via nginx nicht mehr via domain erreichbar, aber VM

Featured Replies

Guten Morgen zusammen,

ich kämpfe gerade mit dem Problem, dass meine Docker via nginx nicht mehr von außerhalb erreichbar via domain sind. 
Der nginx läuft via docker und hat eine Freigabe im Router.

 

Parallel zu meinem Docker System läuft noch eine VM, diese ist komischerweise via nginx von außen erreichbar ohne Probleme.

 

Bei mir läuft unraid 7.0.0. mit dem Patch. 

Hat jemand eine Idee? Ich bin gerade tatsächlich ratlos.

 

Viele Grüße

1 hour ago, LyDjane said:

Hat jemand eine Idee? Ich bin gerade tatsächlich ratlos.

 

mit der Beschreibung wird es auch schwer, aber ich rate mal ...

 

Settings, Docker, advanced (oben rechts aktivieren), host access aktiv ?

  • Author

Guten Morgen zusammen,

 

Fehler gefunden. Die Bridge war seitens unRaid deaktiviert. Lag wahrscheinlich am BIOS Update heute Nacht.

  • Author

Problem wieder vorhanden. Bridge ist aktiviert.

Es scheint definitiv ein Bridge Problem zu sein.
ich bin aber völlig ratlos, was ich machen kann.

 

  • Author

Guten Morgen,

es gibt Neuigkeiten.

Es liegt definitiv am "bridge" mode. Sobald die Docker im br0 mit fester IP sind, klappt es tadellos.

 

Aus dem Logs konnte ich folgendes entnehmen:

Feb  2 02:54:01 unRAID-Server kernel: vethddf336f: renamed from eth0
Feb  2 02:54:04 unRAID-Server kernel: eth0: renamed from vetheca6da9
Feb  2 02:54:15 unRAID-Server kernel: docker0: port 23(veth209ce11) entered disabled state
Feb  2 02:54:15 unRAID-Server kernel: veth68d72f3: renamed from eth0
Feb  2 02:54:15 unRAID-Server kernel: docker0: port 23(veth209ce11) entered disabled state
Feb  2 02:54:15 unRAID-Server kernel: veth209ce11 (unregistering): left allmulticast mode
Feb  2 02:54:15 unRAID-Server kernel: veth209ce11 (unregistering): left promiscuous mode
Feb  2 02:54:15 unRAID-Server kernel: docker0: port 23(veth209ce11) entered disabled state
Feb  2 02:54:15 unRAID-Server kernel: docker0: port 21(veth3ce171c) entered blocking state
Feb  2 02:54:15 unRAID-Server kernel: docker0: port 21(veth3ce171c) entered disabled state
Feb  2 02:54:15 unRAID-Server kernel: veth3ce171c: entered allmulticast mode
Feb  2 02:54:15 unRAID-Server kernel: veth3ce171c: entered promiscuous mode
Feb  2 02:54:15 unRAID-Server kernel: docker0: port 21(veth3ce171c) entered blocking state
Feb  2 02:54:15 unRAID-Server kernel: docker0: port 21(veth3ce171c) entered forwarding state
Feb  2 02:54:15 unRAID-Server kernel: eth0: renamed from vethd456705
Feb  2 02:54:29 unRAID-Server kernel: docker0: port 20(vethfa803bf) entered disabled state
Feb  2 02:54:29 unRAID-Server kernel: veth219fecc: renamed from eth0
Feb  2 02:54:29 unRAID-Server kernel: docker0: port 20(vethfa803bf) entered disabled state
Feb  2 02:54:29 unRAID-Server kernel: vethfa803bf (unregistering): left allmulticast mode
Feb  2 02:54:29 unRAID-Server kernel: vethfa803bf (unregistering): left promiscuous mode
Feb  2 02:54:29 unRAID-Server kernel: docker0: port 20(vethfa803bf) entered disabled state
Feb  2 02:54:57 unRAID-Server kernel: docker0: port 20(veth287a590) entered blocking state
Feb  2 02:54:57 unRAID-Server kernel: docker0: port 20(veth287a590) entered disabled state
Feb  2 02:54:57 unRAID-Server kernel: veth287a590: entered allmulticast mode
Feb  2 02:54:57 unRAID-Server kernel: veth287a590: entered promiscuous mode
Feb  2 02:54:57 unRAID-Server kernel: eth0: renamed from veth9ab4a32
Feb  2 02:54:57 unRAID-Server kernel: docker0: port 20(veth287a590) entered blocking state
Feb  2 02:54:57 unRAID-Server kernel: docker0: port 20(veth287a590) entered forwarding state
Feb  2 02:55:11 unRAID-Server kernel: vethdabe7fb: renamed from eth0
Feb  2 02:55:11 unRAID-Server kernel: docker0: port 19(veth41c2efd) entered disabled state
Feb  2 02:55:11 unRAID-Server kernel: docker0: port 19(veth41c2efd) entered disabled state
Feb  2 02:55:11 unRAID-Server kernel: veth41c2efd (unregistering): left allmulticast mode
Feb  2 02:55:11 unRAID-Server kernel: veth41c2efd (unregistering): left promiscuous mode
Feb  2 02:55:11 unRAID-Server kernel: docker0: port 19(veth41c2efd) entered disabled state
Feb  2 02:55:37 unRAID-Server kernel: docker0: port 19(veth6e55e10) entered blocking state
Feb  2 02:55:37 unRAID-Server kernel: docker0: port 19(veth6e55e10) entered disabled state
Feb  2 02:55:37 unRAID-Server kernel: veth6e55e10: entered allmulticast mode
Feb  2 02:55:37 unRAID-Server kernel: veth6e55e10: entered promiscuous mode
Feb  2 02:55:37 unRAID-Server kernel: eth0: renamed from veth26b8a31
Feb  2 02:55:37 unRAID-Server kernel: docker0: port 19(veth6e55e10) entered blocking state
Feb  2 02:55:37 unRAID-Server kernel: docker0: port 19(veth6e55e10) entered forwarding state
Feb  2 02:55:48 unRAID-Server kernel: docker0: port 11(veth2dfebbf) entered disabled state
Feb  2 02:55:48 unRAID-Server kernel: veth97ba28d: renamed from eth0
Feb  2 02:55:48 unRAID-Server kernel: docker0: port 11(veth2dfebbf) entered disabled state
Feb  2 02:55:48 unRAID-Server kernel: veth2dfebbf (unregistering): left allmulticast mode
Feb  2 02:55:48 unRAID-Server kernel: veth2dfebbf (unregistering): left promiscuous mode
Feb  2 02:55:48 unRAID-Server kernel: docker0: port 11(veth2dfebbf) entered disabled state
Feb  2 02:55:48 unRAID-Server kernel: docker0: port 11(veth4e8d63e) entered blocking state
Feb  2 02:55:48 unRAID-Server kernel: docker0: port 11(veth4e8d63e) entered disabled state
Feb  2 02:55:48 unRAID-Server kernel: veth4e8d63e: entered allmulticast mode
Feb  2 02:55:48 unRAID-Server kernel: veth4e8d63e: entered promiscuous mode
Feb  2 02:55:48 unRAID-Server kernel: docker0: port 11(veth4e8d63e) entered blocking state
Feb  2 02:55:48 unRAID-Server kernel: docker0: port 11(veth4e8d63e) entered forwarding state
Feb  2 02:55:49 unRAID-Server kernel: eth0: renamed from veth9ce9c73
Feb  2 02:55:59 unRAID-Server kernel: docker0: port 9(vethd8ac066) entered disabled state
Feb  2 02:55:59 unRAID-Server kernel: veth2a3b095: renamed from eth0
Feb  2 02:55:59 unRAID-Server kernel: docker0: port 9(vethd8ac066) entered disabled state
Feb  2 02:55:59 unRAID-Server kernel: vethd8ac066 (unregistering): left allmulticast mode
Feb  2 02:55:59 unRAID-Server kernel: vethd8ac066 (unregistering): left promiscuous mode
Feb  2 02:55:59 unRAID-Server kernel: docker0: port 9(vethd8ac066) entered disabled state
Feb  2 02:55:59 unRAID-Server kernel: docker0: port 9(vethbca94b9) entered blocking state
Feb  2 02:55:59 unRAID-Server kernel: docker0: port 9(vethbca94b9) entered disabled state
Feb  2 02:55:59 unRAID-Server kernel: vethbca94b9: entered allmulticast mode
Feb  2 02:55:59 unRAID-Server kernel: vethbca94b9: entered promiscuous mode
Feb  2 02:55:59 unRAID-Server kernel: docker0: port 9(vethbca94b9) entered blocking state
Feb  2 02:55:59 unRAID-Server kernel: docker0: port 9(vethbca94b9) entered forwarding state
Feb  2 02:56:00 unRAID-Server kernel: eth0: renamed from veth81f1d12
Feb  2 02:56:14 unRAID-Server kernel: docker0: port 1(veth6bcb38f) entered disabled state
Feb  2 02:56:14 unRAID-Server kernel: veth4ad328e: renamed from eth0
Feb  2 02:56:14 unRAID-Server kernel: docker0: port 1(veth6bcb38f) entered disabled state
Feb  2 02:56:14 unRAID-Server kernel: veth6bcb38f (unregistering): left allmulticast mode
Feb  2 02:56:14 unRAID-Server kernel: veth6bcb38f (unregistering): left promiscuous mode
Feb  2 02:56:14 unRAID-Server kernel: docker0: port 1(veth6bcb38f) entered disabled state
Feb  2 02:56:36 unRAID-Server kernel: docker0: port 1(veth5a11570) entered blocking state
Feb  2 02:56:36 unRAID-Server kernel: docker0: port 1(veth5a11570) entered disabled state
Feb  2 02:56:36 unRAID-Server kernel: veth5a11570: entered allmulticast mode
Feb  2 02:56:36 unRAID-Server kernel: veth5a11570: entered promiscuous mode
Feb  2 02:56:37 unRAID-Server kernel: eth0: renamed from vetha578426
Feb  2 02:56:37 unRAID-Server kernel: docker0: port 1(veth5a11570) entered blocking state
Feb  2 02:56:37 unRAID-Server kernel: docker0: port 1(veth5a11570) entered forwarding state
Feb  2 02:56:41 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 0 before use
Feb  2 02:57:39 unRAID-Server kernel: docker0: port 3(vethe663fb4) entered disabled state
Feb  2 02:57:39 unRAID-Server kernel: veth36c5243: renamed from eth0
Feb  2 02:57:39 unRAID-Server kernel: docker0: port 3(vethe663fb4) entered disabled state
Feb  2 02:57:39 unRAID-Server kernel: vethe663fb4 (unregistering): left allmulticast mode
Feb  2 02:57:39 unRAID-Server kernel: vethe663fb4 (unregistering): left promiscuous mode
Feb  2 02:57:39 unRAID-Server kernel: docker0: port 3(vethe663fb4) entered disabled state
Feb  2 02:58:47 unRAID-Server kernel: docker0: port 3(veth8f764c8) entered blocking state
Feb  2 02:58:47 unRAID-Server kernel: docker0: port 3(veth8f764c8) entered disabled state
Feb  2 02:58:47 unRAID-Server kernel: veth8f764c8: entered allmulticast mode
Feb  2 02:58:47 unRAID-Server kernel: veth8f764c8: entered promiscuous mode
Feb  2 02:58:48 unRAID-Server kernel: eth0: renamed from vetha9bf300
Feb  2 02:58:48 unRAID-Server kernel: docker0: port 3(veth8f764c8) entered blocking state
Feb  2 02:58:48 unRAID-Server kernel: docker0: port 3(veth8f764c8) entered forwarding state
Feb  2 02:59:50 unRAID-Server kernel: docker0: port 2(veth321688a) entered disabled state
Feb  2 02:59:50 unRAID-Server kernel: vethd3a6eec: renamed from eth0
Feb  2 02:59:50 unRAID-Server kernel: docker0: port 2(veth321688a) entered disabled state
Feb  2 02:59:50 unRAID-Server kernel: veth321688a (unregistering): left allmulticast mode
Feb  2 02:59:50 unRAID-Server kernel: veth321688a (unregistering): left promiscuous mode
Feb  2 02:59:50 unRAID-Server kernel: docker0: port 2(veth321688a) entered disabled state
Feb  2 03:01:09 unRAID-Server kernel: docker0: port 2(veth34c5e36) entered blocking state
Feb  2 03:01:09 unRAID-Server kernel: docker0: port 2(veth34c5e36) entered disabled state
Feb  2 03:01:09 unRAID-Server kernel: veth34c5e36: entered allmulticast mode
Feb  2 03:01:09 unRAID-Server kernel: veth34c5e36: entered promiscuous mode
Feb  2 03:01:09 unRAID-Server kernel: docker0: port 2(veth34c5e36) entered blocking state
Feb  2 03:01:09 unRAID-Server kernel: docker0: port 2(veth34c5e36) entered forwarding state
Feb  2 03:01:09 unRAID-Server kernel: docker0: port 2(veth34c5e36) entered disabled state
Feb  2 03:01:09 unRAID-Server kernel: eth0: renamed from veth112b2c6
Feb  2 03:01:09 unRAID-Server kernel: docker0: port 2(veth34c5e36) entered blocking state
Feb  2 03:01:09 unRAID-Server kernel: docker0: port 2(veth34c5e36) entered forwarding state

 

 

Weiterhin habe ich unzählige Einträge im Log mit:

Feb  2 03:25:09 unRAID-Server kernel: usb 1-5: usbfs: process 13008 (CPU 0/KVM) did not claim interface 0 before use
Feb  2 03:25:19 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 0 before use
Feb  2 03:26:41 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 1 before use
Feb  2 03:26:41 unRAID-Server kernel: usb 1-5: usbfs: process 13008 (CPU 0/KVM) did not claim interface 0 before use
Feb  2 03:26:41 unRAID-Server kernel: usb 1-5: usbfs: process 13008 (CPU 0/KVM) did not claim interface 0 before use
Feb  2 03:26:51 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 0 before use
Feb  2 03:28:12 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 0 before use
Feb  2 03:28:12 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 1 before use
Feb  2 03:28:12 unRAID-Server kernel: usb 1-5: usbfs: process 13008 (CPU 0/KVM) did not claim interface 0 before use
Feb  2 03:28:22 unRAID-Server kernel: usb 1-5: usbfs: process 13008 (CPU 0/KVM) did not claim interface 0 before use
Feb  2 03:29:44 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 0 before use
Feb  2 03:29:44 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 1 before use
Feb  2 03:29:44 unRAID-Server kernel: usb 1-5: usbfs: process 13008 (CPU 0/KVM) did not claim interface 0 before use
Feb  2 03:29:54 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 0 before use

 

  • Author
On 2/2/2025 at 10:20 AM, LyDjane said:

Weiterhin habe ich unzählige Einträge im Log mit:

Feb  2 03:25:09 unRAID-Server kernel: usb 1-5: usbfs: process 13008 (CPU 0/KVM) did not claim interface 0 before use
Feb  2 03:25:19 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 0 before use
Feb  2 03:26:41 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 1 before use
Feb  2 03:26:41 unRAID-Server kernel: usb 1-5: usbfs: process 13008 (CPU 0/KVM) did not claim interface 0 before use
Feb  2 03:26:41 unRAID-Server kernel: usb 1-5: usbfs: process 13008 (CPU 0/KVM) did not claim interface 0 before use
Feb  2 03:26:51 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 0 before use
Feb  2 03:28:12 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 0 before use
Feb  2 03:28:12 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 1 before use
Feb  2 03:28:12 unRAID-Server kernel: usb 1-5: usbfs: process 13008 (CPU 0/KVM) did not claim interface 0 before use
Feb  2 03:28:22 unRAID-Server kernel: usb 1-5: usbfs: process 13008 (CPU 0/KVM) did not claim interface 0 before use
Feb  2 03:29:44 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 0 before use
Feb  2 03:29:44 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 1 before use
Feb  2 03:29:44 unRAID-Server kernel: usb 1-5: usbfs: process 13008 (CPU 0/KVM) did not claim interface 0 before use
Feb  2 03:29:54 unRAID-Server kernel: usb 1-5: usbfs: process 13009 (CPU 1/KVM) did not claim interface 0 before use

Fehler gefunden. Lag am Zigbee Stick für die HomeAssistant VM. 

 

Weiterhin die Docker Fehler mit der Bridge vorhanden:

Feb  4 02:00:41 unRAID-Server kernel: docker0: port 1(vethea45246) entered disabled state
Feb  4 02:00:41 unRAID-Server kernel: veth2281712: renamed from eth0
Feb  4 02:00:41 unRAID-Server kernel: docker0: port 1(vethea45246) entered disabled state
Feb  4 02:00:41 unRAID-Server kernel: vethea45246 (unregistering): left allmulticast mode
Feb  4 02:00:41 unRAID-Server kernel: vethea45246 (unregistering): left promiscuous mode
Feb  4 02:00:41 unRAID-Server kernel: docker0: port 1(vethea45246) entered disabled state
Feb  4 02:01:19 unRAID-Server kernel: docker0: port 1(veth057f068) entered blocking state
Feb  4 02:01:19 unRAID-Server kernel: docker0: port 1(veth057f068) entered disabled state
Feb  4 02:01:19 unRAID-Server kernel: veth057f068: entered allmulticast mode
Feb  4 02:01:19 unRAID-Server kernel: veth057f068: entered promiscuous mode
Feb  4 02:01:19 unRAID-Server kernel: docker0: port 1(veth057f068) entered blocking state
Feb  4 02:01:19 unRAID-Server kernel: docker0: port 1(veth057f068) entered forwarding state
Feb  4 02:01:19 unRAID-Server kernel: docker0: port 1(veth057f068) entered disabled state
Feb  4 02:01:22 unRAID-Server kernel: eth0: renamed from veth751b980
Feb  4 02:01:22 unRAID-Server kernel: docker0: port 1(veth057f068) entered blocking state
Feb  4 02:01:22 unRAID-Server kernel: docker0: port 1(veth057f068) entered forwarding state
Feb  4 02:01:32 unRAID-Server kernel: veth2c64f4d: renamed from eth0
Feb  4 02:01:36 unRAID-Server kernel: eth0: renamed from vethf901c26
Feb  4 02:02:21 unRAID-Server kernel: vethe4af3a8: renamed from eth0
Feb  4 02:02:22 unRAID-Server kernel: eth0: renamed from veth2cd3a3b
Feb  4 02:02:33 unRAID-Server kernel: veth323eccd: renamed from eth0
Feb  4 02:02:34 unRAID-Server kernel: eth0: renamed from veth42a7023
Feb  4 02:02:44 unRAID-Server kernel: veth6daa23f: renamed from eth0
Feb  4 02:03:02 unRAID-Server kernel: eth0: renamed from vethf3dfde4
Feb  4 02:03:17 unRAID-Server kernel: vethcfee5ec: renamed from eth0
Feb  4 02:03:21 unRAID-Server kernel: eth0: renamed from vethaf7349c
Feb  4 02:03:50 unRAID-Server kernel: vetha3bd006: renamed from eth0
Feb  4 02:07:17 unRAID-Server kernel: eth0: renamed from vetha45e7e2
Feb  4 02:07:55 unRAID-Server kernel: veth33d875d: renamed from eth0
Feb  4 02:08:32 unRAID-Server kernel: eth0: renamed from vethb3ae139
Feb  4 02:09:06 unRAID-Server kernel: vethde34ed1: renamed from eth0
Feb  4 02:09:10 unRAID-Server kernel: eth0: renamed from veth18f95d8
Feb  4 02:09:21 unRAID-Server kernel: veth149edce: renamed from eth0
Feb  4 02:09:36 unRAID-Server kernel: eth0: renamed from vethdcc9ac4
Feb  4 02:09:50 unRAID-Server kernel: veth46ca238: renamed from eth0
Feb  4 02:13:52 unRAID-Server kernel: eth0: renamed from vethf9ddf50
Feb  4 02:14:06 unRAID-Server kernel: docker0: port 3(veth3d216e3) entered disabled state
Feb  4 02:14:06 unRAID-Server kernel: vethb187619: renamed from eth0
Feb  4 02:14:06 unRAID-Server kernel: docker0: port 3(veth3d216e3) entered disabled state
Feb  4 02:14:06 unRAID-Server kernel: veth3d216e3 (unregistering): left allmulticast mode
Feb  4 02:14:06 unRAID-Server kernel: veth3d216e3 (unregistering): left promiscuous mode
Feb  4 02:14:06 unRAID-Server kernel: docker0: port 3(veth3d216e3) entered disabled state
Feb  4 02:14:09 unRAID-Server kernel: docker0: port 3(veth8671e18) entered blocking state
Feb  4 02:14:09 unRAID-Server kernel: docker0: port 3(veth8671e18) entered disabled state
Feb  4 02:14:09 unRAID-Server kernel: veth8671e18: entered allmulticast mode
Feb  4 02:14:09 unRAID-Server kernel: veth8671e18: entered promiscuous mode
Feb  4 02:14:10 unRAID-Server kernel: eth0: renamed from vethe82f3a0
Feb  4 02:14:10 unRAID-Server kernel: docker0: port 3(veth8671e18) entered blocking state
Feb  4 02:14:10 unRAID-Server kernel: docker0: port 3(veth8671e18) entered forwarding state
Feb  4 02:14:20 unRAID-Server kernel: vethdbc85c8: renamed from eth0
Feb  4 02:21:16 unRAID-Server kernel: eth0: renamed from vethe1ceb95
Feb  4 02:21:30 unRAID-Server kernel: veth5ad1cb7: renamed from eth0
Feb  4 02:21:32 unRAID-Server kernel: eth0: renamed from vethf1ade1c
Feb  4 02:21:43 unRAID-Server kernel: vethce6e0ef: renamed from eth0
Feb  4 02:21:43 unRAID-Server kernel: eth0: renamed from vethb908476
Feb  4 02:21:59 unRAID-Server kernel: veth1a84d93: renamed from eth0
Feb  4 02:22:19 unRAID-Server kernel: eth0: renamed from vethd22c68d
Feb  4 02:22:30 unRAID-Server kernel: vethf2f4bad: renamed from eth0
Feb  4 02:22:39 unRAID-Server kernel: eth0: renamed from veth7c50a5c
Feb  4 02:23:13 unRAID-Server kernel: vethee8ea16: renamed from eth0
Feb  4 02:23:17 unRAID-Server kernel: eth0: renamed from veth19a7bc3
Feb  4 02:23:27 unRAID-Server kernel: veth3560c92: renamed from eth0
Feb  4 02:23:27 unRAID-Server kernel: docker0: port 4(veth3b943d7) entered disabled state
Feb  4 02:23:27 unRAID-Server kernel: docker0: port 4(veth3b943d7) entered disabled state
Feb  4 02:23:27 unRAID-Server kernel: veth3b943d7 (unregistering): left allmulticast mode
Feb  4 02:23:27 unRAID-Server kernel: veth3b943d7 (unregistering): left promiscuous mode
Feb  4 02:23:27 unRAID-Server kernel: docker0: port 4(veth3b943d7) entered disabled state
Feb  4 02:23:27 unRAID-Server kernel: docker0: port 4(veth361894c) entered blocking state
Feb  4 02:23:27 unRAID-Server kernel: docker0: port 4(veth361894c) entered disabled state
Feb  4 02:23:27 unRAID-Server kernel: veth361894c: entered allmulticast mode
Feb  4 02:23:27 unRAID-Server kernel: veth361894c: entered promiscuous mode
Feb  4 02:23:27 unRAID-Server kernel: docker0: port 4(veth361894c) entered blocking state
Feb  4 02:23:27 unRAID-Server kernel: docker0: port 4(veth361894c) entered forwarding state
Feb  4 02:23:28 unRAID-Server kernel: eth0: renamed from veth62e5729
Feb  4 02:23:41 unRAID-Server kernel: veth6495deb: renamed from eth0
Feb  4 02:24:23 unRAID-Server kernel: eth0: renamed from vethbecf3b5
Feb  4 02:24:36 unRAID-Server kernel: veth46d513a: renamed from eth0
Feb  4 02:25:00 unRAID-Server kernel: eth0: renamed from veth2a1ad3e
Feb  4 02:25:12 unRAID-Server kernel: veth46b9125: renamed from eth0
Feb  4 02:25:12 unRAID-Server kernel: eth0: renamed from vethd7be4b8
Feb  4 02:25:22 unRAID-Server kernel: vethf1f2a48: renamed from eth0
Feb  4 02:25:23 unRAID-Server kernel: eth0: renamed from vethad2d997
Feb  4 02:25:37 unRAID-Server kernel: veth32d9adf: renamed from eth0
Feb  4 02:25:59 unRAID-Server kernel: eth0: renamed from vethb8d1097
Feb  4 02:27:02 unRAID-Server kernel: vethc350506: renamed from eth0
Feb  4 02:28:11 unRAID-Server kernel: eth0: renamed from veth0bf1773
Feb  4 02:29:14 unRAID-Server kernel: veth3c86e2f: renamed from eth0
Feb  4 02:29:14 unRAID-Server kernel: docker0: port 2(vethde10508) entered disabled state
Feb  4 02:29:14 unRAID-Server kernel: docker0: port 2(vethde10508) entered disabled state
Feb  4 02:29:14 unRAID-Server kernel: vethde10508 (unregistering): left allmulticast mode
Feb  4 02:29:14 unRAID-Server kernel: vethde10508 (unregistering): left promiscuous mode
Feb  4 02:29:14 unRAID-Server kernel: docker0: port 2(vethde10508) entered disabled state
Feb  4 02:30:29 unRAID-Server kernel: docker0: port 2(veth8d00036) entered blocking state
Feb  4 02:30:29 unRAID-Server kernel: docker0: port 2(veth8d00036) entered disabled state
Feb  4 02:30:29 unRAID-Server kernel: veth8d00036: entered allmulticast mode
Feb  4 02:30:29 unRAID-Server kernel: veth8d00036: entered promiscuous mode
Feb  4 02:30:29 unRAID-Server kernel: eth0: renamed from veth2263799
Feb  4 02:30:29 unRAID-Server kernel: docker0: port 2(veth8d00036) entered blocking state
Feb  4 02:30:29 unRAID-Server kernel: docker0: port 2(veth8d00036) entered forwarding state

 

  • Author

Niemand?

  • Author

kann mir hier wirklich niemand bei helfen?

  • Community Expert
On 2/2/2025 at 10:20 AM, LyDjane said:

Sobald die Docker im br0 mit fester IP sind, klappt es tadellos.

Was spricht gegen br0?
 

damit vielleicht einer helfen kann, braucht es schon mehr Infos.

- deine Hardware

- dein Netzwerk

- diagnostics

 

  • Author

Guten Morgen,

 

gegen BR0 spricht nichts, ich möchte aber wissen, warum der Fehler nun vorhanden ist.

 

Hardware:
- PC HP EliteDesk 800 G2 Intel i5-6500 4 x 3,2 GHz 4GB - 32GB RAM

- Bios Update auf die letzt mögliche Version wurde durchgeführt

 

Netzwerk:

Was genau wird benötigt? Screenshot anonymisiert?

 

Diagnostics:
Was genau wird von der .zip-Datei benötigt?

 

Viele Grüße

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

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.