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.
tuff_wizard
Can you just give gluetun the wrong info for you vpn server and see if transmission still works?
Figma balls, that is
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.
Yes it is
wow didn't even think of that. embarrassing :(
You can use a “+” symbol to make simple sub-aliases that all get sent to your normal email. If my email is [email protected] any email sent to [email protected] will be sent to the inbox of [email protected] but the email address is was sent to will be listed at [email protected]. Bitwarden can do this automatically when you generate a login.
If your email alias is ever leaked or gets used for spam you can just block all emails going to that alias.
We’ll what do you want to do on your server? Why not just get the same one again?
head over to [email protected] and watch any perceived savings evaporate into thin air. along with your spare time.... seriously, its great.
I mean… they’re not totally wrong.