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

Application Exception #878

Open
1 task done
MegaShinySnivy opened this issue Jul 16, 2024 · 11 comments
Open
1 task done

Application Exception #878

MegaShinySnivy opened this issue Jul 16, 2024 · 11 comments

Comments

@MegaShinySnivy
Copy link

Description

On attempting to load Jellyseerr, I get an exception that prevents the webapp from loading.

TypeError: r.warnings is undefined
    NextJS 10
framework-6a24ea55bfe2d3c0.js:1:71888
    NextJS 11
TypeError: r.warnings is undefined
    NextJS 10
main-a0d77ee65511e9c3.js:1:7915
A client-side exception has occurred, see here for more info: https://nextjs.org/docs/messages/client-side-exception-occurred main-a0d77ee65511e9c3.js:1:7932
TypeError: r.warnings is undefined
    NextJS 10
framework-6a24ea55bfe2d3c0.js:1:71888
TypeError: r.warnings is undefined
    NextJS 10
main-a0d77ee65511e9c3.js:1:7915
A client-side exception has occurred, see here for more info: https://nextjs.org/docs/messages/client-side-exception-occurred main-a0d77ee65511e9c3.js:1:7932
    NextJS 13
MouseEvent.mozInputSource is deprecated. Use PointerEvent.pointerType instead. 17100-f53437216927e03c.js:1:21060

Version

1.9.2

Steps to Reproduce

Start v1.9.2
Attempt to access it

Screenshots

No response

Logs

No response

Platform

desktop

Device

Desktop on Firefox

Operating System

Linux

Browser

Firefox

Additional Context

No response

Code of Conduct

  • I agree to follow Jellyseerr's Code of Conduct
@Fallenbagel
Copy link
Owner

Fallenbagel commented Jul 16, 2024

How did you setup jellyseerr?

What node version. What yarn version.
Exact steps you took.

@MegaShinySnivy
Copy link
Author

I'm using the official docker container on Kubernetes. Here's my helmfile.

https://github.com/MegaShinySnivy/Scaling-Snakes/blob/main/kubernetes/apps/default/jellyseerr/app/helmrelease.yaml

@gauthier-th
Copy link
Collaborator

Could this be related to #875?

@MegaShinySnivy
Copy link
Author

Possibly... I notice when bypassing my reverse proxy, NGINX, it doesn't error. Is it possible there could be some sort of interference?

@gauthier-th
Copy link
Collaborator

The author of the PR I mentioned earlier was also using k8s with some kind of reverse proxy, so yes it may be linked.
Could you test the preview-fix-users-warning tag to see if it fixes your issue?

@MegaShinySnivy
Copy link
Author

Doing that gives me... Something else entirely! Skips the login screen (even in a private tab) and leads to an "Oops!" screen with an option to return home that does jack all.

@Fallenbagel
Copy link
Owner

Doing that gives me... Something else entirely! Skips the login screen (even in a private tab) and leads to an "Oops!" screen with an option to return home that does jack all.

You mentioned without reverse proxy it works. Then that sound like a configuration issue with reverse proxy. Are you using subdomain or subfolder?

Can you show me your nginx configuration?

@M0NsTeRRR
Copy link

I use jellyseerr in a kubernetes environment without issues (traefik). Have you tried to disable some nginx settings you have to see which cause this issue ?

@MegaShinySnivy
Copy link
Author

I'm not sure what I would disable, all of these are pretty standard

@MegaShinySnivy
Copy link
Author

It was my custom error pages. What errors does jellyseerr rely on to function?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants