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

admin panel stuck within login screen #7069

Closed
wennemer opened this issue May 16, 2024 · 2 comments
Closed

admin panel stuck within login screen #7069

wennemer opened this issue May 16, 2024 · 2 comments
Labels

Comments

@wennemer
Copy link

Describe the bug

Hi,
We have deployed unleash 5.12.2 with helm chart 4.1.1 within our kubernetes cluster including an ingress service:

  • Our react frontend can connect to the server and is 100% functional.
  • The admin panel can be reached directly by portforwarding from the cluster and is 100% functional

--

  • The admin panel can not be reached by the subdomain https://unleash.domain.com:

  • The login page stuck in loading state showing the spinner.

  • There are no errors within the developer tools using edge or chrome browser

  • Firefox maybe gives us a hint:

Source-Map-Fehler: Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data
Ressourcen-Adresse: 
Source-Map-Adresse: renderer.js.map

Source-Map-Fehler: Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data
Ressourcen-Adresse: 
Source-Map-Adresse: react_devtools_backend_compact.js.map

Source-Map-Fehler: Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data
Ressourcen-Adresse: 
Source-Map-Adresse: backendManager.js.map

Source-Map-Fehler: Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data
Ressourcen-Adresse: 
Source-Map-Adresse: installHook.js.map

N

Steps to reproduce the bug

No response

Expected behavior

Login screen to admin panel shoul apear

Logs, error output, etc.

No response

Screenshots

No response

Additional context

No response

Unleash version

5.12.2

Subscription type

Open source

Hosting type

Self-hosted

SDK information (language and version)

No response

@wennemer wennemer added the bug label May 16, 2024
@rishiraj88
Copy link

The source files may not be accessible.

Are the json files or the json map files to be read available? May we verify their paths (locations) for reading them?

@wennemer
Copy link
Author

We find a solution:
We normally use custom error pages in our nginx service.
I think the admin ui needs the error pages of the unleash server instead of our owns.
After removing these regarding the unleash server, everything is fine.

Thanks!

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

No branches or pull requests

2 participants