Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature] Ability to define a proxy in config #133

Closed
GordonFreemanK opened this issue Nov 26, 2024 · 2 comments
Closed

[feature] Ability to define a proxy in config #133

GordonFreemanK opened this issue Nov 26, 2024 · 2 comments
Labels
wontfix This will not be worked on

Comments

@GordonFreemanK
Copy link

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.

@Audionut
Copy link
Owner

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.

@Audionut Audionut added the wontfix This will not be worked on label Nov 27, 2024
@GordonFreemanK
Copy link
Author

Makes sense, I'll do that. Thanks for replying.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants