Internal Server Error after jellyseerr configures HTTP_PROXY

[PN62323424]

Description

As soon as I set up the http proxy, I get an Internal Server Error when I open jellyseerr.

I'm in the same situation as this post, here are my install commands:
#343

docker run -d \
--name jellyseerr \
-e LOG_LEVEL=debug \
-e TZ=Asia/Shanghai \
-e JELLYFIN_TYPE=emby \
-e HTTP_PROXY=http://openclash:17890 \
-e HTTPS_PROXY=http://openclash:17890 \
-p 5059:5055 \
-v /volume1/docker/jellyseerr:/app/config \
--restart=always \
fallenbagel/jellyseerr:latest

I tried to change it to this and it still doesn't work, I'm sure all the other containers I installed work fine with this http proxy:

-e HTTP_PROXY=http://192.168.31.100:17890 \
-e HTTPS_PROXY=http://192.168.31.100:17890 \

Version

1.7.0

Steps to Reproduce

It's mentioned above

Screenshots

No response

Logs

No response

Platform

desktop

Device

pc

Operating System

synology

Browser

chrome

Additional Context

No response

Code of Conduct

• I agree to follow Jellyseerr's Code of Conduct

[Fallenbagel]

Can you add the noproxy parts too

[PN62323424]

Can you add the noproxy parts too

thank you，It works now. but It’s a bit strange. Other containers don’t need to set the no_proxy variable

[Fallenbagel]

thank you，It works now. but It’s a bit strange. Other containers don’t need to set the no_proxy variable

That's because we have a health check to localhost so when proxies that would fuck up if localhost itself is going through the proxy

[Fallenbagel]

🎉 This issue has been resolved in version 2.1.0 🎉

The release is available on:

• v2.1.0
• GitHub release

Your semantic-release bot 📦🚀