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

Text Diff module not working when using reverse proxy (with authentik) #1291

Open
gitmotion opened this issue Sep 11, 2024 · 2 comments
Open
Assignees
Labels
bug Something isn't working triage

Comments

@gitmotion
Copy link

gitmotion commented Sep 11, 2024

Describe the bug

Text Diff module does not load anymore. Noticed it works if I access from the internal ip but not from the reverse proxy. I've also tried adding it directly to npm with a custom location mapped to the assests folder and container but still gives me the same error.

image

What happened?

It should load as it does on the internal ip

System information

  • Docker
  • Nginx Proxy Manager
  • Authentik

Where did you encounter the bug?

Self hosted

@gitmotion gitmotion added bug Something isn't working triage labels Sep 11, 2024
@Fintanw23
Copy link

Wow exactly my issue and setup! Very annoying as text-diff is 90% of what i use this container for :(

@gitmotion
Copy link
Author

gitmotion commented Sep 23, 2024

ah so i'm starting to believe this is a CORS issue, since having an authentication provider like authentik redirects from the authentik URL. got this error this when trying to access my local version vs external version (instead of internal ip)
image

  • this still doesn't explain why the other modules work just fine though so i'm sure there's a fix in there that could be made.
  • it seems like an issue with how authentik handles the routing possibly

@Fintanw23
i'm not sure exactly how but somehow i fixed this lol with the following:

  • something i tried was logging out of authentik and then logging back and in hard refreshing ittools. it seems like there's a lot of caching going on. seems like once you get the file to load it stores it locally and allows it to work fine?
  • sorry i can't seem to pinpoint how i fixed it lol but i did something like this to get it to load, hope that helps

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

No branches or pull requests

3 participants