dukiethecorgi

Members
  • Posts

    105
  • Joined

  • Last visited

Everything posted by dukiethecorgi

  1. One workaround is to use multiple containers, limiting each one to 1200 or so torrents. I found that that's about the maximum number before the UI becomes unbearably slow.
  2. Decided to use the built in redis. One thing I'm not understanding is that my network is bond0, a 802.3ad lag. Ntopnrg insists that this is a 'ghost network'. Aside from this, everything seems to working fine
  3. Yes, that fixed it for me too. One other issue I found is that the container will not run while the bitnami/redis container is running.
  4. Port 3000 is already in use. How can I change that?
  5. PIA announces that the legacy servers will shut down at the end of October Now that the next gen server support is in the latest, I guess it's time for me to update
  6. Probably because you don't have an open port. You can go to https://www.yougetsignal.com/tools/open-ports/ and put in your VPN external IP and port number to check
  7. I've been connected to the same endpoint for 5 days without issue
  8. I just saw this Next Generation Port Forwarding on the PIA website
  9. I recently installed the Portainer container, and I noticed that Docker was showing over 400 volumes. From the unraid console I ran docker volume prune to remove the unused volumes and my docker volume reduced in size 38gb.
  10. I installed the Portainer container and found that I have 472(!) volumes. Is it safe to run docker volume prune from the command line? Do all the containers need to be running when I do this?
  11. Out of perceived privacy concerns, not because Kape had a history of not keeping port forwarding servers running
  12. I looked in the logs. When it connects, it tries 10 times to get a port, then disconnects and tries again. I took a LONG time before it finally got assigned a port
  13. CA Vancouver is working, but it took a lot of tries before it would give me a port
  14. I can't seem to figure out how to disable TLSv1.0 and TLSv1.1 I've added ssl_protocols TLSv1.2 TLSv1.3; to the server block, but https://www.ssllabs.com/ssltest/analyze.html still reports TLSv1.0 and TLSv1.1 as active
  15. Version 6.8.3 using Chrome On the main tab, if I click to explore a SMB share it works fine, but when I hit the back button, the entire SMB shares section of the Main tab is missing. A refresh of the web page and everything displays correctly. No impact on functionality, just a cosmetic glitch
  16. I think I know what's going on. In my case, each one of the Jackett instances is using a different set of trackers (public trackers, private trackers and anime trackers). It looks like you are using the same trackers in each instance. I don't think that will work because your using the same credentials for simultaneous logins
  17. Here you go! As you can see, different port # and appdata locations, nothing else needed tweaking
  18. I have three instances of linuxserver jackett running - public trackers, private trackers and anime trackers. Using different appdata folders and ports, everything works fine
  19. Flush the Chrome cache and it should work
  20. My server has two network cards (eth0 and eth1) which are configured as 802.3ad link aggregation. This shows as bond0, which seems to work fine, ethtool shows it as Speed: 2000Mb/s. I also show a bond2 interface, which seems to do nothing - no packets up or down. What is this interface, and why is it there? Edit: Solved network settings had Enable VLAN set as yes, this creates a new interface
  21. Re Homer docker Installed OK, used port 8110, web UI gives me http 413 Request Entity Too Large Nothing in logs. Any ideas?
  22. Nice, Deluge 2.0 broke all the extract plugins, this may be the answer. I'll post back with my results.