-
-
Notifications
You must be signed in to change notification settings - Fork 281
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
Individual Proxy Setting needed #288
Comments
How are you setting up jellyseerr? Using |
nope... It's jellyseer's self healthcheck using localhost, I didn't modify that. |
#181 It's in fact the same problem with this closed issue. |
Have you tried exporting the no proxy env?
I used to do this exact thing on jellyfin before I got transparent proxy setup in router level. And my jellyfin health check would fail back then. Then I added the Not the solution to the exact the issue raised by worth a try as it might just solve the healthcheck thing |
You just taught me something new... Thanks and I'll try it. |
Great, it works~ I didn't know there's a env variable for |
Glad to have been of help and you got it working! c: |
🎉 This issue has been resolved in version 2.1.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
Firstly, please let me describe the situation I'm in.
I'm using k3s(you can just treat it as k8s), and I do need
clash proxy
to make my pods function well, including jellyseer establishing connection with imdb/tmdb.But it costs a lot packing clash into every docker image I deploy, so I made a
clash pod
, using k8s DNS for each pod to get proxy like this:It works properly most of the time.
However, in some application(like jellyseer), they use
localhost
for checking its own api's health. The env variables will cause all network going into clash pod, which don't know the so calledlocalhsot
is which address. And it lead it toclash pod's localhost
. So the jellyseer cannot launch properly, the internal error log is like this:[AxiosError: Request failed with status code 502]
Version
1.3.0
Steps to Reproduce
When setting the proxy env, and the proxy is not on this server, it will reproduce.
Screenshots
No response
Logs
No response
Platform
desktop
Device
PC
Operating System
Debian 9
Browser
Edge
Additional Context
What I think can fix this problem properly is to make a way for user to set proxy for jellyseer's tmdb or other external api connection, like I've seen in some other applications.
Thanks a lot for your viewing and glad to help or discussion.
Code of Conduct
The text was updated successfully, but these errors were encountered: