Jump to content
TorGuard
  • 1

torguard + unraid + qbittorrent (port forwarding issue)

Rate this question


pairofcrocs

Question

pairofcrocs

Okay so I can't figure this out for the life of me.

I've been having seeding ever since I switched to TorGuard, so naturally it seems like a port forwarding issue.

My download speed is fine, but I'm lucky if any of my 500+ linux isos are seeding at all, and when they do, its 100kbps ish

After talking with support they say it's not possible to forward a port and use it inside of unraid, which makes no since to me.

 

Anyone have this same problem with a fix?

 

Thanks!

Link to post
Share on other sites

6 answers to this question

Recommended Posts

  • 0
mindfrost82

Were you ever able to figure this out?  I'm using OpenVPN and Transmission in a Docker container and Transmission shows my port as open but I'm only able to seed to 1-2 peers at VERY slow speeds.

Link to post
Share on other sites
  • 0
On 4/22/2020 at 8:30 PM, mindfrost82 said:

Were you ever able to figure this out?  I'm using OpenVPN and Transmission in a Docker container and Transmission shows my port as open but I'm only able to seed to 1-2 peers at VERY slow speeds.

I'm using the same setup but I am unable to get the port to show as open. Any tips would be great.

I have set up port forwarding in TorGuard for port 51413, also have this forwarded on my router. I am unable to seed any torrents but can't download at decent speeds. I did notice however that if you restart the docker container you end up with a different i.p addess for the VPN so I had to change this in the port forwarding section of TorGuard settings.

For the life of me I can't figure out what im missing here.

Link to post
Share on other sites
  • 0
mindfrost82
On 5/15/2020 at 6:15 PM, BU5T4 said:

I'm using the same setup but I am unable to get the port to show as open. Any tips would be great.

I have set up port forwarding in TorGuard for port 51413, also have this forwarded on my router. I am unable to seed any torrents but can't download at decent speeds. I did notice however that if you restart the docker container you end up with a different i.p addess for the VPN so I had to change this in the port forwarding section of TorGuard settings.

For the life of me I can't figure out what im missing here.

I started using a Deluge container instead of Transmission and it seems to be working better.  I used Docker Compose and depending on the container, I'm able to set the IP address.  So I connect once, then get the IP and assign it in the Compose file so if the container restarts it'll use the same IP every time.

Link to post
Share on other sites
  • 0

Got it working for myself. Turned off port forwarding for those ports on my router. Requested the ports to be open on the VPN server. It still wasn't working so I rebooted my synology NAS and voila! Stopping and starting the Transmission service wasn't enough. I had to reboot the entire NAS for it to work.

Good luck!

Link to post
Share on other sites
  • 0
On 12/7/2020 at 1:21 AM, NeoGohan said:

Got it working for myself. Turned off port forwarding for those ports on my router. Requested the ports to be open on the VPN server. It still wasn't working so I rebooted my synology NAS and voila! Stopping and starting the Transmission service wasn't enough. I had to reboot the entire NAS for it to work.

Good luck!

 

Thanks @NeoGohan  - i have the same config but just cannot get it to work. ports are not being forwarded on router, the TRANSMISSION_PEER_PORT is set, i've requested port fowarding on that same port on VPN (matches the TRANSMISSION_PEER_PORT) -  (incidentally on the right hand side do you leave the Protocol and Auth/Port as default?  ie UDP / 1912)

I've set a port mapping on that container for the same port, I can see when i go into transmission web interface I click on spanner i con at bottom left, click the network tab  - port number is the right port (ie matches all the above, matches the port forwarding request setting) but it just says "closed" i haven't got the foggiest idea where i've gone wrong.  rebooted NAS about 10 times, double checked which VPN server i'm connecting to in the container logs, double checked there a port forward rule for it....at a complete loss for what to try next.

How did you get yours to work?

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...