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.

carefreepastor

Members
  • Joined

  • Last visited

  1. I am able to use my unRAID server as I did before I installed my new router, thanks to the posted advice of itimpi!
  2. Thanks so much! I was hoping that it might be this simple but was worrying that it would not be. I have already pulled the flash drive and found the config/network file. I will use Notepad++ to edit the file and return it to the unRAID server. I will post here if I am successful in getting to the GUI and will change the status of this post to solved.
  3. I purchased an Amazon Eero Pro 6 mesh router to replace a failed Linksys Velop mesh router. Installation of the new Eero was without problem until I tried to boot my unRAID server. I was not able to get to the GUI. In thinking things through, I realized that the old Velop, with a tcp/ip address of 192.168.1.1, handed out tcp/ip addresses in the range of 192.168.1.2 through 192.168.1.250. My unRAID server from the GUI had an assigned static address of 192.168.1.95. The new Eero router, address 192.168.4.1, hands out address in the 192.168.4.x range. I believe that this is the reason I cannot get to the GUI. I was also using the newer remote access feature as well. I also change the default name of the server. What should I do so that the unRAID server can receive a new address in the 192.168.4.x range?
  4. Thank you for the excellent second video about using Cloudflare to workaround a closed port 80, which is the case with Cox. After purchasing a domain name from GoDaddy, I have Let's Encrypt running as a docker now using dns and the log shows that it started properly (log image enclosed). My current problem, however, relates to Home Assistant docker accessing the cert file so that it will open in https. I have mucked around for more than two weeks without coming up with a solution. And, yes, I did watch the first video about setting up Let's Encrypt with dockers other than Home Assistant. i have read many, many postings and videos about how to use Let's Encrypt with Home Assistant; nothing I have attempted as a result of these how-to's has allowed me to use Let's Encrypt to successfully access Home Assistant with https. I am at a total loss and obviously need careful guidance to straighten things out. I would be happy to uninstall the version of Home Assistant which I now have installed and start over.

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.