-
Notifications
You must be signed in to change notification settings - Fork 23
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
Unexpected Error: "500" #342
Comments
I am getting this error, even after using the installation steps given in https://github.com/sensu/web/blob/master/INSTALL.md |
The |
I have tried two ways to use sensu/web for making the sensu dashboard accessible. The below are the two scenarios I had tried:
In this I don’t get any logs to fetch in journalctl of sense-backend container or on sense-web container I see the error message only on the dashboard which not letting me to log in even before authentication it is giving the error of that I have above. In this the steps for installation of yarn and cloning of sensu/web is being done in docker file of sense-web
In both scenarios the login page appears but once the credentials are entered it will produce the error with 500. I get this error on the interactive mode of yarn |
Also, i opened another session of my sensu-backend container and tried "curl -lv 127.0.0.1:3000", then it gives response 200. as below: / # curl -Lv 127.0.0.1:3000
|
I'm also running into this error message with Sensu Web release versions v1.0.3 and v1.0.4 on a cluster which I recently upgraded from Sensu Go v5.21 to v6.1.3 (self-compiled sensu-backend binary with Go v1.13 per building from source guide). The sensu-backend and web application are running on CentOS 7 hosts The web UI (and logging in with default admin credentials) were working prior to the v6 upgrade and Sensu Web deployment following the install guide. Here's the full error message from the console:
|
My whole setup is built from source (backend also) so it might be different but once I've changed from https://127.0.0.1:8080 (which is what is written in the INSTALL.md) to http://127.0.0.1:8080 the UI was able to reach the /auth route and it was working OK. Here is the command that is now working for me:
|
@tzachs It sounds like you just don't have HTTPS enabled on your backend API service. You should be able to config your backend.yml config file with |
Thanks @thisgarryhas2rs for the tip :) |
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
Context
Browser Stack Trace:
at
undefined
(/static/js/app_4296.js:2)at
f
(/static/js/vendorsapp_b5c8.js:2)app_b5c8.js:2)at
T._settlePromiseFromHandler
(/static/js/vendorsat
T._settlePromise
(/static/js/vendorsapp_b5c8.js:2)app_b5c8.js:2)at
T._settlePromise0
(/static/js/vendorsat
T._settlePromises
(/static/js/vendorsapp_b5c8.js:2)app_b5c8.js:2)at
p
(/static/js/vendorsat
d
(/static/js/vendorsapp_b5c8.js:2)app_b5c8.js:2)at
u._drainQueues
(/static/js/vendorsat
drainQueues
(/static/js/vendorsapp_b5c8.js:2)app_b5c8.js:2)at
MutationObserver.<anonymous>
(/static/js/vendorsYour Environment
sensu/web revision:
c0890b2
The text was updated successfully, but these errors were encountered: