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

Health tab does not always show detailed error message #12408

Closed
johnstcn opened this issue Mar 4, 2024 · 5 comments · Fixed by #12430
Closed

Health tab does not always show detailed error message #12408

johnstcn opened this issue Mar 4, 2024 · 5 comments · Fixed by #12430
Assignees
Labels
feature Something we don't have yet site Area: frontend dashboard

Comments

@johnstcn
Copy link
Member

johnstcn commented Mar 4, 2024

The "Access URL" and "Websocket" pages under "Health" do not show detailed error messages or further troubleshooting information.

For example:

Given: Coder instance with misconfigured scheme in CODER_ACCESS_URL (e.g. https://localhost:7080 which is generally HTTP and not HTTPS)

When: you hit the health tab

Then: you see the following information:

Severity: error
Access URL: https://localhost:7080
Reachable: No
Status Code: 0

image

But the /api/v2/debug/health endpoint provides more detailed information, e.g.:

"access_url": {
"healthy": false,
"severity": "error",
"warnings": [],
"dismissed": false,
"access_url": "https://localhost:7080/",
"reachable": false,
"status_code": 0,
"healthz_response": "",
"error": "EACS03: get healthz endpoint: Get \"https://localhost:7080/healthz\": http: server gave HTTP response to HTTPS client"
},

Ditto for websocket check.

@coder-labeler coder-labeler bot added bug Used to filter all bug issues site Area: frontend dashboard labels Mar 4, 2024
@johnstcn
Copy link
Member Author

johnstcn commented Mar 4, 2024

@coder-labeler good bot

@matifali matifali added the s2 Broken use cases or features (with a workaround). Only humans may set this. label Mar 4, 2024
@matifali
Copy link
Collaborator

matifali commented Mar 4, 2024

s2 as we have a workaround to get this info by hitting the debug endpoint manually.

@BrunoQuaresma
Copy link
Collaborator

@matifali I disagree this is a bug because it was the expected behavior when we planned this feature.

@BrunoQuaresma
Copy link
Collaborator

Just checking, for both we should display what is in the error attribute right?

@BrunoQuaresma BrunoQuaresma self-assigned this Mar 4, 2024
@BrunoQuaresma BrunoQuaresma added feature Something we don't have yet and removed s2 Broken use cases or features (with a workaround). Only humans may set this. bug Used to filter all bug issues labels Mar 5, 2024
@BrunoQuaresma
Copy link
Collaborator

@johnstcn would be nice if it could also return the error code EACS03

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Something we don't have yet site Area: frontend dashboard
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants