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

Forward Proxy option #491

Closed
1 task done
spyhuntergenral opened this issue Sep 20, 2023 · 7 comments · Fixed by #1031
Closed
1 task done

Forward Proxy option #491

spyhuntergenral opened this issue Sep 20, 2023 · 7 comments · Fixed by #1031
Labels
awaiting triage This issue needs to be reviewed enhancement New feature or request released

Comments

@spyhuntergenral
Copy link

Description

Currently all outbound internet requests follow the default network path,

Desired Behavior

Add the ability to set proxy options in the GUI settings

i.e external web requests to "api.themoviedb.org" would get proxied via a network proxy (http/https or socks5)

Additional Context

No response

Code of Conduct

  • I agree to follow Overseerr's Code of Conduct
@Fallenbagel
Copy link
Owner

If on docker you can set the proxy through the environment (although some people had issues with it, from my testings http/https/socks5) worked pretty well

@spyhuntergenral
Copy link
Author

spyhuntergenral commented Sep 21, 2023

Yes running in docker, version: 1.7.0

i gave that a go, I'm assuming you meant something like this in the compose file:

   environment:
      HTTP_PROXY: 'http://xxx.xxx.xxx.xxx:xxxx'
      HTTPS_PROXY: 'http://xxx.xxx.xxx.xxx:xxxx'
      NO_PROXY: 'localhost,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16'

||

    environment:
      HTTP_PROXY: 'socks5://xxx.xxx.xxx.xxx:xxxx'
      HTTPS_PROXY: 'socks5://xxx.xxx.xxx.xxx:xxxx'
      NO_PROXY: 'localhost,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16'

didn't like it...

i got these errors from jellyseer:
when using socks {"errorMessage":"protocol mismatch"}
when using http/s: {"errorMessage":"Request failed with status code 405"}

and regardless if any proxy env's where set i lost connection to my jellyfin,radarr and sonarr, so its not respecting the no_proxy env

I have both radarr and sonarr + a few other things pointed at this proxy and they all work ok.

Am interested in knowing how you have yours setup??

@Fallenbagel
Copy link
Owner

That's not how you set it

environment:
     HTTPS_PROXY=http://192.168.100.1:8000

Should be an = sign

@spyhuntergenral
Copy link
Author

What?? that's just yaml syntax?

@Fallenbagel
Copy link
Owner

Fallenbagel commented Oct 2, 2023

What?? that's just yaml syntax?

This is the environment block. In this block its an equal sign to set environment variables. Maybe you might want to read the docs

Or check this #343 (comment)

@spyhuntergenral
Copy link
Author

I see,
Thanks for linking that other issue, it was the '' causing my problems.

I still suggest having proxy settings at the application level, like the other *arrs. makes for a more uniformed config experience. never the less is working now.

@gauthier-th gauthier-th changed the title [Feature Request] Forward Proxy option Forward Proxy option Sep 16, 2024
@gauthier-th gauthier-th added enhancement New feature or request awaiting triage This issue needs to be reviewed labels Sep 16, 2024
@Fallenbagel
Copy link
Owner

🎉 This issue has been resolved in version 2.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting triage This issue needs to be reviewed enhancement New feature or request released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants