crazygambit

I've also been having this issue. Has anyone found a solution? Or at least a way to increase the log size permanently, since 128M seems pretty small and for some reason when the logs roll they're saved in the same directory, which kinda negates the point of rolling in the first place (so the log doesn't fill up in the first place!).

I've been racking my brain to come up with a way to have the plugin automatically start the mover if the cache is filled up over a certain threshold (say 90%), but also run once a day normally at a certain time. I don't want to take the performance hit to run it every hour if it's not needed, but I'm willing to take the hit if it's getting full. I know the plugin won't automatically detect if it's over 90% full, so I'm running it hourly if it's over a certain threshold and have the option to Cron Schedule to force move all of files at 6 am. The problem is that the hourly move never activates, even if the cache is full. Is it possible to do what I want or am I completely misunderstanding what this plugin does?

I got reverse proxy working using Letsencrypt (now called Swag) using nginx just by modifying the provided sample for subdomain. The install instructions mention that subfolder doesn't work so I made a new subdomain using duckdns.org. I've never used Cloudflare, so no clue there.

Is anyone having trouble with setting up email notifications? For some reason the same settings that work perfectly in Ombi don't work here at all. I never get the test email.

Was a solution found to this? I also had my log filled up with this error.

Is there a current workaround? I'm also getting the download error.

Ah yes, I'm indeed using a couple of AOC-SASLP-MV8 cards. If anyone is wondering, the IRQ Nobody cared issue is triggered by either connecting an HDMI out cable to a monitor or USB mouse and keyboard. Simply not doing that (or rebooting after you say change BIOS settings) avoids the problem altogether. Otherwise those cards seem to work fine. I've had them for almost 10 years now.

Really? For me it's a complete performance killer for certain stuff. Like the mover slows to a crawl for example. I've never understood what exactly the problem is.

The release notes for the latest version mentions the removal tests for IRQ x: Nobody cared. Why was that test removed? As someone that has been affected by it in the past (and the present, I know exactly how to trigger it), it was nice to have.

I will check this. There are also some browser extensions that allow you to interact with JDownloader. Instead of copy/paste you links, they could be better alternatives. Did you ever find the answer to this? I find the docker dies with even a moderate number of links ~100. If assigning more resources to it would allow it to work with more, it would be great.

Does anyone know why the webgui doesn't work for me in Chrome while it works in MS Edge? It's not critical, but I'd rather not run Edge. Edit: Also how do I get it to save the settings. The speed limit on downloads is particularly annoying to have to reset each time.

No, I have those on the 15th.

I uninstalled this plugin, but today is the day I had it scheduled to run (the first of the month) and my server is going crazy, so I highly suspect it's still running. I found this in my system log today: Mar 1 05:44:39 Tower inotifywait[5734]: Failed to watch /mnt/disk4; upper limit on inotify watches reached! Mar 1 05:44:39 Tower inotifywait[5734]: Please increase the amount of inotify watches allowed per user via `/proc/sys/fs/inotify/max_user_watches'. Does that mean it is in fact running? If so, how do I disable it? Do I need to install it again and clear the schedule or something?

I've only recently started experiencing issues with radarr. It's using over 5GB RAM (out of 16) and it makes all my dockers completely unresponsive and I start to get 100% CPU utilization. So basically until this is fixed I can no longer use it. Has anyone had any success with limiting the amount of RAM the docker can use?

For some reason it's not making any difference. It still works if I manually redirect, but otherwise, no dice.

I'll take a look. I just realized that if I manually type "https://" before the url giving the 400 Bad Request error it actually works. Of course it's not ideal though.

I don't think that's quite it. In fact if I change it from http to https in the Ombi section I immediately get a 502 Bad Getaway error and don't even get to see the login info. I suspect it has to do with Ombi requiring the blocks of code before and after the typical proxy pass stuff. Here's my current try, I'd love to see how you have it setup if you're using Ombi. location /ombi { return 301 $scheme://$host/ombi/; } location /ombi/ { include /config/nginx/proxy.conf; proxy_pass http://192.168.0.11:3579; } if ($http_referer ~* /ombi/) { rewrite ^/dist/(.*) $scheme://$host/ombi/dist/$1 permanent; }

That's weird, I'm 100% sure that option was there yesterday. Indeed clicking on the icon on the far right works, I hadn't noticed because I was using advanced view. I finally managed to get Tautulli working well, but I'm having some issues with Ombi. I get to the login page fine, but after I login I'm getting "400 Bad Request The plain HTTP request was sent to HTTPS port". I'm following the template of the readme, but not the custom docker network, so I put in my IP address.

Thanks to @CHBMB and @bonienl for their very clear responses. It clears a lot of stuff up. Now I have yet another question. Yesterday when I clicked on the docker icon in the docker page on the GUI I had the option to look at the logs, but now for some reason it's gone and I can't find the logs in the appdata folder either. Does anyone know how I can get that option back?

I'm still trying to get to grips with this. One thing I don't understand is the benefits of having a custom bridge network. As far as I understand that's a feature from 6.5.1, so how was this done before then? Is there a downside in all dockers being "bridge" instead of "host"? I'd rather not make the change unless it's absolutely necessary or there are some big tangible advantages. Is it more secure? I've seen it on this thread that to access the unraid GUI a VPN is recommended since otherwise it's a huge security risk and that someone getting access to your dockers is not as bad, but if someone gets access to your sonarr and radarr they can literally delete your whole server in minutes, so if I get better security with a custom network I'd definitely go for that.

Because I don't understand it and I can't edit the first post, so there's little point in doing it if it's gonna be lost somewhere on a huge thread like this. Once I figure it out if you promise to put it in the first post so people can actually see it, I've got no problem doing it, though I fear it will be after spaceinvaderone releases his video (which should definitely be linked to in the first post IMO). Edit: Also the fact that mods are volunteers is a Limetech decision and as a paying customer I really don't care one way or the other. This isn't a forum for some free open source project. It's a paid OS (and not cheap!), so I don't think expecting decent support is out of the question.

I understand why step by step instructions wouldn't be in the readmes, like I said it's out of their scope (which is why people like me prefer guides). I was talking more about your point of not putting that information in the first post and relying just on the manual. Like you said, this application has many uses and works on many OSs, but if I come to the unraid forums it's not unthinkable to expect the specific knowledge gathered in 89 pages of this thread to be summarized on the first post. You say it's unnecessary, but I strongly disagree. I understand if it can't be done by you and the developers on the container, but it's certainly something that could be done by the mods and experts in this thread. Setting this up for a normal user is actually pretty hard, it requires a lot of steps and failure in any of them can render it inoperable. Since a big selling point of unraid is the flexibility afforded by dockers one would think it would be a priority to make installing stuff like this as easy as possible. Also I love to learn how to do this stuff, which is why I found the third party guide so underwhelming, it just offered a premade default file with no explanation on how or why it was made. I think that's the reason spaceinvaderone's videos are so popular here. He explains the stuff pretty well and goes over every step without skipping stuff that's "too simple". When he makes his video on this topic it should be linked in the front page. Thanks for your suggestion on the browser stuff, I'll do that.

It would. Since it's critical information it should be posted in as many places as possible (repetition is not a bad thing in this place), not in the last paragraph of not even the main readme. I was following the "complete" guide that was recommended in this very forum and is the first google result of let'sencrypt + unraid and it makes absolutely no mention of this. This one: https://cyanlabs.net/tutorials/the-complete-unraid-reverse-proxy-duck-dns-dynamic-dns-and-letsencrypt-guide/ It's very important for the less technically savvy (like myself) for all the steps to be consolidated into one place, which is why guides are my go to rather than the readmes of the application itself that won't go over setting up your dns or forwarding your ports because it's outside it's scope. I think the next video of spaceinvaderone will cover this very issue and honestly I can't wait. I found the "complete" guide pretty terrible since it skips a lot of crucial steps and stops before setting up any docker. They provide a default file to replace the one that comes with the container, but no explanation on how it was created and what each part is doing, no mentions of the steps required in the actual docker to get them to work. I know it's completely obvious to most of you to change the web path in say sonarr to /sonarr to get reverse proxy to work, but for someone following a step by step guide, it really isn't. I found that nugget of wisdom hidden away in the sample files for each docker (even though the readme says if you're using linuxserver dockers there's no need to change them, so there shouldn't be an expectation people are editing them). TL;DR: Critical pieces of information required to get this thing to work scattered in many different readmes = bad. Consolidate everything with step by step instructions = good. Hopefully spaceinvaderone will save us soon. PD: I used the default file from that guide and now even though I deleted the whole appdata folder and reinstalled the container every time I type https://192.160.0.11:444 it gets changed to https://192.160.0.11/htpc even though I don't have that container installed and of course it doesn't work. Do I need to reboot?

Everything was working great, but then sonarr stopped working and it wouldn't restart so I tried to save on the edit settings menu so it would just reinstall itself and this is what I'm getting: IMAGE ID [fa9981cf81f1]: Download complete. IMAGE ID [6886e0428439]: Pulling metadata. Pulling fs layer. Error downloading dependent layers. IMAGE ID [1a49cba2cf95]: Error pulling image (latest) from binhex/arch-sonarr, endpoint: https://registry-1.docker.io/v1/, readdirent: input/output error. Error pulling image (latest) from binhex/arch-sonarr, readdirent: input/output error. TOTAL DATA PULLED: 0 B Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker rm -f binhex-sonarr Error response from daemon: no such id: binhex-sonarr Error: failed to remove containers: [binhex-sonarr] The command failed. Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker rm -f binhex-sonarr Error response from daemon: no such id: binhex-sonarr Error: failed to remove containers: [binhex-sonarr] The command failed. Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="binhex-sonarr" --net="bridge" -e TZ="America/Buenos_Aires" -p 8989:8989/tcp -p 9897:9897/tcp -v "/mnt/user/appdata/sonnar":"/config":rw -v "/mnt/user/":"/data":rw -v "/mnt/user/":"/media":rw binhex/arch-sonarr Error response from daemon: open /var/lib/docker/graph/1a49cba2cf9524a4793a29bec9177bca10b0aebbe00fb14b54c39d2090a0f525/json: stale NFS file handle The command failed. Warning: file_put_contents(/var/lib/docker/unraid-update-status.json): failed to open stream: Read-only file system in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 291 Warning: file_put_contents(/var/lib/docker/unraid-update-status.json): failed to open stream: Read-only file system in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 438 I had just gotten all my settings just how I wanted them too. Is there anything I can do or am I screwed? Edit: actually I'm getting that error from all the other containers as well, but they still keep working. Weird.