Skip to content

Running wsproxy not showing healthy in dashboard #8532

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
Closed
sharkymark opened this issue Jul 15, 2023 · 3 comments · Fixed by #9683
Closed

Running wsproxy not showing healthy in dashboard #8532

sharkymark opened this issue Jul 15, 2023 · 3 comments · Fixed by #9683
Assignees
@Emyrk
Labels
s2 Broken use cases or features (with a workaround). Only humans may set this.

Comments

@sharkymark
Copy link
Contributor

Version: v0.26.1+a0fedeb

The use case is I have EKS deployment and created a wsproxy in GKE.

I can successfully curl the wsproxy and pull up the dashboard message in a browser that redirects me to the EKS deployment's access url.

However in the wsproxies dashboard, it continued to show:

UNHEALTHY
Not available
Errors
unexpected status code 400

Which was expected when I first installed the wsproxy and had not yet created DNS entries.

I had to scale the EKS deployment from 2 to 0 replicas and scaled up to 2, and then the wsproxy showed healthy.
@cdr-bot cdr-bot bot added the bug label Jul 15, 2023
@bpmct
Copy link
Member

bpmct commented Aug 7, 2023

@Emyrk any ideas why this didn't retry? If this is an expected behavior and requires a restart, that is fair. I'm OK closing this one out.

@bpmct bpmct added the s2 Broken use cases or features (with a workaround). Only humans may set this. label Aug 7, 2023
@Emyrk
Copy link
Member

Emyrk commented Aug 7, 2023

Health checks are done every minute I believe. The unexpected status code though makes me think something else was going on 🤔

@Emyrk Emyrk self-assigned this Sep 11, 2023
@Emyrk
Copy link
Member

Emyrk commented Sep 11, 2023

I will see if I can improve the error message to add any more context.

@Emyrk Emyrk mentioned this issue Sep 14, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Emyrk Emyrk

Labels
s2 Broken use cases or features (with a workaround). Only humans may set this.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: add debug information to wsproxy errors coder/coder
3 participants
@sharkymark @Emyrk @bpmct