请问如何设置代理呢

Description
请问如何设置代理呢，我在设置里未找到可以设置代理的界面
Desired Behavior
可以设置代理成功
Additional Context
No response
Code of Conduct

[X] I agree to follow Overseerr's Code of Conduct

Proxy can be set in docker-compose as such
version: 'latest'
services:
  jellyseerr:
       image: fallenbagel/jellyseerr:latest
       container_name: jellyseerr
       hostname: jellyseer
       network_mode: bridge
       environment:
         - http_proxy="http://proxy:8080"
         - https_proxy="http://proxy:8080"
         - no_proxy="localhost,<IP_ADDRESS>"
        - LOG_LEVEL=debug
        - TZ=America/New_York
       ports:
            - 5055:5055
       volumes:
            - /path/to/config:/app/config
       restart: always

Or if youre running natively
export http_proxy="http://proxy:8080"
export https_proxy="http://proxy:8080"
export no_proxy="localhost,<IP_ADDRESS>"

Proxy can be set in docker-compose as such可以在 docker-compose 中设置代理
version: 'latest'
services:
  jellyseerr:
       image: fallenbagel/jellyseerr:latest
       container_name: jellyseerr
       hostname: jellyseer
       network_mode: bridge
       environment:
        - http_proxy="http://proxy:8080"
        - https_proxy="http://proxy:8080"
        - no_proxy="localhost,<IP_ADDRESS>"
        - LOG_LEVEL=debug
        - TZ=America/New_York
       ports:
            - 5055:5055
       volumes:
            - /path/to/config:/app/config
       restart: always

Or if youre running natively 或者如果你在本地运行
export http_proxy="http://proxy:8080"
export https_proxy="http://proxy:8080"
export no_proxy="localhost,<IP_ADDRESS>"

你好，我是在windows下安装的jellyseerr。

请问我该如何设置代理呢？

You can use the global proxy settings in Windows. It will affect jellyseerr as well
您可以在 Windows 中使用全局代理设置。它也会影响 jellyseerr

jellyseerr:
image: fallenbagel/jellyseerr:latest
container_name: jellyseerr
hostname: jellyseer
network_mode: bridge

When I set the proxy server, I can't open the web,Prompt internal server error
When I cancel the agent, everything returns to normal

hmm Weird. I got it working

And I know the proxy is working because when i exec into the container and run apk add curl && curl ident.me It shows my proxy ip

jellyseerr:
image: fallenbagel/jellyseerr:latest
container_name: jellyseerr
hostname: jellyseer
network_mode: bridge

When I set the proxy server, I can't open the web,Prompt internal server error
When I cancel the agent, everything returns to normal

Please note that there should be no quotation marks after HTTP_PROXY and HTTPS_PROXY in your yaml.
However, after configuring according to @Fallenbagel's format, I encountered a 500 Internal Server Error on all of my pages.

jellyseerr:
image: fallenbagel/jellyseerr:latest
container_name: jellyseerr
hostname: jellyseer
network_mode: bridge

When I set the proxy server, I can't open the web,Prompt internal server error
When I cancel the agent, everything returns to normal

Please note that there should be no quotation marks after HTTP_PROXY and HTTPS_PROXY in your yaml.
However, after configuring according to @Fallenbagel's format, I encountered a 500 Internal Server Error on all of my pages.

Could you exec into the container and do a curl to your proxy or sth. To see if the container can reach your proxy. Another thing you could try is putting it into host mode and adding the http_proxies. My guess is that the container can't reach the local proxy so throwing 500 errors

jellyseerr:
image: fallenbagel/jellyseerr:latest
container_name: jellyseerr
hostname: jellyseer
network_mode: bridge

When I set the proxy server, I can't open the web,Prompt internal server error
When I cancel the agent, everything returns to normal

Please note that there should be no quotation marks after HTTP_PROXY and HTTPS_PROXY in your yaml.
However, after configuring according to @Fallenbagel's format, I encountered a 500 Internal Server Error on all of my pages.

Could you exec into the container and do a curl to your proxy or sth. To see if the container can reach your proxy. Another thing you could try is putting it into host mode and adding the http_proxies. My guess is that the container can't reach the local proxy so throwing 500 errors

First of all, thank you for your reply! I have tested the connection to the proxy server using the method you mentioned, and it seems to be working fine. The IP address used is that of my proxy server, and I am able to access websites like Google without any issues (I am in mainland China). However, I keep encountering similar errors in the backend of my container. Could you please take a look at them?

2023-07-25T05:53:59.971Z [error][Jellyfin Sync]: Sync interrupted {"errorMessage":"Sync was aborted."} 2023-07-25T05:54:00.007Z [debug][Jobs]: Starting scheduled job: Download Sync  2023-07-25T05:54:07.893Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:07.981Z [debug][API]: Something went wrong retrieving trending items {"errorMessage":"[TMDB] Failed to fetch all trending: Request failed with status code 400"} 2023-07-25T05:54:08.078Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch movie genres: Request failed with status code 400"} 2023-07-25T05:54:08.735Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-07-25T05:54:08.892Z [debug][API]: Something went wrong retrieving movie {"errorMessage":"[TMDB] Failed to fetch movie details: Request failed with status code 400","movieId":"889575"} 2023-07-25T05:54:08.895Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch TV genres: Request failed with status code 400"} 2023-07-25T05:54:08.901Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:08.979Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:08.981Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:13.437Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:14.028Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch movie genres: Request failed with status code 400"} 2023-07-25T05:54:14.037Z [debug][API]: Something went wrong retrieving trending items {"errorMessage":"[TMDB] Failed to fetch all trending: Request failed with status code 400"} 2023-07-25T05:54:15.402Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:15.505Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:15.507Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch TV genres: Request failed with status code 400"} 2023-07-25T05:54:20.034Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:24.739Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:25.273Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:25.275Z [debug][API]: Something went wrong retrieving trending items {"errorMessage":"[TMDB] Failed to fetch all trending: Request failed with status code 400"} 2023-07-25T05:54:25.287Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch movie genres: Request failed with status code 400"} 2023-07-25T05:54:25.371Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:25.373Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch TV genres: Request failed with status code 400"} 2023-07-25T05:54:25.933Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-07-25T05:54:26.776Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:27.198Z [debug][API]: Something went wrong retrieving movie {"errorMessage":"[TMDB] Failed to fetch movie details: Request failed with status code 400","movieId":"889575"} 2023-07-25T05:54:29.611Z [debug][API]: Something went wrong retrieving movies by studio {"errorMessage":"[TMDB] Failed to fetch movie studio: Request failed with status code 400","studioId":"127928"} 2023-07-25T05:54:31.316Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:32.976Z [debug][API]: Something went wrong retrieving trending items {"errorMessage":"[TMDB] Failed to fetch all trending: Request failed with status code 400"} 2023-07-25T05:54:32.980Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:32.982Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:32.984Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch movie genres: Request failed with status code 400"} 2023-07-25T05:54:32.991Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:33.002Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch TV genres: Request failed with status code 400"} 2023-07-25T05:54:34.175Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:34.316Z [debug][API]: Something went wrong retrieving movie {"errorMessage":"[TMDB] Failed to fetch movie details: Request failed with status code 400","movieId":"889575"} 2023-07-25T05:54:35.535Z [debug][API]: Something went wrong retrieving movies by studio {"errorMessage":"[TMDB] Failed to fetch movie studio: Request failed with status code 400","studioId":"34"} 2023-07-25T05:54:39.604Z [debug][API]: Something went wrong retrieving movies by studio {"errorMessage":"[TMDB] Failed to fetch movie studio: Request failed with status code 400","studioId":"34"} 2023-07-25T05:54:40.305Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-07-25T05:54:46.129Z [debug][API]: Something went wrong retrieving movies by studio {"errorMessage":"[TMDB] Failed to fetch movie studio: Request failed with status code 400","studioId":"34"} 2023-07-25T05:55:00.013Z [debug][Jobs]: Starting scheduled job: Download Sync  2023-07-25T05:55:00.015Z [info][Jobs]: Starting scheduled job: Jellyfin Recently Added Sync  2023-07-25T05:55:00.016Z [info][Jellyfin Sync]: Jellyfin Sync Starting {"sessionId":"c75ca00e-3fc2-4db8-9f9e-184ce15eff68"} 2023-07-25T05:55:00.018Z [info][Jellyfin Sync]: Beginning to process recently added for library: 动画  2023-07-25T05:55:00.144Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: 9148aad7b8c38298dfe5afdb6f9cc6c2 {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"久保同学不放过我","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"9148aad7b8c38298dfe5afdb6f9cc6c2","PremiereDate":"2023-01-10T00:00:00.0000000Z","OfficialRating":"TV-14","ChannelId":null,"CommunityRating":6.4,"RunTimeTicks":14400000000,"ProductionYear":2023,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":12,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"420084"},"ChildCount":2,"Status":"Ended","AirTime":"2023-01-10","AirDays":["Tuesday"],"DisplayOrder":"aired","ImageTags":{"Primary":"09aa263a29311a45dd22f94254305ed2","Banner":"dd4589e1e2728452ffdf8a27c4f3cdae","Logo":"cf0f24a5856f3152c913153705357f44","Thumb":"15c6e586c16ceadeecdf5a7992f8611a"},"BackdropImageTags":["14403ceccf6cc57f073757589b07f321"],"ImageBlurHashes":{"Backdrop":{"14403ceccf6cc57f073757589b07f321":"WYE|YpIdF|_4p0JBXRxwk8NLogS0S~RPs:bcofs:b_NGozxuogt7"},"Primary":{"09aa263a29311a45dd22f94254305ed2":"dTOD5@57$*EL?^s;RPr?-:o|IUWCX8ozxua}ogX9kVxZ"},"Banner":{"dd4589e1e2728452ffdf8a27c4f3cdae":"H~QJAt.8aKoN-;tQjaxuoz~qxbaKaft7kCkCt7bb"},"Logo":{"cf0f24a5856f3152c913153705357f44":"OIRfd|RQ-p-Vi^-:Na~CrERjJ7N@XSRjx]oLRjj[bHRje:"},"Thumb":{"15c6e586c16ceadeecdf5a7992f8611a":"NeQ0Er9FD%yDtS?I_4o#kXt7njjF?bbIRmn,WBbc"}},"LocationType":"FileSystem","EndDate":"2023-06-20T00:00:00.0000000Z"}} 2023-07-25T05:55:00.148Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: 922e69cd40cc47372b992e84787b535f {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"Fate/stay night [Unlimited Blade Works]","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"922e69cd40cc47372b992e84787b535f","PremiereDate":"2014-10-04T00:00:00.0000000Z","OfficialRating":"TV-14","ChannelId":null,"CommunityRating":7.5,"RunTimeTicks":14400000000,"ProductionYear":2014,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":27,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"278626"},"ChildCount":27,"Status":"Ended","AirTime":"2014-10-04","AirDays":["Saturday"],"DisplayOrder":"aired","ImageTags":{"Primary":"4233a15db2384125d1471557b9909018","Banner":"7c7a78f90072ae461412902000c0d47e","Logo":"54a5e3d6582f71b92c7514769b7439da"},"BackdropImageTags":["cc179b3a7e2e192c899d7a0ff33dcb02"],"ImageBlurHashes":{"Backdrop":{"cc179b3a7e2e192c899d7a0ff33dcb02":"WOHvx6r@Ip$*5rxZ9IxZ5lNbxtNH9_NHtQJ8-7xZ~9t6NHj[M#xF"},"Primary":{"4233a15db2384125d1471557b9909018":"daK[oD-oafwK?Z%1NHI;}=xaRQaKx[s+RQj[o|S5jGW;"},"Banner":{"7c7a78f90072ae461412902000c0d47e":"HJEcwf}Y-Aw^OBobbrXRS}xGoLNHoL$%R+afj[WV"},"Logo":{"54a5e3d6582f71b92c7514769b7439da":"OC7A#ooK9ZX8RjWBozWqa|ofoLWBayWB0eWq-pnit7ofWB"}},"LocationType":"FileSystem","EndDate":"2015-06-28T00:00:00.0000000Z"}} 2023-07-25T05:55:00.149Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: 21d7e53792d75e2d5cef0098bd882e2d {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"【我推的孩子】","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"21d7e53792d75e2d5cef0098bd882e2d","PremiereDate":"2023-04-12T00:00:00.0000000Z","OfficialRating":"TV-14","ChannelId":null,"CommunityRating":7.6,"RunTimeTicks":14400000000,"ProductionYear":2023,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":11,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"421069"},"ChildCount":3,"Status":"Continuing","AirTime":"2023-04-12","AirDays":["Wednesday"],"DisplayOrder":"aired","ImageTags":{"Primary":"9cfddd71ca16c6326f33d28ae8a2d4e2","Banner":"f9f1050355b87ed35c33e96a043a9d32","Logo":"cbcd51b286faee521e7ee3fa6f168332","Thumb":"6ce8506c8966f48a0e3838a4b6e0e772"},"BackdropImageTags":["ec2a3cb06f17461ae19f4b3a610319e7"],"ImageBlurHashes":{"Backdrop":{"ec2a3cb06f17461ae19f4b3a610319e7":"WfM?D7?^kq~VyW%3ogxv%g-oS4M}TJs;n5o|RjM{?HxukVxaW;of"},"Primary":{"9cfddd71ca16c6326f33d28ae8a2d4e2":"dXJ~{3|y:u=}}K#m#s$j9Rn5%KnP#bwbt3V{^Rnhf,wP"},"Banner":{"f9f1050355b87ed35c33e96a043a9d32":"H,CQQWo}NHt8tRxwxcSNac-@t8W?t7oyxut7bbax"},"Logo":{"cbcd51b286faee521e7ee3fa6f168332":"ORC?Q6%M.8R6sCN@t7j[ayofjujtayj[0KM{R6o|buxGe:"},"Thumb":{"6ce8506c8966f48a0e3838a4b6e0e772":"NoFh}CxbIloyMxVs?dozNEoeenWAcDf+R*oIoMWY"}},"LocationType":"FileSystem","EndDate":"2020-03-27T00:00:00.0000000Z"}} 2023-07-25T05:55:00.155Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: 010665d585f9f9e83ad5bfc2d6aecba6 {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"偶像大师 灰姑娘女孩 U149","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"010665d585f9f9e83ad5bfc2d6aecba6","PremiereDate":"2023-04-05T00:00:00.0000000Z","OfficialRating":"10","ChannelId":null,"CommunityRating":7.9,"RunTimeTicks":14400000000,"ProductionYear":2023,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":12,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"424278"},"ChildCount":7,"Status":"Ended","AirTime":"2023-04-05","AirDays":["Wednesday"],"DisplayOrder":"aired","ImageTags":{"Primary":"d80e5cac0592545543c4a521794b2ac8","Logo":"bfe110db1f15852ccaf470023e3bb714","Thumb":"f8481c645d5136272bc1e6b15afec910"},"BackdropImageTags":["34564053659546580626e709204a4006"],"ImageBlurHashes":{"Backdrop":{"34564053659546580626e709204a4006":"WPNmAx.R_N^+xu?vx@-;%3W.Sia{s$-pNFi^I[ae~U-.R*t5IWNb"},"Primary":{"d80e5cac0592545543c4a521794b2ac8":"dcI5[BpfIok=CQpIs*X6x-xsn#em%3RqM|nOtlkDnjWC"},"Logo":{"bfe110db1f15852ccaf470023e3bb714":"OaL|.kt7}?oeiwozM{GakBo|j]-oV@so9]VtjEbFW;ozt7"},"Thumb":{"f8481c645d5136272bc1e6b15afec910":"NPHC.vGwo[tRIntTL3-CMOVZVttQIZw}r]WCxnxV"}},"LocationType":"FileSystem","EndDate":"2023-06-29T00:00:00.0000000Z"}} 2023-07-25T05:55:00.162Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: bfed7e898464fae6a06b3a0da48f8567 {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"白圣女与黑牧师","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"bfed7e898464fae6a06b3a0da48f8567","PremiereDate":"2023-07-12T00:00:00.0000000Z","OfficialRating":"TV-14","ChannelId":null,"CommunityRating":7,"RunTimeTicks":14400000000,"ProductionYear":2023,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":2,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"421283"},"ChildCount":2,"Status":"Continuing","AirTime":"2023-07-12","AirDays":["Wednesday"],"DisplayOrder":"aired","ImageTags":{"Primary":"fa62d3f0ca672f73bf80c32d86137135","Logo":"b99378dc2c78b772e9291361bacc389a"},"BackdropImageTags":["dd6c14e1867023aa5cd34fe2f59dd5e7"],"ImageBlurHashes":{"Backdrop":{"dd6c14e1867023aa5cd34fe2f59dd5e7":"WuP?HkS*%K~V%ft6^*o~XAo0WBj]$xo#W;RjV[oz?GbdkXs,oKj]"},"Primary":{"fa62d3f0ca672f73bf80c32d86137135":"dYLzy^.8M_%1~XbvaKspyEW=RQS2FNoes,kDNHi_n$g3"},"Logo":{"b99378dc2c78b772e9291361bacc389a":"HHQP4+#n.=i{LIxZv4#AP8_kS}rsofKhbH#mSzO="}},"LocationType":"FileSystem"}} 2023-07-25T05:55:00.166Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: 32ed4e0b0477690c8470707fbe08ee6a {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"和山田谈场Lv999的恋爱","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"32ed4e0b0477690c8470707fbe08ee6a","PremiereDate":"2023-04-01T00:00:00.0000000Z","OfficialRating":"TV-14","ChannelId":null,"CommunityRating":6.6,"RunTimeTicks":14400000000,"ProductionYear":2023,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":13,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"423413"},"ChildCount":3,"Status":"Ended","AirTime":"2023-04-01","AirDays":["Saturday"],"DisplayOrder":"aired","ImageTags":{"Primary":"853a8fdb8e4039623abb2ec79a65729d","Banner":"c1955b56cbb40ed83f5fa76494902675","Logo":"7f5cdec98262ae21d1102acde4f01724","Thumb":"20da3d9d7ada1a76d48826087d8f7871"},"BackdropImageTags":["9f3df409aa41b8a9a86dfab1e9ff6fef"],"ImageBlurHashes":{"Backdrop":{"9f3df409aa41b8a9a86dfab1e9ff6fef":"WhM%yGMy$y?GM{t7~prsN2r@xGX9XSM{nObct6ni%MWBnhs;WYay"},"Primary":{"853a8fdb8e4039623abb2ec79a65729d":"dZMZ]*RQ,-^j?^t7EOSL^*xZN1aMXoRlr;R.ozo|SwS5"},"Banner":{"c1955b56cbb40ed83f5fa76494902675":"H*OM+_sqbboNxZ%1Nbo#aK~qtQWFWBt6t7bvWWWA"},"Logo":{"7f5cdec98262ae21d1102acde4f01724":"OjFrksay0Jj[RjkCxuWBfkWBjut7WBf7NZWVnif6t7s:of"},"Thumb":{"20da3d9d7ada1a76d48826087d8f7871":"NdLX9[IC-P?ZRixs_MrrN1xaxFR-TJIVr=g3s:V?"}},"LocationType":"FileSystem","EndDate":"2023-06-25T00:00:00.0000000Z"}} 2023-07-25T05:55:04.176Z [info][Jellyfin Sync]: Beginning to process recently added for library: 电影  2023-07-25T05:55:04.311Z [error][Jellyfin Sync]: Failed to process Jellyfin item, id: ec08556cba757fcac1c8aae4a319ca6c {"errorMessage":"[TMDB] Failed to find media using external IMDb ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"碟中谍4：幽灵协议","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"ec08556cba757fcac1c8aae4a319ca6c","HasSubtitles":true,"Container":"mkv,webm","PremiereDate":"2011-12-07T00:00:00.0000000Z","OfficialRating":"PG-13","ChannelId":null,"CommunityRating":7.1,"RunTimeTicks":79771197440,"ProductionYear":2011,"IsFolder":false,"Type":"Movie","UserData":{"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"56292"},"ChildCount":0,"VideoType":"VideoFile","ImageTags":{"Primary":"929c581c66fe6f8699ab3145db49e751","Logo":"b32b9bc24d9bd00bf4d310bdbd4214e1","Thumb":"2dde7973553a591aa028f65537a9dd2c"},"BackdropImageTags":["9d03e287fb200d0c363054b5d00a4781"],"ImageBlurHashes":{"Backdrop":{"9d03e287fb200d0c363054b5d00a4781":"W#IWx;%1-T%1bHso~TtPs.xZkBoL-oofNHoej[jt-nR+RkayWVjZ"},"Primary":{"929c581c66fe6f8699ab3145db49e751":"dKECOUJ.E1~WyE%1IoofD%WY%19GE2%1xZM{?bR-R*t7"},"Logo":{"b32b9bc24d9bd00bf4d310bdbd4214e1":"O$N,GJMxtRt7WBt7kC~CiwX8ozV@kCj[8_R5ozfke.kCkC"},"Thumb":{"2dde7973553a591aa028f65537a9dd2c":"NdKAD*?G=s-.-pxt^aR%xtxYM{Rk~VX9Ipt6RlWC"}},"LocationType":"FileSystem","MediaType":"Video"}} 2023-07-25T05:55:04.322Z [error][Jellyfin Sync]: Failed to process Jellyfin item, id: 44fa137f65390aad226ac5b9f1559b65 {"errorMessage":"[TMDB] Failed to find media using external IMDb ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"命运之夜：无限剑制","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"44fa137f65390aad226ac5b9f1559b65","HasSubtitles":true,"Container":"mkv,webm","PremiereDate":"2010-01-23T00:00:00.0000000Z","ChannelId":null,"CommunityRating":7.121,"RunTimeTicks":63413350400,"ProductionYear":2010,"IsFolder":false,"Type":"Movie","UserData":{"PlayedPercentage":21.627196660468517,"PlaybackPositionTicks":13714530000,"PlayCount":2,"IsFavorite":false,"LastPlayedDate":"2023-07-18T10:10:03.0218628Z","Played":false,"Key":"46304"},"ChildCount":0,"VideoType":"VideoFile","ImageTags":{"Primary":"fe8a07fabcab825558d709454b668538"},"BackdropImageTags":["ef58d04cbd19b3c181891528c5159152"],"ImageBlurHashes":{"Backdrop":{"ef58d04cbd19b3c181891528c5159152":"WTCEay}ssUNHsm-Av~#mxFbaR*RkaxoJoLbHS3R+$*xZayWBj[of"},"Primary":{"fe8a07fabcab825558d709454b668538":"dNHJEp-U=G=d[W$zIonOWXWEI;WB$*R-bIbH0#NaJ9Na"}},"LocationType":"FileSystem","MediaType":"Video"}} 2023-07-25T05:55:04.327Z [error][Jellyfin Sync]: Failed to process Jellyfin item, id: 6626b113b693d544ad6b4bed25c97e5e {"errorMessage":"[TMDB] Failed to find media using external IMDb ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"明日之战","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"6626b113b693d544ad6b4bed25c97e5e","HasSubtitles":true,"Container":"mkv,webm","PremiereDate":"2021-09-03T00:00:00.0000000Z","CriticRating":52,"OfficialRating":"PG-13","ChannelId":null,"CommunityRating":7.549,"RunTimeTicks":82862505984,"ProductionYear":2021,"IsFolder":false,"Type":"Movie","UserData":{"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"588228"},"ChildCount":0,"VideoType":"VideoFile","ImageTags":{"Primary":"3a89050abce5f3f9ae2b5948ebbddc4a","Logo":"877f0a9840736c00c28761d16b6bda5f","Thumb":"7cbc4f93a3cb31917f01430c27f86857"},"BackdropImageTags":["3dfddff0a4bcbb6ef3a341eb76a4f653"],"ImageBlurHashes":{"Backdrop":{"3dfddff0a4bcbb6ef3a341eb76a4f653":"WcHT,KsCR*M{I;xtyDI=aes.R*xa~Bt6R+soR+aexas:fjbGShWB"},"Primary":{"3a89050abce5f3f9ae2b5948ebbddc4a":"dYL3M,$iOE=|KOOYENof}@xtEMxZ-VV@j[ay56W=a#Rj"},"Logo":{"877f0a9840736c00c28761d16b6bda5f":"ObD0Gpay00j[xufQt7WBRjogxuRjIUt79Fay%Mj[t7WBRj"},"Thumb":{"7cbc4f93a3cb31917f01430c27f86857":"NXINH#%3bFIUE2%1yWE*aKn~Nb$*}@NGWVsoShs:"}},"LocationType":"FileSystem","MediaType":"Video"}}

Did you check if you can reach the proxy within the container? By doing docker exec -it jellyseerr sh?

Did you check if you can reach the proxy within the container? By doing docker exec -it jellyseerr sh?

Yes, the proxy function well by doing curl test.

I'm also facing this same problem.

i have the same issu

Could all of you try network_mode: host and remove the port bindings?

tried but didn't work. same problem as Yukk1No mentioned

tried but didn't work. same problem as Yukk1No mentioned

Well I'm out of ideas. I use v2ray/xray daily although I now do dokodemodoor on a pi acting as the gateway and everyrhing works seamlessly.
However, I set up xray/v2ray with socks5 and then used a socks5->http converter to recreate this issue, and passing the proxy through docker environment, jellyseerr worked flawlessly.
The one other idea I have is, try running jellyseerr natively instead of docker. And have http proxy passed on the entire system env.

All the trick is  no quotation
aka rather than
    environment:
        - no_proxy="localhost,<IP_ADDRESS>"

you should do
    environment:
        - no_proxy=localhost,<IP_ADDRESS>

and all is fine.

jellyseerr：
图像：fallbagel/jellyseerr：最新
容器名称：jellyseerr
主机名：jellyseer
网络模式：桥接

当我设置代理服务器时，无法打开网页，提示内部服务器错误
当我取消代理时，一切恢复正常
请注意，你的yaml中的HTTP_PROXY和HTTPS_PROXY后面不要有引号。
然而，根据配置后

@Fallenbagel的格式，我在所有页面上都遇到了 500 内部服务器错误。

您可以执行到容器中并对您的代理或其他东西进行卷曲吗？查看容器是否可以到达您的代理。您可以尝试的另一件事是将其置于主机模式并添加 http_proxies。我的猜测是容器无法到达本地代理，因此抛出 500 错误

首先感谢您的回复！我已经使用您提到的方法测试了与代理服务器的连接，并且似乎工作正常。使用的IP地址是我的代理服务器的IP地址，我可以毫无问题地访问Google等网站（我在中国大陆）。但是，我在容器后端不断遇到类似的错误。你能看一下它们吗？

2023-07-25T05:53:59.971Z [error][Jellyfin Sync]: Sync interrupted {"errorMessage":"Sync was aborted."} 2023-07-25T05:54:00.007Z [debug][Jobs]: Starting scheduled job: Download Sync  2023-07-25T05:54:07.893Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:07.981Z [debug][API]: Something went wrong retrieving trending items {"errorMessage":"[TMDB] Failed to fetch all trending: Request failed with status code 400"} 2023-07-25T05:54:08.078Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch movie genres: Request failed with status code 400"} 2023-07-25T05:54:08.735Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-07-25T05:54:08.892Z [debug][API]: Something went wrong retrieving movie {"errorMessage":"[TMDB] Failed to fetch movie details: Request failed with status code 400","movieId":"889575"} 2023-07-25T05:54:08.895Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch TV genres: Request failed with status code 400"} 2023-07-25T05:54:08.901Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:08.979Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:08.981Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:13.437Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:14.028Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch movie genres: Request failed with status code 400"} 2023-07-25T05:54:14.037Z [debug][API]: Something went wrong retrieving trending items {"errorMessage":"[TMDB] Failed to fetch all trending: Request failed with status code 400"} 2023-07-25T05:54:15.402Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:15.505Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:15.507Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch TV genres: Request failed with status code 400"} 2023-07-25T05:54:20.034Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:24.739Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:25.273Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:25.275Z [debug][API]: Something went wrong retrieving trending items {"errorMessage":"[TMDB] Failed to fetch all trending: Request failed with status code 400"} 2023-07-25T05:54:25.287Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch movie genres: Request failed with status code 400"} 2023-07-25T05:54:25.371Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:25.373Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch TV genres: Request failed with status code 400"} 2023-07-25T05:54:25.933Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-07-25T05:54:26.776Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:27.198Z [debug][API]: Something went wrong retrieving movie {"errorMessage":"[TMDB] Failed to fetch movie details: Request failed with status code 400","movieId":"889575"} 2023-07-25T05:54:29.611Z [debug][API]: Something went wrong retrieving movies by studio {"errorMessage":"[TMDB] Failed to fetch movie studio: Request failed with status code 400","studioId":"127928"} 2023-07-25T05:54:31.316Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:32.976Z [debug][API]: Something went wrong retrieving trending items {"errorMessage":"[TMDB] Failed to fetch all trending: Request failed with status code 400"} 2023-07-25T05:54:32.980Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:32.982Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:32.984Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch movie genres: Request failed with status code 400"} 2023-07-25T05:54:32.991Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-07-25T05:54:33.002Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch TV genres: Request failed with status code 400"} 2023-07-25T05:54:34.175Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-07-25T05:54:34.316Z [debug][API]: Something went wrong retrieving movie {"errorMessage":"[TMDB] Failed to fetch movie details: Request failed with status code 400","movieId":"889575"} 2023-07-25T05:54:35.535Z [debug][API]: Something went wrong retrieving movies by studio {"errorMessage":"[TMDB] Failed to fetch movie studio: Request failed with status code 400","studioId":"34"} 2023-07-25T05:54:39.604Z [debug][API]: Something went wrong retrieving movies by studio {"errorMessage":"[TMDB] Failed to fetch movie studio: Request failed with status code 400","studioId":"34"} 2023-07-25T05:54:40.305Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-07-25T05:54:46.129Z [debug][API]: Something went wrong retrieving movies by studio {"errorMessage":"[TMDB] Failed to fetch movie studio: Request failed with status code 400","studioId":"34"} 2023-07-25T05:55:00.013Z [debug][Jobs]: Starting scheduled job: Download Sync  2023-07-25T05:55:00.015Z [info][Jobs]: Starting scheduled job: Jellyfin Recently Added Sync  2023-07-25T05:55:00.016Z [info][Jellyfin Sync]: Jellyfin Sync Starting {"sessionId":"c75ca00e-3fc2-4db8-9f9e-184ce15eff68"} 2023-07-25T05:55:00.018Z [info][Jellyfin Sync]: Beginning to process recently added for library: 动画  2023-07-25T05:55:00.144Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: 9148aad7b8c38298dfe5afdb6f9cc6c2 {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"久保同学不放过我","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"9148aad7b8c38298dfe5afdb6f9cc6c2","PremiereDate":"2023-01-10T00:00:00.0000000Z","OfficialRating":"TV-14","ChannelId":null,"CommunityRating":6.4,"RunTimeTicks":14400000000,"ProductionYear":2023,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":12,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"420084"},"ChildCount":2,"Status":"Ended","AirTime":"2023-01-10","AirDays":["Tuesday"],"DisplayOrder":"aired","ImageTags":{"Primary":"09aa263a29311a45dd22f94254305ed2","Banner":"dd4589e1e2728452ffdf8a27c4f3cdae","Logo":"cf0f24a5856f3152c913153705357f44","Thumb":"15c6e586c16ceadeecdf5a7992f8611a"},"BackdropImageTags":["14403ceccf6cc57f073757589b07f321"],"ImageBlurHashes":{"Backdrop":{"14403ceccf6cc57f073757589b07f321":"WYE|YpIdF|_4p0JBXRxwk8NLogS0S~RPs:bcofs:b_NGozxuogt7"},"Primary":{"09aa263a29311a45dd22f94254305ed2":"dTOD5@57$*EL?^s;RPr?-:o|IUWCX8ozxua}ogX9kVxZ"},"Banner":{"dd4589e1e2728452ffdf8a27c4f3cdae":"H~QJAt.8aKoN-;tQjaxuoz~qxbaKaft7kCkCt7bb"},"Logo":{"cf0f24a5856f3152c913153705357f44":"OIRfd|RQ-p-Vi^-:Na~CrERjJ7N@XSRjx]oLRjj[bHRje:"},"Thumb":{"15c6e586c16ceadeecdf5a7992f8611a":"NeQ0Er9FD%yDtS?I_4o#kXt7njjF?bbIRmn,WBbc"}},"LocationType":"FileSystem","EndDate":"2023-06-20T00:00:00.0000000Z"}} 2023-07-25T05:55:00.148Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: 922e69cd40cc47372b992e84787b535f {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"Fate/stay night [Unlimited Blade Works]","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"922e69cd40cc47372b992e84787b535f","PremiereDate":"2014-10-04T00:00:00.0000000Z","OfficialRating":"TV-14","ChannelId":null,"CommunityRating":7.5,"RunTimeTicks":14400000000,"ProductionYear":2014,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":27,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"278626"},"ChildCount":27,"Status":"Ended","AirTime":"2014-10-04","AirDays":["Saturday"],"DisplayOrder":"aired","ImageTags":{"Primary":"4233a15db2384125d1471557b9909018","Banner":"7c7a78f90072ae461412902000c0d47e","Logo":"54a5e3d6582f71b92c7514769b7439da"},"BackdropImageTags":["cc179b3a7e2e192c899d7a0ff33dcb02"],"ImageBlurHashes":{"Backdrop":{"cc179b3a7e2e192c899d7a0ff33dcb02":"WOHvx6r@Ip$*5rxZ9IxZ5lNbxtNH9_NHtQJ8-7xZ~9t6NHj[M#xF"},"Primary":{"4233a15db2384125d1471557b9909018":"daK[oD-oafwK?Z%1NHI;}=xaRQaKx[s+RQj[o|S5jGW;"},"Banner":{"7c7a78f90072ae461412902000c0d47e":"HJEcwf}Y-Aw^OBobbrXRS}xGoLNHoL$%R+afj[WV"},"Logo":{"54a5e3d6582f71b92c7514769b7439da":"OC7A#ooK9ZX8RjWBozWqa|ofoLWBayWB0eWq-pnit7ofWB"}},"LocationType":"FileSystem","EndDate":"2015-06-28T00:00:00.0000000Z"}} 2023-07-25T05:55:00.149Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: 21d7e53792d75e2d5cef0098bd882e2d {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"【我推的孩子】","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"21d7e53792d75e2d5cef0098bd882e2d","PremiereDate":"2023-04-12T00:00:00.0000000Z","OfficialRating":"TV-14","ChannelId":null,"CommunityRating":7.6,"RunTimeTicks":14400000000,"ProductionYear":2023,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":11,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"421069"},"ChildCount":3,"Status":"Continuing","AirTime":"2023-04-12","AirDays":["Wednesday"],"DisplayOrder":"aired","ImageTags":{"Primary":"9cfddd71ca16c6326f33d28ae8a2d4e2","Banner":"f9f1050355b87ed35c33e96a043a9d32","Logo":"cbcd51b286faee521e7ee3fa6f168332","Thumb":"6ce8506c8966f48a0e3838a4b6e0e772"},"BackdropImageTags":["ec2a3cb06f17461ae19f4b3a610319e7"],"ImageBlurHashes":{"Backdrop":{"ec2a3cb06f17461ae19f4b3a610319e7":"WfM?D7?^kq~VyW%3ogxv%g-oS4M}TJs;n5o|RjM{?HxukVxaW;of"},"Primary":{"9cfddd71ca16c6326f33d28ae8a2d4e2":"dXJ~{3|y:u=}}K#m#s$j9Rn5%KnP#bwbt3V{^Rnhf,wP"},"Banner":{"f9f1050355b87ed35c33e96a043a9d32":"H,CQQWo}NHt8tRxwxcSNac-@t8W?t7oyxut7bbax"},"Logo":{"cbcd51b286faee521e7ee3fa6f168332":"ORC?Q6%M.8R6sCN@t7j[ayofjujtayj[0KM{R6o|buxGe:"},"Thumb":{"6ce8506c8966f48a0e3838a4b6e0e772":"NoFh}CxbIloyMxVs?dozNEoeenWAcDf+R*oIoMWY"}},"LocationType":"FileSystem","EndDate":"2020-03-27T00:00:00.0000000Z"}} 2023-07-25T05:55:00.155Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: 010665d585f9f9e83ad5bfc2d6aecba6 {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"偶像大师 灰姑娘女孩 U149","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"010665d585f9f9e83ad5bfc2d6aecba6","PremiereDate":"2023-04-05T00:00:00.0000000Z","OfficialRating":"10","ChannelId":null,"CommunityRating":7.9,"RunTimeTicks":14400000000,"ProductionYear":2023,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":12,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"424278"},"ChildCount":7,"Status":"Ended","AirTime":"2023-04-05","AirDays":["Wednesday"],"DisplayOrder":"aired","ImageTags":{"Primary":"d80e5cac0592545543c4a521794b2ac8","Logo":"bfe110db1f15852ccaf470023e3bb714","Thumb":"f8481c645d5136272bc1e6b15afec910"},"BackdropImageTags":["34564053659546580626e709204a4006"],"ImageBlurHashes":{"Backdrop":{"34564053659546580626e709204a4006":"WPNmAx.R_N^+xu?vx@-;%3W.Sia{s$-pNFi^I[ae~U-.R*t5IWNb"},"Primary":{"d80e5cac0592545543c4a521794b2ac8":"dcI5[BpfIok=CQpIs*X6x-xsn#em%3RqM|nOtlkDnjWC"},"Logo":{"bfe110db1f15852ccaf470023e3bb714":"OaL|.kt7}?oeiwozM{GakBo|j]-oV@so9]VtjEbFW;ozt7"},"Thumb":{"f8481c645d5136272bc1e6b15afec910":"NPHC.vGwo[tRIntTL3-CMOVZVttQIZw}r]WCxnxV"}},"LocationType":"FileSystem","EndDate":"2023-06-29T00:00:00.0000000Z"}} 2023-07-25T05:55:00.162Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: bfed7e898464fae6a06b3a0da48f8567 {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"白圣女与黑牧师","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"bfed7e898464fae6a06b3a0da48f8567","PremiereDate":"2023-07-12T00:00:00.0000000Z","OfficialRating":"TV-14","ChannelId":null,"CommunityRating":7,"RunTimeTicks":14400000000,"ProductionYear":2023,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":2,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"421283"},"ChildCount":2,"Status":"Continuing","AirTime":"2023-07-12","AirDays":["Wednesday"],"DisplayOrder":"aired","ImageTags":{"Primary":"fa62d3f0ca672f73bf80c32d86137135","Logo":"b99378dc2c78b772e9291361bacc389a"},"BackdropImageTags":["dd6c14e1867023aa5cd34fe2f59dd5e7"],"ImageBlurHashes":{"Backdrop":{"dd6c14e1867023aa5cd34fe2f59dd5e7":"WuP?HkS*%K~V%ft6^*o~XAo0WBj]$xo#W;RjV[oz?GbdkXs,oKj]"},"Primary":{"fa62d3f0ca672f73bf80c32d86137135":"dYLzy^.8M_%1~XbvaKspyEW=RQS2FNoes,kDNHi_n$g3"},"Logo":{"b99378dc2c78b772e9291361bacc389a":"HHQP4+#n.=i{LIxZv4#AP8_kS}rsofKhbH#mSzO="}},"LocationType":"FileSystem"}} 2023-07-25T05:55:00.166Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: 32ed4e0b0477690c8470707fbe08ee6a {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"和山田谈场Lv999的恋爱","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"32ed4e0b0477690c8470707fbe08ee6a","PremiereDate":"2023-04-01T00:00:00.0000000Z","OfficialRating":"TV-14","ChannelId":null,"CommunityRating":6.6,"RunTimeTicks":14400000000,"ProductionYear":2023,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":13,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"423413"},"ChildCount":3,"Status":"Ended","AirTime":"2023-04-01","AirDays":["Saturday"],"DisplayOrder":"aired","ImageTags":{"Primary":"853a8fdb8e4039623abb2ec79a65729d","Banner":"c1955b56cbb40ed83f5fa76494902675","Logo":"7f5cdec98262ae21d1102acde4f01724","Thumb":"20da3d9d7ada1a76d48826087d8f7871"},"BackdropImageTags":["9f3df409aa41b8a9a86dfab1e9ff6fef"],"ImageBlurHashes":{"Backdrop":{"9f3df409aa41b8a9a86dfab1e9ff6fef":"WhM%yGMy$y?GM{t7~prsN2r@xGX9XSM{nObct6ni%MWBnhs;WYay"},"Primary":{"853a8fdb8e4039623abb2ec79a65729d":"dZMZ]*RQ,-^j?^t7EOSL^*xZN1aMXoRlr;R.ozo|SwS5"},"Banner":{"c1955b56cbb40ed83f5fa76494902675":"H*OM+_sqbboNxZ%1Nbo#aK~qtQWFWBt6t7bvWWWA"},"Logo":{"7f5cdec98262ae21d1102acde4f01724":"OjFrksay0Jj[RjkCxuWBfkWBjut7WBf7NZWVnif6t7s:of"},"Thumb":{"20da3d9d7ada1a76d48826087d8f7871":"NdLX9[IC-P?ZRixs_MrrN1xaxFR-TJIVr=g3s:V?"}},"LocationType":"FileSystem","EndDate":"2023-06-25T00:00:00.0000000Z"}} 2023-07-25T05:55:04.176Z [info][Jellyfin Sync]: Beginning to process recently added for library: 电影  2023-07-25T05:55:04.311Z [error][Jellyfin Sync]: Failed to process Jellyfin item, id: ec08556cba757fcac1c8aae4a319ca6c {"errorMessage":"[TMDB] Failed to find media using external IMDb ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"碟中谍4：幽灵协议","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"ec08556cba757fcac1c8aae4a319ca6c","HasSubtitles":true,"Container":"mkv,webm","PremiereDate":"2011-12-07T00:00:00.0000000Z","OfficialRating":"PG-13","ChannelId":null,"CommunityRating":7.1,"RunTimeTicks":79771197440,"ProductionYear":2011,"IsFolder":false,"Type":"Movie","UserData":{"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"56292"},"ChildCount":0,"VideoType":"VideoFile","ImageTags":{"Primary":"929c581c66fe6f8699ab3145db49e751","Logo":"b32b9bc24d9bd00bf4d310bdbd4214e1","Thumb":"2dde7973553a591aa028f65537a9dd2c"},"BackdropImageTags":["9d03e287fb200d0c363054b5d00a4781"],"ImageBlurHashes":{"Backdrop":{"9d03e287fb200d0c363054b5d00a4781":"W#IWx;%1-T%1bHso~TtPs.xZkBoL-oofNHoej[jt-nR+RkayWVjZ"},"Primary":{"929c581c66fe6f8699ab3145db49e751":"dKECOUJ.E1~WyE%1IoofD%WY%19GE2%1xZM{?bR-R*t7"},"Logo":{"b32b9bc24d9bd00bf4d310bdbd4214e1":"O$N,GJMxtRt7WBt7kC~CiwX8ozV@kCj[8_R5ozfke.kCkC"},"Thumb":{"2dde7973553a591aa028f65537a9dd2c":"NdKAD*?G=s-.-pxt^aR%xtxYM{Rk~VX9Ipt6RlWC"}},"LocationType":"FileSystem","MediaType":"Video"}} 2023-07-25T05:55:04.322Z [error][Jellyfin Sync]: Failed to process Jellyfin item, id: 44fa137f65390aad226ac5b9f1559b65 {"errorMessage":"[TMDB] Failed to find media using external IMDb ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"命运之夜：无限剑制","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"44fa137f65390aad226ac5b9f1559b65","HasSubtitles":true,"Container":"mkv,webm","PremiereDate":"2010-01-23T00:00:00.0000000Z","ChannelId":null,"CommunityRating":7.121,"RunTimeTicks":63413350400,"ProductionYear":2010,"IsFolder":false,"Type":"Movie","UserData":{"PlayedPercentage":21.627196660468517,"PlaybackPositionTicks":13714530000,"PlayCount":2,"IsFavorite":false,"LastPlayedDate":"2023-07-18T10:10:03.0218628Z","Played":false,"Key":"46304"},"ChildCount":0,"VideoType":"VideoFile","ImageTags":{"Primary":"fe8a07fabcab825558d709454b668538"},"BackdropImageTags":["ef58d04cbd19b3c181891528c5159152"],"ImageBlurHashes":{"Backdrop":{"ef58d04cbd19b3c181891528c5159152":"WTCEay}ssUNHsm-Av~#mxFbaR*RkaxoJoLbHS3R+$*xZayWBj[of"},"Primary":{"fe8a07fabcab825558d709454b668538":"dNHJEp-U=G=d[W$zIonOWXWEI;WB$*R-bIbH0#NaJ9Na"}},"LocationType":"FileSystem","MediaType":"Video"}} 2023-07-25T05:55:04.327Z [error][Jellyfin Sync]: Failed to process Jellyfin item, id: 6626b113b693d544ad6b4bed25c97e5e {"errorMessage":"[TMDB] Failed to find media using external IMDb ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"明日之战","ServerId":"647a10d423244eed8ae61afe7eeb7318","Id":"6626b113b693d544ad6b4bed25c97e5e","HasSubtitles":true,"Container":"mkv,webm","PremiereDate":"2021-09-03T00:00:00.0000000Z","CriticRating":52,"OfficialRating":"PG-13","ChannelId":null,"CommunityRating":7.549,"RunTimeTicks":82862505984,"ProductionYear":2021,"IsFolder":false,"Type":"Movie","UserData":{"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"588228"},"ChildCount":0,"VideoType":"VideoFile","ImageTags":{"Primary":"3a89050abce5f3f9ae2b5948ebbddc4a","Logo":"877f0a9840736c00c28761d16b6bda5f","Thumb":"7cbc4f93a3cb31917f01430c27f86857"},"BackdropImageTags":["3dfddff0a4bcbb6ef3a341eb76a4f653"],"ImageBlurHashes":{"Backdrop":{"3dfddff0a4bcbb6ef3a341eb76a4f653":"WcHT,KsCR*M{I;xtyDI=aes.R*xa~Bt6R+soR+aexas:fjbGShWB"},"Primary":{"3a89050abce5f3f9ae2b5948ebbddc4a":"dYL3M,$iOE=|KOOYENof}@xtEMxZ-VV@j[ay56W=a#Rj"},"Logo":{"877f0a9840736c00c28761d16b6bda5f":"ObD0Gpay00j[xufQt7WBRjogxuRjIUt79Fay%Mj[t7WBRj"},"Thumb":{"7cbc4f93a3cb31917f01430c27f86857":"NXINH#%3bFIUE2%1yWE*aKn~Nb$*}@NGWVsoShs:"}},"LocationType":"FileSystem","MediaType":"Video"}}

I have also encountered the same problem. How did you solve it?

@Geeksun2018 don't use quotes " when you define the proxy hosts

@Geeksun2018"定义代理主机时不使用引号
This is my docker-compose.yml. I have no issues with proxy in the container and can successfully access any website through the proxy, but my jellyseerr always displays 500- Internal Server Error. Here is my log.
2023-11-12T12:59:22.287Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: 7765b81103ff9e76d454090c87f26154 {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"咒术回战","ServerId":"34665d5296714a63a6bc626d87e1b33a","Id":"7765b81103ff9e76d454090c87f26154","PremiereDate":"2020-10-03T00:00:00.0000000Z","OfficialRating":"TV-MA","ChannelId":null,"CommunityRating":8.566,"RunTimeTicks":14400000000,"ProductionYear":2020,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":15,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"377543"},"Status":"Continuing","AirDays":[],"ImageTags":{"Primary":"369d87eae92ca1dd8d17415509f4d7a0","Logo":"344bbb4af9f6967b9235fb2f679b6fc2"},"BackdropImageTags":["c9fe852bde7d22661dcb924cdeb92797"],"ImageBlurHashes":{"Backdrop":{"c9fe852bde7d22661dcb924cdeb92797":"WOG[H8#X#re[Vs$*~DwNwM?Hs:E1$,sDRR-WRQRQ^+Myogs;IUWA"},"Primary":{"369d87eae92ca1dd8d17415509f4d7a0":"dNGu^H%L~n_3A5?I$^t6%PWtRhRi9HXAtQkCt8t7ogM{"},"Logo":{"344bbb4af9f6967b9235fb2f679b6fc2":"O3C6oDE3%Koe?Yj[^$~m--%1oe%KayWC4q-.%Kxst6RkRk"}},"LocationType":"FileSystem"}} 2023-11-12T12:59:26.288Z [info][Jellyfin Sync]: Full Scan Complete 2023-11-12T12:59:28.554Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-11-12T12:59:42.646Z [debug][API]: Something went wrong retrieving backdrops {"errorMessage":"[TMDB] Failed to fetch all trending: Request failed with status code 400"} 2023-11-12T12:59:44.966Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-11-12T13:00:00.015Z [debug][Jobs]: Starting scheduled job: Download Sync 2023-11-12T13:00:00.025Z [info][Jobs]: Starting scheduled job: Jellyfin Recently Added Sync 2023-11-12T13:00:00.025Z [info][Jellyfin Sync]: Jellyfin Sync Starting {"sessionId":"26b48c18-9e30-42b8-8a89-9d33bf0de178"} 2023-11-12T13:00:00.072Z [info][Jellyfin Sync]: Beginning to process recently added for library: 节目 2023-11-12T13:00:00.086Z [debug][Jellyfin Sync]: failed show: [BDMV][CODE GEASS] 2023-11-12T13:00:04.087Z [info][Jellyfin Sync]: Recently Added Scan Complete 2023-11-12T13:00:09.738Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-11-12T13:00:14.932Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-11-12T13:00:26.139Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-11-12T13:00:50.068Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-11-12T13:00:50.127Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-11-12T13:00:50.129Z [debug][API]: Something went wrong retrieving trending items {"errorMessage":"[TMDB] Failed to fetch all trending: Request failed with status code 400"} 2023-11-12T13:00:50.406Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-11-12T13:00:50.409Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-11-12T13:00:50.470Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch movie genres: Request failed with status code 400"} 2023-11-12T13:00:50.776Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch TV genres: Request failed with status code 400"} 2023-11-12T13:00:51.939Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-11-12T13:00:53.015Z [debug][API]: Something went wrong retrieving languages {"errorMessage":"[TMDB] Failed to fetch langauges: Request failed with status code 400"}

@Geeksun2018"定义代理主机时不使用引号
Thank you very much for your reply.
This is my Docker Compose. yml file. I have no issues with proxy in the container and can successfully access any website through the proxy.

But my jellyseerr always displays 500- Internal Server Error. Here is my log
2023-11-12T12:59:22.287Z [error][Jellyfin Sync]: Failed to process Jellyfin item. Id: 7765b81103ff9e76d454090c87f26154 {"errorMessage":"[TMDB] Failed to get TV show using the external TVDB ID: [TMDB] Failed to find by external ID: Request failed with status code 400","jellyfinitem":{"Name":"咒术回战","ServerId":"34665d5296714a63a6bc626d87e1b33a","Id":"7765b81103ff9e76d454090c87f26154","PremiereDate":"2020-10-03T00:00:00.0000000Z","OfficialRating":"TV-MA","ChannelId":null,"CommunityRating":8.566,"RunTimeTicks":14400000000,"ProductionYear":2020,"IsFolder":true,"Type":"Series","UserData":{"UnplayedItemCount":15,"PlaybackPositionTicks":0,"PlayCount":0,"IsFavorite":false,"Played":false,"Key":"377543"},"Status":"Continuing","AirDays":[],"ImageTags":{"Primary":"369d87eae92ca1dd8d17415509f4d7a0","Logo":"344bbb4af9f6967b9235fb2f679b6fc2"},"BackdropImageTags":["c9fe852bde7d22661dcb924cdeb92797"],"ImageBlurHashes":{"Backdrop":{"c9fe852bde7d22661dcb924cdeb92797":"WOG[H8#X#re[Vs$*~DwNwM?Hs:E1$,sDRR-WRQRQ^+Myogs;IUWA"},"Primary":{"369d87eae92ca1dd8d17415509f4d7a0":"dNGu^H%L~n_3A5?I$^t6%PWtRhRi9HXAtQkCt8t7ogM{"},"Logo":{"344bbb4af9f6967b9235fb2f679b6fc2":"O3C6oDE3%Koe?Yj[^$~m--%1oe%KayWC4q-.%Kxst6RkRk"}},"LocationType":"FileSystem"}} 2023-11-12T12:59:26.288Z [info][Jellyfin Sync]: Full Scan Complete 2023-11-12T12:59:28.554Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-11-12T12:59:42.646Z [debug][API]: Something went wrong retrieving backdrops {"errorMessage":"[TMDB] Failed to fetch all trending: Request failed with status code 400"} 2023-11-12T12:59:44.966Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-11-12T13:00:00.015Z [debug][Jobs]: Starting scheduled job: Download Sync 2023-11-12T13:00:00.025Z [info][Jobs]: Starting scheduled job: Jellyfin Recently Added Sync 2023-11-12T13:00:00.025Z [info][Jellyfin Sync]: Jellyfin Sync Starting {"sessionId":"26b48c18-9e30-42b8-8a89-9d33bf0de178"} 2023-11-12T13:00:00.072Z [info][Jellyfin Sync]: Beginning to process recently added for library: 节目 2023-11-12T13:00:00.086Z [debug][Jellyfin Sync]: failed show: [BDMV][CODE GEASS] 2023-11-12T13:00:04.087Z [info][Jellyfin Sync]: Recently Added Scan Complete 2023-11-12T13:00:09.738Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-11-12T13:00:14.932Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-11-12T13:00:26.139Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-11-12T13:00:50.068Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"Request failed with status code 503"} 2023-11-12T13:00:50.127Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-11-12T13:00:50.129Z [debug][API]: Something went wrong retrieving trending items {"errorMessage":"[TMDB] Failed to fetch all trending: Request failed with status code 400"} 2023-11-12T13:00:50.406Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: Request failed with status code 400"} 2023-11-12T13:00:50.409Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"} 2023-11-12T13:00:50.470Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch movie genres: Request failed with status code 400"} 2023-11-12T13:00:50.776Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch TV genres: Request failed with status code 400"} 2023-11-12T13:00:51.939Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: Request failed with status code 400"}

@Geeksun2018 you have to use HTTP_PROXY etc.
All capitalised

@Geeksun2018 you have to use HTTP_PROXY etc. All capitalised

I reset the proxy in uppercase, and the page still displays a status code of 500. I just tried to shut down all agents, and the request response will be very slow, but in the end, the 500 status code will still be displayed. I really don't know where the reason is.

@Geeksun2018 you have to use HTTP_PROXY etc. All capitalised

I reset the proxy in uppercase, and the page still displays a status code of 500. I just tried to shut down all agents, and the request response will be very slow, but in the end, the 500 status code will still be displayed. I really don't know where the reason is.

Can you send me full docker-compose again

@Geeksun2018你必须使用HTTP_PROXYetc。全部大写

我把代理重置为大写，页面仍然显示500状态码。我刚刚尝试关闭所有代理，请求响应会很慢，但最终还是会显示500状态码。我实在不知道原因在哪里。

你能再次向我发送完整的 docker-compose 吗？
容器可能无法到达代理主机。有时会发生这种情况，因为奇怪的基于 ubuntu/debian 的发行版有奇怪的防火墙问题。是否有可能跳到不和谐的地方并帮助你解决它？

This is my latest docker-compose. yml file. In a few days, I will try setting up a proxy directly on the router, which may be effective.

@Geeksun2018 it might be the container can't reach. For better easier troubleshooting hop on discord and ill help you. That's where we do the support.
Router thing might work better yeah because that's what I do too.

@Geeksun2018 it might be the container can't reach. For better easier troubleshooting hop on discord and ill help you. That's where we do the support.
Router thing might work better yeah because that's what I do too.

Thank you very much. I will try to seek help on Discord.

jellyseerr:
image: fallenbagel/jellyseerr:latest
container_name: jellyseerr
hostname: jellyseer
network_mode: bridge

When I set the proxy server, I can't open the web,Prompt internal server error
When I cancel the agent, everything returns to normal

Please note that there should be no quotation marks after HTTP_PROXY and HTTPS_PROXY in your yaml.
However, after configuring according to @Fallenbagel's format, I encountered a 500 Internal Server Error on all of my pages.
I have solved this problem. The problem lies in my agent. I used to use V2ray, but now I have changed it to clash and it's no problem.

:tada: This issue has been resolved in version 2.1.0 :tada:
The release is available on:

v2.1.0
GitHub release

Your semantic-release bot :package::rocket:


Overwriting Pipeline timeout does not work

Expected Behavior
A PipelineRun, created by a Pipeline should not timeout after 1 hour, but rather after 2h30m.
I used the following configuration:
apiVersion: tekton.dev/v1beta1
kind: Pipeline
metadata:
  name: pipeline-name
spec:
  tasks:
    - name: task-name
      taskRef:
        kind: Task
        name: task-name
      timeout: "2h30m0s"

Actual Behavior
A PipelineRun, created by a Pipeline runs out after 1 hour:
PipelineRun "pipeline-name-id" failed to finish within "1h0m0s"
The PipelineRun yaml configuration contains the following:
spec:
  pipelineRef:
    name: pipeline-name
  taskRunTemplate:
    serviceAccountName: pipeline
  timeouts:
    pipeline: 1h0m0s

The pipeline timeout is not overwritten and the pipeline fails.
Steps to Reproduce the Problem

Create a Pipeline with a task that takes over an hour to complete.
Set the timeout of the task to more than 1 hour (as shown in the "Expected Behavior" section).
Run the Pipeline. Check the created PipelineRun config for the timeout limits

Additional Info
I am running a pipeline with 2 tasks, one of which takes longer than an hour. I have specified the timeout limit for this task. However, when a PipelineRun is created by the Pipeline, the default value of 1 hour is not overwritten. I have followed the documentation on how to set a timeout for a pipeline, which seems to have to be done on the task-level.
In the PipelineRun yaml, created by the Pipeline, both:
tasks:
      - name: task-name
        taskRef:
          kind: Task
          name: task-name
        timeout: 2h30m0s

and
spec:
  pipelineRef:
    name: pipeline-name
  taskRunTemplate:
    serviceAccountName: pipeline
  timeouts:
    pipeline: 1h0m0s

are present. Because the pipeline timeout is shorter than the task timeout, the pipeline will fail after an hour.
I have also tried to set the default timeout value to 2 hours via a ConfigMap. This did not work either:
apiVersion: v1
kind: ConfigMap
metadata:
  name: config-defaults
  namespace: tekton-pipelines
data:
  default-timeout-minutes: "150"

This still resulted in a 1 hour timeout limit.
PipelineRun
Using the following configuration for a PipelineRun does work. In this case the default value of 1 hour is overwritten by 2h40m. However, I would like to not have to create my PipelineRuns manually.
apiVersion: triggers.tekton.dev/v1alpha1
kind: TriggerTemplate
metadata:
  name: trigger
spec:
  resourcetemplates:
    - apiVersion: tekton.dev/v1beta1
      kind: PipelineRun
      metadata:
        generateName: triggered
      spec:
        pipelineRef:
          name: pipeline-name
        timeout: "2h40m0s"

Kubernetes version: v1.27.10+28ed2d7 (OpenShift 4.4)
Output of kubectl version:

Client Version: v1.27.4
Kustomize Version: v5.0.1
Server Version: v1.27.10+28ed2d7

Tekton Pipeline version: tekton.dev/v1beta1

Using the following configuration for a PipelineRun does work. In this case the default value of 1 hour is overwritten by 2h40m. However, I would like to not have to create my PipelineRuns manually.

How is the PipelineRun created in your setup ? Asking this because, it is most likely, on the "thing" that creates the PipelineRun to set the timeouts correctly.

Tekton Pipeline version: tekton.dev/v1beta1

v1beta1 is the API version, we also need the pipeline instance version (tkn version should display this)

The PipelineRun where the timeout value is correct is created with a Cronjob and EventListener. A PipelineRun created by a Pipeline does not seem to set the timeout value correctly.
I hope that answers your question regarding how the PipelineRun is created.
tkn version:
Client version: 0.33.0
Chains version: v0.19.0
Pipeline version: v0.53.3
Triggers version: v0.25.3
Operator version: v0.69.1


How to Install and execute the module

Sorry for being so slow, but I have downloaded the files and unzipped them.
But I dont understand how to "Install and execute the module in a device that is domain joined to on-premises AD DS with AD DS credentials that have permissions to create a service logon account or a computer account in the target AD."
How to install and execute them? What commands to use? They just open in Notepad for me.
Regards nanordas

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7a1a9f3d-5733-012a-a0d7-c00ec21b9232
Version Independent ID: 1e70ab95-9488-5aa3-b8ef-e58b3e0067bb
Content: Enable AD DS authentication to Azure file shares
Content Source: articles/storage/files/storage-files-identity-ad-ds-enable.md
Service: storage
Sub-service: files
GitHub Login: @khdownie
Microsoft Alias: kendownie

@nanordas Providing these 3rd party docs that talks about installing and executing the same-
https://blog.simontimms.com/2022/02/16/install-azfileshybrid-powershell/
https://www.ciraltos.com/azure-files-smb-access-with-windows-ad/
Please let us know if this helps. Thank you!

Thank you so much! It helped a lot!
But I ran into an error when running the Join-AzStorageAccountForAuth ` command:
New-ADUser : The password does not meet the length, complexity, or history requirement of the domain.
At C:\Users\admin\Documents\WindowsPowerShell\Modules\AzFilesHybrid\<IP_ADDRESS>\AzFilesHybrid.psm1:2539 char:21

                New-ADUser `

                ~~~~~~~~~~~~

CategoryInfo          : InvalidData: (CN=fellesazure,CN=Users,DC=PB,DC=local:String) [New-ADUser], ADPasswordCom
plexityException
FullyQualifiedErrorId : ActiveDirectoryServer:1325,Microsoft.ActiveDirectory.Management.Commands.NewADUser

How to fix this?
Med vennlig hilsen
[SIRIUSD15aR03aP01ZL]
Narve Andreas Nordås
Tlf. +47 479 25 199
www.siriusdata.nohttp://www.siriusdata.no/
Fra: SaiKishor-MSFT @.>
Sendt: fredag 8. april 2022 00.22
Til: MicrosoftDocs/azure-docs @.>
Kopi: Narve Andreas Nordås @.>; Mention @.>
Emne: Re: [MicrosoftDocs/azure-docs] How to Install and execute the module (Issue #91168)
@nanordashttps://github.com/nanordas Providing these 3rd party docs that talks about installing and executing the same-
https://blog.simontimms.com/2022/02/16/install-azfileshybrid-powershell/
https://www.ciraltos.com/azure-files-smb-access-with-windows-ad/
Please let us know if this helps. Thank you!
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/91168#issuecomment-1092264785, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYTI634PQGT5GTNTZZJBYJ3VD5NYFANCNFSM5SZERHTQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

The user is created in AD, but is disabled and not possible to enable it

@nanordas Can you try to create a stronger password or disable the security policy? See this document for more details- https://windowsreport.com/unable-to-update-the-password-the-value-provided-windows-10/#:~:text=Open Group Policy Editor.,and OK to save changes.

@nanordas Any update?

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Missing img file for 1.6.0 release

.img file for 1.6.0 release is missing on the release page: https://github.com/hypriot/image-builder-rpi/releases/tag/1.6.0

Thanks for the heads-up. My fault, Travis didn't trigger the release because I forgot to prepend "v" to the version number.
A new release "v1.6.0" just started a build on Travis https://travis-ci.org/hypriot/image-builder-rpi/builds/280751889
Take about 20-30 minutes...


Default native-image config files is not enough for some project.

Starting from version 1.25.0, Armeria has begun to support GraalVM, but there are still some default configurations that are not adequately addressed.

I am trying to compile SkyWalking (which uses Armeria) into a native image and have encountered some issues (the above picture is not all of problems I have found). After running with the native tracing agent, I obtained the following configuration, which successfully compiled and resolved the aforementioned issues.
native-image.json
These configurations may not be the simplest, but they do solve the problem. Could you consider incorporating them into the main repository?

Hi! Sorry about the late comment.
I think it's probably fine to add this to the base configuration, but let me also talk to the other devs tomorrow morning cc. @trustin

Thanks a lot for reporting this issue, @yswdqz! At the moment, our native-image configuration is not updated automatically because the configuration generated by the tracing agent is not clean enough, although we hope to automate it in the future. I'll take a look and merge your configuration in the next release. :bow:

Let me just release a new version with the re-run of the config for now. We can follow up if there are other configs we missed.

Thank you ! I'm sorry that I don't have time to test it recently. I will test it later.

No problem. Please feel free to reopen this issue or open a new one if you find the new version still has a problem. :bow:


Overflow warnings are impossible to disable

Problem
There are often times where we intentionally have overflow by design (example below).
Although this will look fine in production, this spamming of the console, and on-screen clutter negatively impacts developer productivity.
This is disruptive to development because it prevents you from clearly seeing the UI you are working on. You can switch to profile mode, but then you lose the ability for hot reload. Further, Android Simulator does not support profile mode.
It also confuses team members who report errors / log bugs, when they spot overflow in the console, when it was intentional by another developer. Causing a lot of wasted time and repetitive discussions.
Essentially feels like we are fighting the framework here, and it won't co-operate with what we want to do.
Possible Solution
It would be nice if the developer had the option to tell a parent not throw overflow errors at specific points in the tree.
The idea is not to disable Overflow warnings globally, but to tell specific sub-trees to not display an error.
OR
The framework could properly detect when ClipRect is applied, and then not throw the warning. Currently while it  does tell you do add a ClipRect, this seems to have no effect on whether the warning is thrown or not.
Example 1
Here we have a panel that, when child is changed, it will size itself to match that child. This requires that, when changing children, some of the content is temporarily clipped. By design.
https://user-images.githubusercontent.com/736973/160184624-4c1c176d-9460-4452-8ae4-8c5f1c4fbd14.mp4
Example on dartpad here: https://dartpad.dev/?id=8879b345a2f5eef780fa4840c3a4be30
Gist: https://gist.github.com/esDotDev/8879b345a2f5eef780fa4840c3a4be30
Resulting in this error:

The suggested fixes of adding a ClipRect or a ListView are not desired. A ClipRect is already in place in the parent, and a ListView is not desired as it adds a ton of complications and potential bugs, to an otherwise simple implementation.
Example 2
In another situation, we have a visual decorator that is already clipped (otherwise the effect wouldn't work), and we want to spin the circle around, to reveal another title, while the previous title is clipped out of view.

Again the framework decides it knows best, and aggressively tells us we're doing something wrong, when this really a nice elegant approach, and overdraw is minimal (and clipped regardless, as you can see)
You can also see how this blocks me from seeing the top or bottom of the widget, actively slowing down my development, and preventing me from seeing potential errors.
Example 3
Here we use an animated container to hide or reveal a child widget. Normally the child would scale-down here, but our design would prefer that the widget keep its natural size, and instead be cropped out of view.

This can be done simply and robustly with something like:
AnimatedContainer(
  width: _isOpen: 60 : 0,
  child: ClipRect(
      child: UnconstrainedBox(
         child: FlutterLogo(50);
      )))

But again, the overflow error blocks us from really seeing the finer pts of the animation, unless we run in profile mode. Also weird how we are usng a ClipRect, but the framework complains we should be using a ClipRect.

Hi @esDotDev, thanks for filing the issue, I believe you are trying to hide the errors shown from the Flutter framework, I believe onError can help you to handle the custom error.
Please take a look at the below code sample which just prints to the console when the overflow error occurs.

code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
  FlutterError.onError = (FlutterErrorDetails details) {
    print('flutter error hidden from console');
    // FlutterError.dumpErrorToConsole(details, forceReport: false);
  };
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: PageOne(),
    );
  }
}

class PageOne extends StatelessWidget {
  const PageOne({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Column(
        children: [
          for (int i = 0; i < 100; i++) Text('$i'),
        ],
      ),
      floatingActionButton: FloatingActionButton(
        child: const Icon(Icons.add),
        onPressed: () {},
      ),
    );
  }
}

class PageTwo extends StatelessWidget {
  const PageTwo({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Builder(builder: (context) {
        return Center(
          child: ElevatedButton(
            child: const Text('Show SnackBar'),
            onPressed: () {
              ScaffoldMessenger.of(context).showSnackBar(
                const SnackBar(
                  content: Text('SnackBar!'),
                  behavior: SnackBarBehavior.floating,
                ),
              );
            },
          ),
        );
      }),
    );
  }
}

It's actually quite disruptive to development. I either have these giant yellow bars that stop me from accurately dialing in my UI, or I am forced to run it in profile mode, which disables hot-reload, also preventing me from efficiently working on the UI.

Thanks for the info, Labelling this issue for further insights from the team.

Thanks for the info, Labelling this issue for further insights from the team.

Thx! I have updated the original post to include a running example on dartpad:
https://dartpad.dev/?id=8879b345a2f5eef780fa4840c3a4be30

Hello @esDotDev. Thumbs up for this issue.  I have a use case too. I want to use UnconstrainedBox without overflow warnings (not in the console nor on screen).
In the source code it says:
  /// Creates a widget that imposes no constraints on its child, allowing it to
  /// render at its "natural" size. If the child overflows the parents
  /// constraints, a warning will be given in debug mode.

