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.

akoivist

Members
  • Joined

  • Last visited

  1. Upgraded from 7.1.2 to 7.1.4 and containers using custom/br0 to have an own IP in the host's subnet lost that ability (did not start). Docker settings show's the custom docker network has now ip-range from those private docker networks (gw still the original). Also Docker settings screen went corrupt and did not allow to re-enable docker. Sounds a bit like usb memory corruption, but there is no other signs of that. Downgrade went ok and now everything works again. "Normally Docker does not allow Docker containers to directly access the same subnet as the one used by the host. You can allow this under Settings → Docker by changing Host access to custom networks from disabled to enabled."I thought that setting was for the host to access containers network, not the other way around. So enabling this setting the original ability is restored in 7.1.4?

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.