No idea but there are new and exciting torrent technologies being worked on all the time. Things like DHT nodes or turning off anonymous mode can affect speeds. Your other clients may have different settings enabled or disabled or may not have implemented new protocols.
Can you just give gluetun the wrong info for you vpn server and see if transmission still works?
Nice can you send me the link when you make the torrent?
Well first I’d try turning off pi hole on the server avenue see if it fixes the issue, even though it’s unlikely as pihole should be handling dns requests for your whole network anyway.
Usually with this setup you only need to place your torrent/Usenet download client behind the VPN. Use a container like gluetun and make your download client container a service of gluetun so it only connects though gluetun. The rest of your stack can just access the internet normally.
There should be more info in the jellyseer log file, have a look in your docker directory or have a play with the “docker logs” command and try to recreate the issue. If you kill your jellyseer container then start it
You have to scroll for miles to reach different sections.
You’ll be better off trying to get a proper network attached storage (NAS) rather than an enclosure. Either buy a pre-made one or make one out of parts. That way you can use the network speeds. Or you could get a usb3 pcie card, they are very cheap these days.
Does your “old computer” have usb3 or usb c? If not you’ll find it very slow to access all that data over usb 2
Yes it is
head over to [email protected] and watch any perceived savings evaporate into thin air. along with your spare time… seriously, its great.
That’s… not all hand written is it? No one who is good at computers can write that well. We got into this BECAUSE we couldn’t write well, right?
I mean… they’re not totally wrong.