Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

The 2.0.0 version of Jellyseer cannot use http proxy, while version 1.9.2 works fine. #1025

Open
1 task done
nasssssss2363 opened this issue Oct 17, 2024 · 18 comments · May be fixed by #1031
Open
1 task done

The 2.0.0 version of Jellyseer cannot use http proxy, while version 1.9.2 works fine. #1025

nasssssss2363 opened this issue Oct 17, 2024 · 18 comments · May be fixed by #1031
Labels
bug Something isn't working confirmed This bug has been reproduced

Comments

@nasssssss2363
Copy link

nasssssss2363 commented Oct 17, 2024

Description

After today's update, I found that my Jellyseerr, which I have been using for several years, cannot display posters (I cannot access The Movie Database without a proxy in my region). Below are the steps to reproduce the issue and some potentially useful logs.

I tried deleting the Jellyseer image, fetching a new image, and reconfiguring from scratch, but none of that worked. The only solution was to revert the version back to 1.9.2 to use the proxy again.

Version

2.0.0

Steps to Reproduce

If you install version 2.0.0 this way, Jellyseerr cannot use a proxy, but if you change the image version to 1.9.2, it works.

docker run -d \
--name jellyseerr \
--link clash:clash \
-e LOG_LEVEL=debug \
-e TZ=Asia/Shanghai \
-e HTTP_PROXY="http://192.168.31.66:7890" \
-e HTTPS_PROXY="http://192.168.31.66:7890" \
-e no_proxy="localhost,127.0.0.1" \
-p 5059:5055 \
-v /mnt/sda/appdata/jellyseerr:/app/config \
--restart=always \
fallenbagel/jellyseerr:latest

Screenshots

No response

Logs

2024-10-17T10:32:25.565Z [debug][API]: Something went wrong retrieving trending items {"errorMessage":"[TMDB] Failed to fetch all trending: fetch failed"}
2024-10-17T10:32:25.586Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: fetch failed"}
2024-10-17T10:32:25.601Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch movie genres: fetch failed"}
2024-10-17T10:32:25.610Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: fetch failed"}
2024-10-17T10:32:25.617Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch TV genres: fetch failed"}
2024-10-17T10:32:25.973Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: fetch failed"}
2024-10-17T10:32:30.874Z [debug][API]: Something went wrong retrieving popular movies {"errorMessage":"[TMDB] Failed to fetch discover movies: fetch failed"}
2024-10-17T10:32:30.889Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch movie genres: fetch failed"}
2024-10-17T10:32:30.905Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: fetch failed"}
2024-10-17T10:32:30.917Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch TV genres: fetch failed"}

Platform

desktop

Device

pc

Operating System

windows11

Browser

chrome

Additional Context

No response

Code of Conduct

  • I agree to follow Jellyseerr's Code of Conduct
@nasssssss2363 nasssssss2363 added awaiting triage This issue needs to be reviewed bug Something isn't working labels Oct 17, 2024
@Fallenbagel
Copy link
Owner

Can you also try adding the lowe case http proxy, https proxy

@nasssssss2363
Copy link
Author

Can you also try adding the lowe case http proxy, https proxy

I've tried it, and it still doesn't work. I've tested it on several of my Synology devices, and none of them work

@nasssssss2363
Copy link
Author

Can you also try adding the lowe case http proxy, https proxy

New error log found today

2024-10-18T14:33:24.921Z [info][Notifications]: Registered notification agents
2024-10-18T14:33:24.989Z [info][Jobs]: Scheduled jobs loaded
2024-10-18T14:33:25.120Z [info][Server]: Server ready on port 5055
2024-10-18T14:33:33.247Z [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 403"}
2024-10-18T14:33:48.221Z [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 403"}
2024-10-18T14:34:00.008Z [debug][Jobs]: Starting scheduled job: Download Sync
2024-10-18T14:34:00.037Z [debug][Download Tracker]: Matching download data to 2 other Sonarr server(s)
2024-10-18T14:34:03.614Z [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 403"}
2024-10-18T14:34:36.560Z [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 403"}
2024-10-18T14:34:44.028Z [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 403"}
2024-10-18T14:35:00.005Z [debug][Jobs]: Starting scheduled job: Download Sync
2024-10-18T14:35:00.033Z [info][Jobs]: Starting scheduled job: Jellyfin Recently Added Scan
2024-10-18T14:35:00.038Z [debug][Download Tracker]: Matching download data to 2 other Sonarr server(s)

@theggs
Copy link

theggs commented Oct 18, 2024

I have the same issue.
It seems the new version uses a new way to fetch http resource. But it doesn't support proxy defined in environment variables.

@Fallenbagel
Copy link
Owner

It seems the new version uses a new way to fetch http resource. But it doesn't support proxy defined in environment variables.

Correct.

@Fallenbagel Fallenbagel added confirmed This bug has been reproduced and removed awaiting triage This issue needs to be reviewed labels Oct 18, 2024
@nasssssss2363
Copy link
Author

Can you also try adding the lowe case http proxy, https proxy

There's another bug in version 2.0.0, which is that if I change the password of my emby account, I can't log in, even if I log out of jellyseerr early.

In the past, changing the emby didn't affect it as long as I logged out of jellyseerr early.

@Fallenbagel
Copy link
Owner

Fallenbagel commented Oct 18, 2024

Can you also try adding the lowe case http proxy, https proxy

There's another bug in version 2.0.0, which is that if I change the password of my emby account, I can't log in, even if I log out of jellyseerr early.

In the past, changing the emby didn't affect it as long as I logged out of jellyseerr early.

You should update to 2.0.1
And i tested this and is working for me. There authentication is handled by emby, jellyseerr doesn't store any passwords so changing password doesn't matter to jellyseerr at all all it does is pass credentials to emby and emby is like okay!

If still not working for you even after updating to 2.0.1, I suggest to hop onto discord to troubleshoot. Your issue is unrelated to this issue.

@nasssssss2363
Copy link
Author

Can you also try adding the lowe case http proxy, https proxy

There's another bug in version 2.0.0, which is that if I change the password of my emby account, I can't log in, even if I log out of jellyseerr early.
In the past, changing the emby didn't affect it as long as I logged out of jellyseerr early.

You should update to 2.0.1 And i tested this and is working for me. There authentication is handled by emby, jellyseerr doesn't store any passwords so changing password doesn't matter to jellyseerr at all all it does is pass credentials to emby and emby is like okay!

If still not working for you even after updating to 2.0.1, I suggest to hop onto discord to troubleshoot. Your issue is unrelated to this issue.

OK, thanks for the answer, I'll test it again

By the way, what causes the http proxy problem?

@Fallenbagel
Copy link
Owner

It seems the new version uses a new way to fetch http resource. But it doesn't support proxy defined in environment variables.

We migrated from axios to fetch. Fetch doesnt support proxy defined in environment variables

@nasssssss2363
Copy link
Author

It seems the new version uses a new way to fetch http resource. But it doesn't support proxy defined in environment variables.

We migrated from axios to fetch. Fetch doesnt support proxy defined in environment variables

Well, actually I as well as many users don't want to use http proxies, but if we don't, we can't use jellyseerr, so I hope it's fixed!

@Fallenbagel
Copy link
Owner

#491
This will be implemented to fix this

@nasssssss2363
Copy link
Author

nasssssss2363 commented Oct 18, 2024

#491 This will be implemented to fix this

I didn't quite get it. You mean jellyseerr will soon be able to set up proxies within the interface?

@Fallenbagel
Copy link
Owner

#491 This will be implemented to fix this

I didn't quite get it. You mean jellyseerr will soon be able to set up proxies within the interface?

Yes in the gui

@Fallenbagel Fallenbagel linked a pull request Oct 19, 2024 that will close this issue
3 tasks
@nasssssss2363
Copy link
Author

#491 This will be implemented to fix this

I didn't quite get it. You mean jellyseerr will soon be able to set up proxies within the interface?

Yes in the gui

Can I ask for an approximate time?

@gauthier-th
Copy link
Collaborator

Can I ask for an approximate time?

It should be implemented in a few days.

@Fallenbagel
Copy link
Owner

#491 This will be implemented to fix this

I didn't quite get it. You mean jellyseerr will soon be able to set up proxies within the interface?

Yes in the gui

Can I ask for an approximate time?

I'm working on my free time (while doing full time studies and work). So expect it to be a few days (almost done).

@nasssssss2363
Copy link
Author

nasssssss2363 commented Oct 22, 2024

#491 This will be implemented to fix this

I didn't quite get it. You mean jellyseerr will soon be able to set up proxies within the interface?

Yes in the gui

Can I ask for an approximate time?

I'm working on my free time (while doing full time studies and work). So expect it to be a few days (almost done).

Thank you for your reply! I really appreciate you taking the time to address this despite.

@Fallenbagel
Copy link
Owner

Fallenbagel commented Oct 23, 2024

I'm working on my free time (while doing full time studies and work). So expect it to be a few days (almost done).

I misspoke. I'm working on #1027 (basic auth)

@gauthier-th is working on this #1031. And currently there is a preview tag if you want to test if it works:
preview-proxy-setting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working confirmed This bug has been reproduced
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants