search

haugene / vpn-configs-contrib

A collection of configs for various VPN providers
GNU General Public License v3.0
188 stars 752 forks source link

Some torrents get stuck at Magnetized transfer - retrieving metadata 0% #49

Closed Marelebone closed 11 months ago

Marelebone commented 3 years ago

Is there a pinned issue for this?

Is there an existing or similar issue for this?

Is there any comment in the documentation for this?

Is this related to a provider?

Are you using the latest release?

Have you tried using the dev branch latest?

Config used

version: '3.3'

transmission-vpn: container_name: transmission-vpn image: haugene/transmission-openvpn cap_add:

Current Behavior

Most torrents download perfectly fine using Haugene's transmission-vpn. Since approx. one month however some torrents get stuck at Magnetized transfer - retrieving metadata 0%. This problem seems only to appear when using public trackers.

I tested these torrents on my laptop with qbitorrent and connecting to PIA and it works just fine. So it seems for certain torrents transmission can't connect to peers.

I am not sure if it has something to do with ipv6 WARNING: OpenVPN was configured to add an IPv6 route over tun0. However, no IPv6 has been configured for this interface, therefore the route installation may fail or may not work as expected. nor do I know how to fix this error.

Expected Behavior

Download of all torrents if seeders are available.

How have you tried to solve the problem?

1) Restarted docker container 2) Restarted server 3) Changed DNS in .yml from 1.1.1.1/1.0.0.1 to 8.8.8.8/8.8.4.4

Log output

transmission-vpn | STARTING TRANSMISSION transmission-vpn | Provider PIA has a script for automatic port forwarding. Will run it now. transmission-vpn | If you want to disable this, set environment variable DISABLE_PORT_UPDATER=true transmission-vpn | Transmission startup script complete. transmission-vpn | Mon Sep 6 12:04:26 2021 WARNING: OpenVPN was configured to add an IPv6 route over tun0. However, no IPv6 has been configured for this interface, therefore the route installation may fail or may not work as expected. transmission-vpn | Mon Sep 6 12:04:26 2021 Initialization Sequence Completed transmission-vpn | Running functions for token based port fowarding transmission-vpn | Reserved Port: 25848 Mon Sep 6 12:04:33 CEST 2021 transmission-vpn | transmission auth not required transmission-vpn | waiting for transmission to become responsive transmission-vpn | transmission became responsive transmission-vpn | 6 100% 6.22 MB Done 0.0 0.0 0.0 Idle
transmission-vpn | Sum: 110.5 GB 0.0 0.0 transmission-vpn | setting transmission port to 25848 transmission-vpn | localhost:9091/transmission/rpc/ responded: "success" transmission-vpn | Checking port... transmission-vpn | Port is open: Yes transmission-vpn | ####################### transmission-vpn | SUCCESS
transmission-vpn | #######################

In the transmission.log file i often see these messages: [2021-09-06 13:10:23.266] Couldn't connect socket 120 to 2a05:4f44:b13:4e00::2, port 32247 (errno 99 - Cannot assign requested address) (net.c:288)

Please let me know if further logs are required

Environment

- OS: Ubuntu 20.04
- Docker: 20.10.7
- VPN Provider: PrivateInternetAccess

Anything else?

No response

nickysemenza commented 3 years ago

I got this too with PIA, switching back to 3.7.1 resolved it for me

pkishino commented 3 years ago

can you post your /etc/resolv.conf please (from the container)? have you tried loading the torrent file directly instead of magnet? I wonder if those tracker are having issue with transmission 2.95 (using now) vs 3.0 (used in 3.7*)

pilotman28 commented 3 years ago

I got this too with PIA, switching back to 3.7.1 resolved it for me

Cheers! Worked for me too. My problem however was none of my torrents were showing in the WebUI and none of the WebUI buttons responded to clicks.

Marelebone commented 3 years ago

can you post your /etc/resolv.conf please (from the container)? have you tried loading the torrent file directly instead of magnet? I wonder if those tracker are having issue with transmission 2.95 (using now) vs 3.0 (used in 3.7*)

I am not sure if I did this correctly. Here is what I did

  1. docker exec -it transmission-vpn bash
  2. apt update && apt install -y vim
  3. vim /etc/resolv.conf

Here is the output:

nameserver 127.0.0.11
options edns0 trust-ad ndots:0

And yes I tried to load the torrent file directly. But the torrent remains idle (downloading from 0 of 0 peers)

Many thanks

pkishino commented 3 years ago

no need for vim.. can jut use built-in cat ;) well, if the peers are 0 then that would explain it..nobody to fetch it from.. I have the same behaviour from torrents with 0 peers..magnets won't get metadata.. so I wonder if the trackers you are connecting to are blocking this "older" transmission client..

Marelebone commented 3 years ago

I got this too with PIA, switching back to 3.7.1 resolved it for me

Many thanks. How would I switch back to v3.7.1? And I assume that with version 3.7.1 you won't get updates anymore as Haugene stated here #1937, correct?

Marelebone commented 3 years ago

no need for vim.. can jut use built-in cat ;) well, if the peers are 0 then that would explain it..nobody to fetch it from.. I have the same behaviour from torrents with 0 peers..magnets won't get metadata.. so I wonder if the trackers you are connecting to are blocking this "older" transmission client..

Many thanks for your reply! What is strange though is that some torrents from the same public torrent site work and others dont.

But I could try downloading transmission 2.9.4 on my PC and check wether I am able to download the exact same torrent files there

pkishino commented 3 years ago

Instead of pulling latest, you can specify the 3.7.1 tag

On Tue, Sep 7, 2021 at 16:41 Marelebone @.***> wrote:

no need for vim.. can jut use built-in cat ;) well, if the peers are 0 then that would explain it..nobody to fetch it from.. I have the same behaviour from torrents with 0 peers..magnets won't get metadata.. so I wonder if the trackers you are connecting to are blocking this "older" transmission client..

Many thanks for your reply! What is strange though is that some torrents from the same public torrent site work and others dont.

But I could try downloading transmission 2.9.4 on my PC and check wether I am able to download the exact same torrent files there

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/haugene/docker-transmission-openvpn/issues/1940#issuecomment-914068774, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7OFYXYM7AT3TB23SQSGHLUAW63DANCNFSM5DQ5LFZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Marelebone commented 3 years ago

Instead of pulling latest, you can specify the 3.7.1 tag … On Tue, Sep 7, 2021 at 16:41 Marelebone @.***> wrote: no need for vim.. can jut use built-in cat ;) well, if the peers are 0 then that would explain it..nobody to fetch it from.. I have the same behaviour from torrents with 0 peers..magnets won't get metadata.. so I wonder if the trackers you are connecting to are blocking this "older" transmission client.. Many thanks for your reply! What is strange though is that some torrents from the same public torrent site work and others dont. But I could try downloading transmission 2.9.4 on my PC and check wether I am able to download the exact same torrent files there — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1940 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7OFYXYM7AT3TB23SQSGHLUAW63DANCNFSM5DQ5LFZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thanks for your explanation!

I installed both transmission on my PC 3.00 and 2.94 and added the torrent file which wouldn't download in my container earlier. Apparently it doesn't download with either versions of transmission. Could this mean that the trackers I am connecting to are blocking transmission in general? As stated in my original post the problem first appeared over one month ago and not since transmission downgrade 3 days ago

pkishino commented 3 years ago

So if it doesn’t work with transmission app either then it’s not related to this container. That’s good at least. But yes, it could be related to the tracker blocking.. you mentioned you tried another client and it worked? Could you see if the torrent is available on another tracker? Or share the link and I can try?

On Tue, Sep 7, 2021 at 18:03 Marelebone @.***> wrote:

Instead of pulling latest, you can specify the 3.7.1 tag … <#m-7072681893112475440> On Tue, Sep 7, 2021 at 16:41 Marelebone @.***> wrote: no need for vim.. can jut use built-in cat ;) well, if the peers are 0 then that would explain it..nobody to fetch it from.. I have the same behaviour from torrents with 0 peers..magnets won't get metadata.. so I wonder if the trackers you are connecting to are blocking this "older" transmission client.. Many thanks for your reply! What is strange though is that some torrents from the same public torrent site work and others dont. But I could try downloading transmission 2.9.4 on my PC and check wether I am able to download the exact same torrent files there — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1940 (comment) https://github.com/haugene/docker-transmission-openvpn/issues/1940#issuecomment-914068774>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7OFYXYM7AT3TB23SQSGHLUAW63DANCNFSM5DQ5LFZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

Thanks for your explanation!

I installed both transmission on my PC 3.00 and 2.94 and added the torrent file which wouldn't download in my container earlier. Apparently it doesn't download with either versions of transmission. Could this mean that the trackers I am connecting to are blocking transmission in general? As stated in my original post the problem first appeared over one month ago and not since transmission downgrade 3 days ago

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/haugene/docker-transmission-openvpn/issues/1940#issuecomment-914127200, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7OFYUIGISDEC6S7427H6TUAXIOBANCNFSM5DQ5LFZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Marelebone commented 3 years ago

So if it doesn’t work with transmission app either then it’s not related to this container. That’s good at least. But yes, it could be related to the tracker blocking.. you mentioned you tried another client and it worked? Could you see if the torrent is available on another tracker? Or share the link and I can try? … On Tue, Sep 7, 2021 at 18:03 Marelebone @.> wrote: Instead of pulling latest, you can specify the 3.7.1 tag … <#m-7072681893112475440> On Tue, Sep 7, 2021 at 16:41 Marelebone @.> wrote: no need for vim.. can jut use built-in cat ;) well, if the peers are 0 then that would explain it..nobody to fetch it from.. I have the same behaviour from torrents with 0 peers..magnets won't get metadata.. so I wonder if the trackers you are connecting to are blocking this "older" transmission client.. Many thanks for your reply! What is strange though is that some torrents from the same public torrent site work and others dont. But I could try downloading transmission 2.9.4 on my PC and check wether I am able to download the exact same torrent files there — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1940 (comment) <#1940 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7OFYXYM7AT3TB23SQSGHLUAW63DANCNFSM5DQ5LFZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . Thanks for your explanation! I installed both transmission on my PC 3.00 and 2.94 and added the torrent file which wouldn't download in my container earlier. Apparently it doesn't download with either versions of transmission. Could this mean that the trackers I am connecting to are blocking transmission in general? As stated in my original post the problem first appeared over one month ago and not since transmission downgrade 3 days ago — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1940 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7OFYUIGISDEC6S7427H6TUAXIOBANCNFSM5DQ5LFZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Yes I was able to download the torrent using qbittorrent.

Since I am new to this topic and don't exactly understand what you want me to do please find here the link to the torrent file I am referring. Could you please let me know the outcome of your research? Many thanks

pkishino commented 3 years ago

I had no problems with that magnet link using latest. Using PrivateVPN.. perhaps provider issues? Try changing DNS perhaps?

Marelebone commented 3 years ago

I had no problems with that magnet link using latest. Using PrivateVPN.. perhaps provider issues? Try changing DNS perhaps?

Thanks! Then I really don't understand what I am doing wrong. I allready changed DNS in the .yml file from 1.1.1.1/1.0.0.1 to 8.8.8.8/8.8.4.4 (see config used). But it didn't help. Do you think the error warning in the log file could have something to do with it? WARNING: OpenVPN was configured to add an IPv6 route over tun0. However, no IPv6 has been configured for this interface, therefore the route installation may fail or may not work as expected.

technowhizz commented 3 years ago

+1 I too have this issue but with purevpn

pkishino commented 3 years ago

@technowhizz does your PR #47 fix this? just tagging for reference.

technowhizz commented 3 years ago

@technowhizz does your PR #47 fix this? just tagging for reference.

Unfortunately not

pkishino commented 3 years ago

oh, too bad.. I suggest first to validate dns settings in /etc/resolv.conf inside container.. and to try to ping the hostname of the tracker to see if that works.

technowhizz commented 3 years ago

I tried a different config file and its now working. Turns out only some purevpn servers support torrenting/p2p

pkishino commented 3 years ago

Still a problem?

technowhizz commented 3 years ago

Nope :)

Marelebone commented 3 years ago

For me unforetunately yes

pkishino commented 3 years ago

@Marelebone can you try latest please and remove the dns settings from config? Also you can add the following line to config: sysctls:

Marelebone commented 3 years ago

I am running latest (name of image in Portainer is: haugene/transmission-openvpn:latest).

By adjusting config you mean the .yml file I posted in my original post?

pkishino commented 3 years ago

Yes, the compose