I intentionally use it so that a child widget can be rendered at its natural size.
That child widget has a parent and the width of the parent can be changed. In this case, I want to decrease the parent size and it should act like a masking widget that masks the natural-sized child widget.

As you can see, the overflow warning is shown no matter I do: a warning will be given in debug mode

@esDotDev Oh if it is solved then it is ok to close the issue. I can open another but would you mind showing a snippet of how OverflowBox solved the Example 3?
I had quite a lot of experiments with OverflowBox but couldn't make it work.
Thanks for your help :)

For any child that will overflow, you should be able to do this?
OverflowBox(
  maxWidth: double.infinity,
  maxHeight: double.infinity,
  child: someHugeChild,
)

Oh, that didn't work. Because the OverflowBox needs constraints from the parent whereas UnconstrainedBox does not. Setting maxWidth: double.infinity for OverflowBox is not the solution for my case because I needed the child to build itself as it is, with its naturally free sizing.
However, I copied and modified the UnconstrainedBox into some new widget that has the showDebugModeOverflowWarning constructor. I might release it as a package while also adding example use-cases.
Because the UnconstrainedBox was already working in my case as expected. The only thing missing was it showed an overflow warning even though the overflow was intentional.
You can close this issue safely. Thank you for your time. :)

Hm, did you try OverflowBox + InstrinsicHeight & InstrinsicWidth?

Unconstrained box should not show the warning if it has clip behavior set. Instead of ClipRect -> UnconstrainedBox why not set clip behavior directly on the UnconstrainedBox?
Other than that, I agree that Flutter should have an easier way to disable overflow warnings in certain cases. I usually just end up writing a simple render object in that case, but it would be nice not having to do that.


Support frameworks

Support various frameworks with exact matches and add new partial regex matches
E.g.
*jquery*.js
*angular*.js
*dojo*.js
*mootools*.js
*prototype*.js
codeigniter* (dir)
yii* (dir), yiic, yiic.bat

The pattern matching should be easy for v0.5.0 as long as I can fix some glyph scaling issues, preview:

Identifying libraries based on folder structure will be a bit more work and maybe should go after v0.5.0

For anyone feeling brave you can give 0.5.0 a try :smirk: :

support for flagship
support for perl
added support for more languages
support for unite and vimfiler
API fix
misc code formatting fixes
misc readme and doc updates

(I still need to do more testing before a release AND maybe try to get ctrlp support and nerdtree added files no icon but those might be pushed off to say 0.6.0 or something)


ssh/scp/sftp: enable pipelining of write operations

Turn on pipelining of write operations for ssh/scp/sftp
Motivation
It significantly speeds up writes. From paramiko docs:

When pipelining is on, paramiko won’t wait for the server response after each write operation. Instead, they’re collected as they come in. At the first non-write operation (including close), all remaining server responses are collected. This means that if there was an error with one of your later writes, an exception might be thrown from within close instead of write.

Popular sftp client library pysftp enables pipelining for put operations.
Result of simple benchmark
pipelining disabled:

Total time: 33.55 seconds, sent: 2621440 bytes, speed: 76 kbytes/sec

pipelining enabled:

Total time: 3.58 seconds, sent: 2621440 bytes, speed: 714 kbytes/sec

@mpenkov could you take a look?

Thank you for your contribution. Sorry it has taken so long for me to review this.
Please have a look at the comments and get back to me.

@mrk-its Ping. Are you able to finish this PR?

Closing as stale


Adding service, env, version tags to email

Ticket #3310
Description
Adding service, env, version tags to emails being sent through AWS. Updated unit tests as well. The tags should show up in Datadog for analysis.
Checklist

[ ] Provided ticket and description
[ ] Provided screenshots/demo
[ ] Provided testing information
[ ] Provided adequate test coverage for all new code
[ ] Added PR reviewers

Not sure if there's a way to test if the tags will appear correctly in Datadog before adding the changes?

Thanks for the step-by-step guide!


Travis issue

PR Details
Fix Travis issue
Description
We need to force Travis to run build to be able to found the issue
Related Issue
#85

Merged without approvals due is a infrastructure change

Merged without approvals because is an infrastructure issue


Universal viewer not loading

Summary
The UV forever spins without actually loading. SSL is configured to true. FlipFlop is set to UV. Additionally, the UV tries to load even if you select PDF.js flipflop.
https://demo.hyku-demo.notch8.cloud/concern/images/a4b6eb39-3530-4a76-a35a-2e7415d2b91e

Acceptance Criteria

[ ] If UV flip flop is on, the UV should be displayed

Screenshots or Video
Testing Instructions
Notes

UV is not loading because even though we have thumbnails, we are missing the original files for some reason.

🎉
QA Result: Pass ✅
https://demo.hyku-staging.notch8.cloud/concern/images/f0903764-f799-45ef-94b1-b849e460009b?locale=en


[Feature]: Keyboard entry on MacOS

Describe the problem
Bitkit runs nicely on MacOS, but I wish I could use my physical keyboard to type instead of the onscreen keyboard.
Describe the solution
No response
Additional context
Low-priority, just a little side wish!

@BitcoinErrorLog Keyboard entry works for me, I don't get the onscreen keyboard. One thing to try is to hit CMD + Shift + K that's how you switch from onscreen to physical in the simulator.

What about PIN entry?

What about PIN entry?

It's really only incidental that the app mostly works on MacOS. In the case of the NumberPad (PIN and Amount screens) it is a custom UI and not a <TextInput /> component that only listens to click events. For this issue specifically we can try something like react-native-external-keyboard but if the plan is to support desktop we should think about targeting that more cleanly and keep mobile and desktop code separate since the APIs will vary widly.


[WIP] Script for LLM benchmark - Humaneval

This pr contains a wip script for evaluating llm benchamrk.

demo link https://www.loom.com/share/cdc5d026374c43efaed54fc6630f5c5b?sid=7f4d8e8e-123e-4ec3-bb0c-7202a9daf700

