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

Jellyseerr widget #39

Closed
ilusi0n opened this issue Aug 28, 2022 · 3 comments
Closed

Jellyseerr widget #39

ilusi0n opened this issue Aug 28, 2022 · 3 comments

Comments

@ilusi0n
Copy link
Contributor

ilusi0n commented Aug 28, 2022

Hello @benphelps !
I implemented the jellyseerr widget in #34 but I guess I messed up something. The widgets works indeed when using the pnpm. But when using the dockerized app it doesn't work since the request is returning a 500 internal server error.
I already tried to google it but no avail. Do you have any tips or ideas what could be the cause and how to solve it?

Thanks!

@Trever123
Copy link

When using docker are you using it in bridge mode or host mode? I ask because the IP you are using may be wrong for jellyseerr depending on your docker setup. (If bridge mode, you’ll need jellyseerr to also be in docker and to use the internal docker ip/container name, not the actual IP of the host)

@ilusi0n
Copy link
Contributor Author

ilusi0n commented Aug 28, 2022

I'm using on a bridge mode. I created my network and all my containers are on that network. The other widgets work just fine. I have all my containers behind a reverse proxy and they don't need the docker ip/container name to access them.
With jellyseerr doesnt work. But, if I use the internal docker ip/container name as you suggested it works quite fine. Must be something related with the proxy api I think.
Gonna close this since it's not a big deal at least for me!

@ilusi0n ilusi0n closed this as completed Aug 28, 2022
Copy link
Contributor

github-actions bot commented Feb 6, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants