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.

bobbintb

Members
  • Joined

  • Last visited

Everything posted by bobbintb

  1. You'll have to set up a daemon or cronjob.
  2. I'm not having any issues with Plex account is what I'm saying. Screenshot?
  3. The error you are getting seems to indicate that you have your download path set to /root/downloads instead of /downloads.
  4. I'm not having any issues. I hate to state the obvious but are you using the right username and password?
  5. Yes, that's what that means.
  6. Yeah, just to elaborate on what as Waseh was saying, the two are going to have to remain separate, at least for most people. The reason being, as he said, running rclone in a docker means loosing the ability to mount shares to the file system. Mounting a remote cloud share is one of the main reasons people use rclone so that's a big issue. While there is also an rclone docker from a different developer, I don't know how well maintained it is and I don't think a lot of people use it because not being able to mount shares makes it useless for most people. This isn't a bug or anything that can be fixed, just a result of what docker is. On the other side of that, rclone browser is a gui tool and UnRAID is headless. So the only way to use rclone browser is in a docker. If someone already made a docker image of rclone browser, it should be pretty easy to just use the docker template in UnRAID. I doubt anyone has though so you'll have to make your own docker image first. I can't help with that but a quick google search help with that.
  7. The error looks pretty self explanatory to me.
  8. Sonarr and deluge are mounted the same. Radarr is not though. It should work for Sonarr.
  9. Yes, I mentioned that and that was my point. He had already corrected that before you posted and you said that was all he needed to do. But he still needed to change the guest side of things. Anyway, he seems to have gotten it resolved.
  10. No, that's not entirely correct. First of all, that's the old mapping they used and that has already been corrected. Second, both the host AND the guest side have to be the same for the reasons I mentioned.
  11. The host and guest directories need to be the same. You gave the wrong mappings at first, but I also didn't notice the host mappings were not the same. So my first answer was incorrect based on the incorrect mapping you gave but correct based on the correct mapping. If you're still not following that, it's not important. Just trying to explain my error. The bottom line is the guest and host mappings need to be the same (or use the Sonarr remote mapping feature). The host mappings need to be the same in order to link the guests together, and the guest directories need to be the same or the two guests will both have access to the same host directory, but refer the directory by different names. Got it?
  12. Ah, I didn't notice the host mappings were different in your first post. I thought they were the same. If those first mappings you gave were correct, my answer would have actually been incomplete because of that. But with the correct mappings you gave, my original answer if complete.
  13. The issue is the drive mappings are different from the guest perspective. Deluge is downloading files to /downloads. When a download completes, it then passes the download location to Sonarr. But Sonarr has no /downloads folder and can't find the files because they are in /Complete. You either have to make the directories that same or use the remote path mapping feature in Sonarr.
  14. I just thought I'd share something. No endorsement implied but I found two websites were you can automatically create an app out of a website. If you make your Ombi publicly available (making sure you secure it, of course) you can very easily create an app for your friends and family to use for making Plex requests. The sites are appsgeyser.com and gonative.io. I get a message every once in a while with the gonative.io app when I open it informing me that it cannot be published without licensing. That can be a little annoying but can be turned off in the Android settings. The appsgeyser one doesn't seem to save cookies even though the option is on so users have to log in every time. That might be fixable but I haven't tried. You can change the icon and splash screen from the default and use whatever image you like. I just used the Ombi logo from the site. Both sites are free to use.
  15. Oh, so it adds a basic auth login to webuis that don't have one?
  16. What exactly does the .htpasswd part do? Encrypt https logins or something?
  17. Ok. I only plan on exposing Ombi anyway. I was hoping I'd get a little more familiar with certs with this but letsencrypt is so automated. I have to deal with certs for my servers at work and it's not my thing. But it's been a learning experience none the less. I got a little better at reverse proxies, with I'll be doing soon as well so that's good. I'm really liking Ombi so far. I never got into setting up any of the older solutions like Plex Requests because I just didn't really like the layout. It just felt clunky.
  18. Thanks, that did it. I had tried removing ombi form the location/ part but left it in the proxy_pass and buseurl of ombi but that didn't work. I also had to comment out the existing location section in default: location / { try_files $uri $uri/ /index.html /index.php?$args =404; } It's working now. Thanks again. One last thing. Do I need to do anything with .htpasswd for this? I've seen mentions of it but didn't seem to need it. Is that a security issue?
  19. Ok, I had gleaned bits and pieces of that but didn't quit get it. Probably because it was 2am at that point. And on a work night too. I followed your instructions but I am getting this error from letsencrypt: nginx: [emerg] "location" directive is not allowed here in /config/nginx/site-confs/default:78 EDIT: Nevermind, I had to move the code in default so that it was inside the server block. I'm trying to tweak it a bit because I don't want the base url of /ombi. I just want to use the DNS with no base URL. I should be able to figure that out on my own though. Thanks for the help.
  20. I think I got my letsencrypt done. I got a dynamic dns and ran the letsencrypt docker. I can go to my dns in a web browser and it show the example page and it has the green lock so that's good. How do I implement Ombi now?
  21. Oh it will be a while before I'll have the time. I'm sure I can do it if I can just sit down and spend some time with it. It's about time I got comfortable with certificates anyway but I'll definitely hit you up if it comes to that. Thanks.
  22. I was looking at that but don't know too much about it and was wondering if there was a guide. I guess I'll just mess around with it first once I find the time.
  23. I want to set this up for my family that lives out of state. Anyone have a guide on how to best secure this?
  24. Oh, I see what you're saying but that's something different. That has to do with the way the two programs communicate over the API, not docker directory mapping. The path's don't have to match, they just both have to be able to find the file, regardless of whatever they each use for the path. In this example, when rutorrent downloads something it will put it /data (which is really in /mnt/user/downloads). Sonarr will see it as /downloads. So they both have access to the same file but internally have a different mapped path. The real cause of the issue is that Sonarr and rutorrent communicate over an API and once Sonarr gets notified a download is complete, rutorrent will tell Sonarr where it is. But since neither one of them can really see outside of their respective virtual containers, rutorrent will tell Sonarr the file is in /data and Sonarr won't be able to find it because that path is /downloads to Sonarr. So yes, you can change the guest sides of the docker directory mapping to match but it really isn't a docker specific issue. It's an issue with having Sonarr and rutorrent on two different machines, which is essentially what docker is doing. Sonarr has the remote path settings specifically for this scenario of Sonarr and the torrent program (or usenet) being on different machines.
  25. Of course not. It make absolutely no sense to wipe out all the settings and force a user to reconfigure everything every time they updated a program. The docker image is a virtualized container, basically a stripped down virtual machine. Docker has configuration settings that tell it which directories in the docker image (rutorrent) correspond to which directories in the host system (UnRAID). Those settings aren't stored in the image; it wouldn't make any sense. It can get a confusing mapping the directories but it will make sense eventually. Here is a visual representation. Deleting (or updating) those "soanrr" and "rutorrent" boxes doesn't wipe out those mappings.

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.