Here is a video explaining the changes done as a part of "automates workbench and project creation" commit


⚠ TorrentLeech has degraded performance

In 346d00f, TorrentLeech ($TL) experienced degraded performance:

HTTP code: 200
Response time: 5034 ms

Resolved: TorrentLeech performance has improved in ca44c8a after 6 minutes.


Waiting for PortScan Module

Hi Sir,
I love you tool, but i had problem when Starting Masscan
[+] Starting Masscan 65535 ports
[*] Execute: /home/wayc0de/tools/Osmedeus/lib/alias/portscan -i /home/wayc0de/.osmedeus/workspaces/target.com/probing/ip-target.com.txt -o '/home/wayc0de/.osmedeus/workspaces/target.com/portscan/target.com' -s '/home/wayc0de/.osmedeus/workspaces/target.com/portscan/summary.txt' -p '/home/wayc0de/tools/Osmedeus/plugins'
[sudo] password for wayc0de: [*] Waiting for PortScan module
[*] Waiting for PortScan module
[*] Waiting for PortScan module
[*] Waiting for PortScan module
[*] Waiting for PortScan module

How long i must wait for that? because more than 1 hours still waiting
Thank you

It's obviously masscan need root permissions so you have to provide your password if you're running as a non-root user. It's waiting too long because you don't provide that so it's never actually run :).
I normally run Osmedeus as a root user or you can whitelist some command need to run as root like masscan and nmap.


Improve DrawSphereWires

Improve DrawSphereWires by using vertex arrays, resulting in a 2x FPS increase in the validation app.

#5 maar dan met de juiste base branch


ignore suggest-override warning in gcc

In https://github.com/vesoft-inc/nebula-storage/pull/232 use gmock, however, for now our gtest version is outdated, so we could only use the old style macro, which can not mark override.
We can ignore it by adding #pragma GCC diagnostic ignored "-Wsuggest-override", but we failed to compile in clang for now, this would raise clang unknown-warning-option warning.
If we try to #pragma clang diagnostic ignored "-Wunknown-warning-option", gcc can't ignore it anymore.
For similarity, just ignore suggest-override in gcc, and we could add it back when third-party update.

Better add a TODO comment here. Since we really benefit from this option.

👌


refactor(http): merge Request and Response from server and client

I started exploring Hyper's code and saw issue #1155, so I started tinkering with the Request and Response classes. For the most part, the merge was straight-forward, but ran into a small snag: server::Request has a Body, but client::Request has an Option<Body>. I merged them by making the final Request use Option<Body> and added the Default trait to Body. Unfortunately, this makes the formerly-concise req.body(), as seen in test/server.rs#117, a lengthy req.take_body().unwrap_or_default().
I also re-exported Request and Response to minimize breaking changes, but this has the side-effect of being visible from 3 locations: hyper, hyper::server, and hyper::client).
Thoughts?

[x] The commit messages match the guidelines in https://github.com/hyperium/hyper/blob/master/CONTRIBUTING.md#git-commit-guidelines

Thanks for contributing! Unfortunately, I'm here to tell you there were the following style issues with your Pull Request:

Commit: ff4369835b002764d62525ad46bec3702ce6bf25
Your commit message body contains a line that is longer than 100 characters

Guidelines are available at https://github.com/hyperium/hyper/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

Oh my, this is super exciting! I was slowly working on this, since I wanted to improve a reverse proxy example for the docs, but I also didn't want to slow down releasing 0.11, so I kept pausing. In my branch, I had united the inner parts into a Message with a generic Head, but the exposed result would be the same thing, and it doesn't really matter.
I'll do a proper review in a moment.

Superb work, thank you!


DecisionTreeRegressor added to pymilo param

Reference Issues/PRs
https://github.com/openscilab/pymilo/issues/18
What does this implement/fix? Explain your changes.
Add full support for Decision Tree Regressor
Any other comments?

@AHReccese Thanks for your efforts 💯

Would you please update the CHANGELOG.md?
I am not sure about the docstring style, particularly when it comes to multi-line mode.
@alirezazolanvari would you please check it out?

Changelog updated.
Could you please explain it a little bit more? what do you mean by docstring style? nothing is changed from the previous versions, I follow the same structure, if there is anything I can do let me know.

@AHReccese Thanks for your efforts 💯

Would you please update the CHANGELOG.md?
I am not sure about the docstring style, particularly when it comes to multi-line mode.
@alirezazolanvari would you please check it out?

Changelog updated.
Could you please explain it a little bit more? what do you mean by docstring style? nothing is changed from the previous versions, I follow the same structure, if there is anything I can do let me know.

I left some minor comments. Please check them out and resolve them if they look fine with you.

@AHReccese Thanks for your efforts 💯

Would you please update the CHANGELOG.md?
I am not sure about the docstring style, particularly when it comes to multi-line mode.
@alirezazolanvari would you please check it out?

Changelog updated.
Could you please explain it a little bit more? what do you mean by docstring style? nothing is changed from the previous versions, I follow the same structure, if there is anything I can do let me know.

I left some minor comments. Please check them out and resolve them if they look fine with you.

I applied all the feasible ones.


add GetLightdInfo RPC

Returns chain info such as version, chain (main or test), height, Vendor, t-addr support flag, Sapling activation height, branchID. I'm not sure if our wallet engineers will find this useful, but there's no harm in merging it (it's a small amount of code), and ZECWallet definitely needs it. See #137.

If vendor and version are not necessary as a return from this RPC, they should be removed


TarArchive decompress fails when tar has broken relative symlinks

When using the TarArchive decompress function, if the input Tar file has broken symlinks inside, the decompression fails with error
failed to evaluate symlink
However sometimes these broken symlinks don't really have negative impacts.
One example of such tar archives are the releases of code-server https://github.com/coder/code-server/releases
Manually untarring these files work, but they are not possible to be untarred with packit.
Expected Behavior
It is possible to use the TarArchive packit functionality to untar files containing broken symlinks
Current Behavior
Untarring files with broken symlinks always result in error
Possible Solution
It would be good enough to have an option/flag to specify in order to ignore broken symlinks instead of just throwing an error.
Steps to Reproduce

download one of the code-server releases linked above
try to deliver/decompress it with packit

Hey @davellas - this sounds like a reasonable request. We'll take a look and see what the best course of action is.
I see three options:

make packit always ignore broken symlinks
allow optional configuration to ignore broken symlinks (your suggestion)
decide that the current behavior is desirable and do nothing (unlikely, but just including it here for completeness)

We'll do some exploring and get back to you.
Out of curiosity, are you actually using packit to download the https://github.com/coder/code-server/releases tarball as part of a buildpack? Or is that just a convenient example to reproduce the failure?

 Do you have a link to it? It's always interesting to see what kinds of buildpacks the community is creating and what problems they solve!

I downloaded a tarball release of code server e.g. this one, extracted it with tar -xf and then checked for broken symlinks with:
→ find ./code-server-4.9.1-linux-amd64 -type l -exec test ! -e {} \; -print
./code-server-4.9.1-linux-amd64/lib/vscode/extensions/node_modules/.bin/tsc
./code-server-4.9.1-linux-amd64/lib/vscode/extensions/node_modules/.bin/tsserver

(from this Stack Overflow post)
Which I then validated were broken by looking for the typescript/bin directory with:
→ ls -alh ./code-server-4.9.1-linux-amd64/lib/vscode/extensions/node_modules/typescript/
total 16K
drwxr-xr-x  3 ubuntu ubuntu 4.0K Dec 16 16:48 .
drwxr-xr-x  5 ubuntu ubuntu 4.0K Dec 16 16:48 ..
drwxr-xr-x 15 ubuntu ubuntu 4.0K Dec 16 16:48 lib
-rw-r--r--  1 ubuntu ubuntu 4.0K Dec 16 16:48 package.json

And we see that the symlinks are invalid because there is no typscript/bin directory.
I haven't tried to reproduce this with Packit yet, but assuming that this causes Packit to break, I think that the best course of action is to warn on broken symlinks (maybe via the debug logger) but not fail. I don't think we need to introduce configuration for this, given that tar silently ignores the broken symlinks. This is essentially the first option I laid out above, but with some logging to aid debugging of dependencies.


Failed to fetch private key

@mariotaku
HI:
My desktop OS is Win 11 ,LG TV is qned86sqa, WebOS & Developer Mode is updated to date.
Just use developer account to log in Developer Mode,
Dev Mode Status and Key server both turned on.
Dev manager 1.11.16 installed.
When I add device on Dev Manager, All 4 steps are checked.
address & passphrase all entered which shows on tv.
After "please wait" its shows "failed to fetch private key". "Please make sure key server in developer mode app is turned on during device setup" <--But I actually turned on the key server.
Tried several times and can't figure it out.
Need your help,Please!

Hi, how do you connect the PC and the TV to the network? Can you do a ping to the TV?

I think you got the point!
I try two different ways to connect the PC and the TV with wire.
the first way :
living room network socket--wire--asus zenwifi xd5 router--wire--TV
study room network socket--wire--PC
In this way cause Failed to fetch private key.
then second way:
living room network socket--wire--TV
study room network socket--wire--PC
In this way I successfully add device on Dev Manager!
but I need the router to launch wifi.
So I think now the question is :How can I use the first connect way to use Dev Manager?
Thank you!

@JRC326 The most important part is to put your TV under the same network. There are multiple ways to do that, for the exact router model, the easiest way is to switch it to "Access Point" mode. Please follow the instructions in your router's booklet.

@mariotaku
HI TAKU:
I changed my router setting to "ap mode" with asus app,
but it didn't work (my wifi signal is gone and the router starting shines a breathing green light).
So I reset it and put the router in the study room.
here is my setting now:
living room network socket--wire--TV
study room network socket--wire--asus zenwifi xd5 router--wire--PC
then I try again add device on DEV Manager,and it works fine.
I installed moonlight on my TV successfully.
But when I launch moonlight on TV,
I can't find or add my PC(by type in PC IPV4 address)
I know the situation is all about put PC & TV under the same network.
Is there any better suggestion for me?
THANK YOU!~

If you don't put 2 devices under the same network, one can't access another by default.
PC under second router
graph TD;
    A[Main Router]---B[Living Room Network Socket];
    A---C[Study Room Network Socket];
    B---E[TV];
    C---D[Second Router];
    subgraph Secondary Network;
    D---F[Computer];
    D---G[Other Devices];
    end;

TV under second router
graph TD;
    A[Main Router]---C[Study Room Network Socket];
    A---B[Living Room Network Socket];
    B---D[Second Router];
    subgraph Secondary Network;
    D---E[TV];
    D---G[Other Devices];
    end;
    C---F[Computer];

Please read the booklet thoroughly when you set it up, it should work if you're following the instructions properly.

Closing as this specific problem is solved. If you finish setup and face other issues when you use moonlight, feel free to open an issue there!

@mariotaku Thank you for explaining so much!!
I'll keep trying to make it works.