Jason Harris

  • Posts

  • Joined

  • Last visited

About Jason Harris

  • Birthday 08/11/1979


  • Gender
  • Location
    Houston, TX.

Recent Profile Visitors

423 profile views

Jason Harris's Achievements


Rookie (2/14)



  1. 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...
  2. 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.
  3. 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
  4. 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:
  5. 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.
  6. Ooh thanks. That probably just saved me 3 hours of hand-wrenching and headbanging!
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. Hopefully you weren't asking me, and mis-quoted. Sounds like you were already in another deep convo.
  12. 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).
  13. Yea, probably not. Which is fine. But, as the popular saying goes, "once you go firewalld, you never go back". Sort of like NetworkManager vs network, or systemd vs sysv. At the end of the day, if it gets the job done, that's all that matters!
  14. Fair question - firewalld is my response. But I come from EL7/EL8 land, and firewalld replaced iptables there.
  15. Thank you. I tried 'localhost' - no dice. I tried adding my container ports to the ADDITIONAL_PORTS section and restarted all containers. No dice. This was my only solution. I just spent 30 hours over 2 days on a work-related issue and I just don't have any time to really fight this right now. My Unraid server sits behind an edge firewall switch and a secondary firewall. Also - why is this container still using iptables?