You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be nice to be able to define a proxy to use when doing requests to trackers (or any, really). This could be done using the built-in requests.get parameter e.g. requests.get(url, proxies={'https':'http://192.168.0.1:3130'})
I don't know how many people this could be useful for but I suspect this is the source of an issue I have uploading to a tracker: I normally browse the tracker website through a local proxy connected to a VPN (gluetun) but upload.py is connecting directly through my home IP. Possibly the tracker is refusing connections from two IPs at the same time? Anyway even if this isn't the issue if other people are doing VPN through proxies they might find this useful anyway.
I'd create a PR myself but I have this issue running locally.
The text was updated successfully, but these errors were encountered:
This is outside of scope. This is an upload assistant, not a network manager. If you have gluetun running and connections through both your local ethernet and vpn, then it sounds like you have split tunneling working, and need to correctly tunnel python as needed.
Would be nice to be able to define a proxy to use when doing requests to trackers (or any, really). This could be done using the built-in
requests.get
parameter e.g.requests.get(url, proxies={'https':'http://192.168.0.1:3130'})
I don't know how many people this could be useful for but I suspect this is the source of an issue I have uploading to a tracker: I normally browse the tracker website through a local proxy connected to a VPN (gluetun) but upload.py is connecting directly through my home IP. Possibly the tracker is refusing connections from two IPs at the same time? Anyway even if this isn't the issue if other people are doing VPN through proxies they might find this useful anyway.
I'd create a PR myself but I have this issue running locally.
The text was updated successfully, but these errors were encountered: