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.

Asusane

Members
  • Joined

  • Last visited

  1. cant create docker container because they dont exist localy and i got no connection to the server to pull the images but i got my problem solved i guess every time i tryed to pull a docker that happens :nslookup registry-1.docker.io ;; communications error to 100.122.xxx.xxx#53: connection refused ;; communications error to 100.122.xxx.xxx#53: connection refused ;; communications error to 100.122.xxx.xxx#53: connection refused ;; no servers could be reached that was a Tailscale IP solved : kill TS & Netbird Plugin killall -HUP dnsmasq echo "nameserver 8.8.8.8" > /etc/resolv.conf echo "nameserver 1.1.1.1" >> /etc/resolv.conf /etc/rc.d/rc.docker restart nslookup registry-1.docker.io Server: 8.8.8.8 Address: 8.8.8.8#53 after that it works fine i got all my containers from recreate back without great issues exept nextcloud but i got this really fast fixed cuz my custom network was deleted aswell for nextcloud
  2. Hi everyone, I'm experiencing a persistent issue where my Docker tab in the Unraid GUI hangs indefinitely on "Please wait..." and any attempt to pull a new image results in a "context deadline exceeded" or "request canceled while waiting for connection" error. What happened: The issue started after a crash of a VPN container (Gluetun/Netbird). Since then, the Docker service seems to be in a deadlock. Symptoms: The Docker UI tab never finishes loading. Pulling images consistently fails with timeouts. nslookup inside the terminal shows timeouts for standard lookups, seemingly attempting to route through a leftover Tailscale/VPN interface (100.100.100.100). I have already tried restarting the Docker service and pruning networks, but the issue persists after reboots. The docker.img has not been deleted to preserve data. What I have tried: Verified network DNS settings (1.1.1.1/8.8.8.8) in the GUI, but the system still seems to attempt routing via the old VPN/Tailscale interface. Checked iptables and network interfaces, but unable to clear the deadlock. The logs show that the Docker daemon is struggling to connect to registry-1.docker.io. I have attached my diagnostics file to this post. Could you please help me identify which zombie process or network interface is blocking the Docker daemon? I want to avoid deleting the docker image/rebuilding everything if possible. Thank you for your help! asunastower-diagnostics-20260709-1325.zip

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.