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.

Sign up for GitHub

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

Jump to bottom

v0.66.0-oss errors after login #6763

Open
mgilham opened this issue Jan 7, 2025 · 3 comments · May be fixed by #6780 or #6826
Open

v0.66.0-oss errors after login #6763

mgilham opened this issue Jan 7, 2025 · 3 comments · May be fixed by #6780 or #6826

Comments

@mgilham
Copy link

mgilham commented Jan 7, 2025

Bug description

Opaque web page error ("Oops !!! Something went wrong") after logging in with a fresh build of v0.66.0.

Expected behavior

How to reproduce

  1. git checkout v0.66.0
  2. build query-service via make all, overriding REPONAME with my repo
  3. helm install fresh signoz release to clean Kubernetes cluster with chart version 0.64.2, overwriting queryService.image.repository to my repo
  4. after creating an account or logging in, the "Oops !!! Something went wrong" error message is displayed in the web browser
  5. issue also reproduces when using docker.io/signoz/query-service:0.66.0-oss
  6. if I replace my build of the query service with the default image from docker hub (docker.io/signoz/query-service:0.66.0), it works
  7. If I build ee via make build-push-ee-query-service, it also works. This serves as a temporary workaround, since I'm not yet using it in production.

Version information

  • Signoz version: v0.66.0
  • Browser version:
  • Your OS and version:
  • Your CPU Architecture(ARM/Intel): amd64

Additional context

I haven't looked at the front end code, but one difference I noticed in the network calls is that the oss query service returns 404 to /api/v2/licenses shortly before the error message.
@welcome Welcome
Copy link

welcome bot commented Jan 7, 2025

Thanks for opening this issue. A team member should give feedback soon. In the meantime, feel free to check out the contributing guidelines.

@shivanshuraj1333
Copy link
Member

Image

Please go to your browser, and clear browser local storage, it would require you to login again.

@mgilham
Copy link
Author

mgilham commented Jan 8, 2025

Thanks, I tried clearing the local storage each time, but the result is the same: docker.io/signoz/query-service:0.66.0 works, but docker.io/signoz/query-service:0.66.0-oss does not work (also my local oss build does not work). I can see that the login is succeeding and the JWT is being issued, so I'm guessing it's tripping up on some front-end invariant.

@shivanshuraj1333 shivanshuraj1333 linked a pull request Jan 8, 2025 that will close this issue
Open
mgilham added a commit to mgilham/signoz that referenced this issue Jan 16, 2025
@mgilham
fix: don't expect /licenses to work for oss query service (SigNoz#6763)
87dc3e0
@mgilham mgilham linked a pull request Jan 16, 2025 that will close this issue
Open
mgilham added a commit to mgilham/signoz that referenced this issue Jan 17, 2025
@mgilham
fix: don't expect /licenses to work for oss query service (SigNoz#6763)
351958f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@mgilham @shivanshuraj1333