jaylo123

Got ya. Yea, the containers used in Unraid are built upon projects mostly out of Github or elsewhere. The container itself, when clicked on in the "Docker" screen should have a link or two that can direct you to either the source for the container or even sometimes the source for the project upon which the container was built. The author of the container used in Unraid grabs the Github (or whatever source) code and makes it a container for use in Unraid. That's all, in a nutshell (a VERY high-level overview). So if the application being used in the container has a potential issue, its best to chase it upstream directly to the developer of the application. The application maintainer will resolve the issue, then the container owner will create a new build around it and then boom, you'll see a notification to update your downstream Unraid container in your web GUI. All the container creator (in this case, linuxserver.io) does in that process is take any updates to the application and just wraps it in a docker container and presents it in an easily digestible format for Unraid to eat, preferably like a pizza with plenty of pepperoni. So - issue with the container? That is an issue for the container owner (linuxserver.io in this case). Issue with the underlying app? You gotta go further upstream to the actual app developer. Even more confusing - sometimes they're the same people

I'll readily admit that I haven't read this entire thread. But I've been on 6.9.2 since it was released and I haven't experienced this issue at all. My disks spin down just fine. Hardware specs are in my signature. --------------------------------------------------------- One question I do have though, for QEMU / KVM: I heard from a birdie about 5-6 months ago - an oVirt dev, really - that QEMU/KVM had an update that allowed console access to a Windows VM that had a GPU passed through to it. In the past, if you passed a GPU through to a VM you were left with a blank screen on the console. So this enhancement added a feature that Citrix / VMWare have had for quite a while. Is that a thing here? Or am I possibly making something up in my own head? I've checked Phoronix and other upstream sites but haven't found anything to link here to back up my question with documentation (I know, I'm the worst...). But I figured I'd ask the question anyway. But I swear I read this somewhere. I'm going to keep searching. I can't find it now. Maybe I had too many IPAs when I heard it. /shrug

Heya @jbartlett - I looked for a github or other source and did a very cursory search through a few pages here but didn't see an answer to a question I have, so I'll just ask: What are you using to test? IOzone? I guess I could just check the container itself, but I guess I'm lazy.

You would probably want to ask that question on their github page, not here. https://github.com/Tautulli/Tautulli That said, I did just recursively check for any java or log4j installation in THIS container and I did not get any returns. So, no, not impacted.

It's fine, just wanted to provide some feedback! I'll keep an eye on this project, certainly. Looks interesting. I can explore it with Edge for now.

Oh - and yea, I can logout / login just fine with Edge. I cannot on Firefox. The only extension I have installed is my 1Password extension on Firefox. I also have it installed on Edge. Oh well, got in

It's an empty file Now, I did just try it in Edge/Chromium. It worked that time! So maybe it's a Firefox thing /shrug

Darn. Nope. Wiped the db, recreated from scratch, still same blue screen "419 page expired" message.

Let me try to just wipe the database on mysql and see if a re-instantiation fixes it?

Yep. I was about to post a message here because initially it was complaining about an invalid cipher. Then I realized I only input 31. Changed to 32, got the Network Manager container to start, got to the register page automatically, and now I'm stuck here.

Restarted, launched webgui, filled out the form (~10 seconds) after the page came - same issue. I also changed the db account being used for the database to the db root instead of mine - still didn't help. The table is populated, but no users are being generated in the database. Here are the logs, if they help any. I didn't see anything jump out:

Creating a new user account generated a blue "419 | Page Expired" message. Can't proceed. Nothing in the logs on either the MySQL server or Network Manager containers.

Just wanted to say thanks - this worked. I'm still leery of the whole "chmod 777" step but yea, it works. Hopefully UnRAID includes this as a toggle in the UI in the next release. Seems simple enough on the surface, although I'm sure it really isn't that simple.

Update: This will, I assume, be fixed soon. But since I needed this sooner for my discussions with my ISP I made the following change to the "Repository" for the container in Unraid: Modified from henrywhitaker3/speedtest-tracker to henrywhitaker3/speedtest-tracker:dev (appended :dev to the end) Saved, restarted the container. It grabbed the dev branch, and confirmed, the graphs work again. Once the main branch is updated with the graph fix, I'll switch the repository back. As expected, all historical data is still there. *non-relevant information for the docker issue, but a use case for this docker* As it turns out, I've been losing ~7% of my download bandwidth since August 26th about every 3 days. Tech support is sending someone out to check my line and the main fiber panel at the end of my street Tuesday, October 5th. And a large part of that was due to this information. I didn't notice it before because it was slowly and slowly dropping. 45 day graph: I'm supposed to be getting ~950Mb/s down, I'm NOW getting ~36Mb/s down! Yikes! We both are wondering if I'll be at dial-up speeds by Tuesday... Time to bust out an old US Robotics 56.6...

Hi. The speedtest tracker container running v1.12.0 currently has a broken feature. The graphs don't change to anything other than the 7 day default view. I recently discovered that my 1Gbps line is performing fine for uploads (980Mbps) but downloads are ~90 to ~200Mbps. I wanted to look up my history to see when this happened so I can call my ISP. The historical data is there as I can see a median result over the lifetime of me running the container. The graphs just don't adjust. This is a known bug, and there is a fix in 1.12.2, but the container itself is still running 1.12.0. I couldn't tell from the github ticket whether or not it's actually released to anything other than the dev branch though.

Ok no problem. I was just pulling my hair out this past week trying to see why it wasn't working. Totally fine with the bookmark method, that's what I was thinking I had to do. Cheers

Hi. I believe I have finally deciphered how to make this work. However, I cannot access the web gui directly from Unraid's docker menu. Once I remove the network from, say, Sonarr and add it to the binhex-delugevpn network, the "WebUI" option on the Docker screen in UnRAID disappears for Sonarr. If I visit the IP:Port directly in a web browser, it works. However, the containers seem to communicate fine. Sonarr tests fine when I run the "Test" button for the download clients. I'm still working through getting the Indexers working as well as they don't respond at all from Sonarr, but that's another issue I suspect. I just wanted to ask about the missing WebUI link in UnRAID itself for now. Is it intended behavior for the "WebUI" option to disappear from UnRAID's docker menu for any containers directly passed to the binhex-delugevpn network? If so, may I make a suggestion for the official documentation to add this caveat to Q25/A25? Overview: binhex-delugevpn configuration: binhex-sonarr configuration: UnRAID Docker WebUI Missing:

Hi. Have a curious issue. I haven't dug into the CLI on the docker yet or anything, just checking logs from Unraid's web GUI for the docker container. When it starts, I get this spewing over and over and the container never comes up. Any ideas? I haven't rebooted the container since the last update. I rebooted my whole unraid server just last night. Since the container auto-updates I'm not quite sure when the actual container was last restarted, so if this is an existing issue with a known workaround please point me to that direction! ::: Starting docker specific checks & setup for docker pihole/pihole [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole Error: Unable to update package cache. Please try "apt-get update"[cont-init.d] 20-start.sh: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. Edit: Nevermind, seems the maintainer isn't 'maintaining' anymore. I'll try this route. Cheers for the tip @hoodust Final edit - Yep, that fixed it. All I did was: Shut down this container Go to Apps Search for "pihole dot doh" Installed FlippinTurt's fork. I used the same IP and password as my current container on the container configuration screen. Everything else was defaulted correctly. Started FlippinTurt's container In a Borat voice, "Great success" Easy peasy.

Ooh thanks. That probably just saved me 3 hours of hand-wrenching and headbanging!

Yep. I'm using a default Intel GPU and I am a bit surprised that the Intel driver package isn't loaded in the main build. But running an X server is a pain in the butt anyway unless you're using Nvidia's driver set or AMD's driver set. I'll tinker with it today, maybe I can figure this out. I just loathe getting into xorg.conf, it's a game of cat and mouse every time! Edit - plus, I'm sure my changes will get wiped on an updated Unraid release. But as I said above, I'm just using this as a temporary stopgap.

Using HDMI I had half of my screen garbled (lower half). Switching to DVI-D got me a screen that I can at least work in, but the DPI is jacked up and it's running at 640x480. I never use the console directly but I have to ship my laptop off to get serviced and need a temporary backup system for work. I'm planning on just using KVM and a Windows VM as a stop-gap. Not the best, but it's at least something I can utilize.

Ahh I see. It's been a few weeks, I'll give the delugevpn container another go. Why can't people be nice online and not hack stuff or try to exploit 0-days? This is why we can't have nice things. Thanks again for keeping up with all of this my dude.

Curious (honestly) about this statement. All of my traffic is still funneled through a VPN and all traffic is encrypted, end to end. If I were to go to :latest, the whole thing falls over. And to be clear - I only reverted the delugevpn release to the last release. I didn't forego it entirely, that would be a Bad Idea(tm) obviously. Edit - but the DelugeVPN stuff is off-topic for this thread, so I'll digress.

Hopefully you weren't asking me, and mis-quoted. Sounds like you were already in another deep convo.

Heyyyyyyy, there we go. I'm sure I would have been fixed tonight after my next nightly update of dockers and another update check... Guess I caught this same issue during the 'grey' area between 'push to release' and end clients seeing the :latest update today and then being prompted for the update. And now, UI parity between radarr and sonarr! Cheers for the work, and for your contributions to the community! Edit - that said, maybe with the feature releases going on in the containers now (vs. just patch releases), I'll turn off auto-updates for now in Unraid. It's bitten me twice now (other one was delugevpn and the iptables changes, which I had to revert).