• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral


  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ah, gotcha. Thanks for educating me.
  2. @clowrym, perhaps you can educate me here. Wouldn't the version of Java running inside this docker be best updated through the hub? Or is upgrading Java manually inside the docker truly the best way (as mentioned by hexparrot in his post on github)? I looked at binhex's post as well, on this forum, and he has some valid hesitations listed there. Just trying to make sense of all the data to make an informed decision.
  3. For anyone interested, it looks as though someone has opened an issue there: https://github.com/hexparrot/mineos-node/issues/410
  4. From the docker console you can run: java -version openjdk version "1.8.0_292" As you can see, mine is running 1.8. From the Minecraft website: https://help.minecraft.net/hc/en-us/articles/360035131371-Minecraft-Java-Edition-system-requirements- you can see at the bottom that Minecraft 1.17 requires Java 16 or newer. So the docker needs a Java upgrade before a 1.17 server will be able to run successfully.
  5. How can I disable IPTables entirely for this docker? Including anytime the docker gets updated in the future. I am using my upstream firewall to do all of my blocking for me as that method is working very well for me and I can guarantee the traffic that is passed through upstream.
  6. Yes, that is still the same. To reiterate: All dockers have their own unique IP's on the same subnet (br0.x). All *arrs are using the proxy configuration through binhex/arch-qbittorrentvpn using privoxy. Then separately I also have binhex/arch-sabnzbdvpn using openvpn only and no privoxy. Everything works minus the *arrs talking to binhex/arch-sabnzbdvpn as a download client using the API key over port 8080. So far no test rules in iptables are working for me successfully, still thinking of more to possibly try. iptables -I INPUT 1 -s 10.x.x.0/24 -j ACCEPT iptables -I OUT
  7. I have tried them all multiple times, but nothing seems to be working for me. 🤷‍♂️
  8. I had a little time to troubleshoot again. This time I used a bigger hammer and disabled iptables all together. Sure enough, the *arrs can now talk to sabnzb now. So at this point I know it's the sab docker and I know it's the iptables rules at fault, but I don't know how to fix it... I suppose I may have to now experiment with adding iptables rules until I find the right one to add, but that doesn't sound very permanent as a restart or update of the docker will undo my changes.
  9. I am fairly confident that iptables is dropping my traffic. I rolled a Firefox docker, to rule out the *arr's entirely, and put it in the same vlan/br interface as SABnzb so it is layer 2 adjacent with nothing in the way (including not sharing the unraid IP, rather I assigned it its own IP). When I try to hit the SABnzb web ui on http://[IP]:[PORT:8080]/ the page times out and doesn't load. Same goes for https on 8090. I tested other internal web UI's to make sure connectivity was good and it is. So I hopped on the SABnzb console and looked at IP the tables hit counts and sure enough I see the
  10. I can ping each docker from each docker, no problem. I have also tried unchecking Use proxy in the *arr's and they still won't test successfully to SABnzb as a Download Client. That makes me think the issue lies with the SABnzb docker, but I can't seem to find the resolution. Any ideas?
  11. I am not having any luck getting my *arr's to connect to SABnzb. All of my dockers have their own IP, nothing shares IP with unraid. All of the *arr's go through the qbittorrent docker with vpn and privoxy. I can hit all webui's no problem and all openvpn's are connected successfully. Indexers all work and torrents work with all the *arr's. The only thing that isn't working is the *arr's can't see the SABnzb Download Client (they did before updates). Any ideas beyond what is in the FAQ? I have tried every combination that I can think of that is listed in the FAQ and not having any success. Tha
  12. Looks like it's QBittorrent's fault:
  13. I couldn't figure out why, but this appears to be exactly what is happening to me as well.
  14. I assumed the DB's would be built into the docker, is that not the case? Setting the IP as the host for both DB's renders the same result.
  15. I can't get this to work... I get Bad Request (400) regardless of using IP or hostname. My logs show this: I tried setting 'Database Host:' to, but that didn't help. Any ideas?