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.

Gragorg

Members
  • Joined

  • Last visited

Everything posted by Gragorg

  1. Try and plug the USB into a windows PC if it finds errors let it repair them. Also try another USB port preferably a USB 2.0 port if you have one.
  2. That should work. I think you will find that most people use XFS for array drives thou as some have had issues with BTRFS in the array. BTRFS works great for pools, ZFS also an option for pools which also allows easy snapshots to be taken with ZFS Master plugin.
  3. Gragorg replied to Mxoio's topic in General Support
    I assume you have "Turn off UPS after shutdown:" set to no in the UPS settings page built into unraid?
  4. The only other thing different from mine is I don't have static routing setup at all. I only have 51820 port forwarded. Maybe try without it.
  5. 300gb is way to big start at 10gb. You can make it larger if you need to. My 21 dockers use about 14gb so I currently have it set for 20gb. I would swap the 150gb for 512gb. First i recommend running appdata backup so you have your appdata saved to the array. I basically disabled the docker service and set the mover up to move all the data off the old cache drive to the array. Once the old drive was empty I put the new cache drive in place and then reversed the mover direction back to cache drive and run the mover again. At this point you can always restore from appdata backup if something wasn't right.
  6. Spindown Issue fixed thanks for the quick fix.
  7. Hey wondering if you got your Jellyfin working. I asked my son about it and when it says add a server try and use your web URL with https:// again and not the ip and port number. Seems odd to me but maybe worth a shot.
  8. Did you try with Local server uses NAT set to yes?
  9. Not to sure then. I actually use Plex. Try and post in Jellyfin support page.
  10. Make sure “Allow remote connections to this server” is enabled on the Jellyfin server (Administration | Dashboard | Advanced | Networking)
  11. Does it work from the webgui? When you added your IP did you included the port such as 192.168.1.50:8096
  12. Try and clear browser cache
  13. There is a docker container called Cloudflare-DDNS by selfhosters that you can run to keep your dynamic IP upto date. Spaceinvader one has a video on this.
  14. Ok So I can ping your URL. I would remove that picture so you don't have your URL for everyone to see. In Nginx proxy manager you should have scheme set to HTTP not HTTPS. Also is NPM returning a proper SSL certificate.
  15. Forward should work but no need to forward 2 ports for each. It should be 443-443 Wan and 18443-18443 Lan and 80-80 Wan and 1880-1880 Lan. Can you ping the your URL for jellyfin that you have setup from cloudflare?
  16. Are you using SWAG or NPM? Did you forward port 80 and 443 external port to the proper internal port that you setup on your docker template. NginxProxyManager is much easier to configure if that matters.
  17. Post diagnostics. Its very likely a bad cable/connection
  18. Did you try and put the USB stick in a windows machine to see if detects errors? If it does let windows fix them.
  19. Here is the information from the manual.
  20. Since switching to the updated repository for V1 I have noticed that mealie opens without being logged in. Is this normal behaviour? I used to have to login before it would open up.
  21. Once cabling is fixed and logs are clear 1. Stop the array 2. Unassign parity drive 3. Start the Array 4. Stop the Array 5. Assign the parity drive back 6. Start the Array ( this will start parity reconstruct)
  22. I would leave unraid on 80 and 443 its best not to change them. Is it possible you were using 443 for both unraid and Swag? Try switching swag to an unused port like 180 to container port 80 and 1443 container port 443. Assuming 180 and 1443 are free.
  23. Gragorg replied to cwebb's topic in General Support
    This is from the manual
  24. No I never did figure out the error or find anyone who knew anything about it.
  25. Ok so I looked at the new template and saw the container now uses port 9000. I edited my template to use 3000 on container port 9000 and deleted the old front end port and the old API port. Seems to be working fine again.

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.