Posit workbench launcher is getting down and not allowing users
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
Description
The main launcher page becames unresponsive and throws 502 error but we can use /health-check and
/admin path. This confirms the problem is not with the service and ingress. Users can't able to log in to
the Workbench launcher but the launcher container is authenticating in the backend
I have added a detailed explanation as pdf with probable causes. Please find the causes found and input the suggestions that can be done.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached 502 Issue 1.pdf and comparing the failing launcher page with the available /health-check and /admin paths. Reproduce the 502 response and trace the launcher authentication path; the issue is done when the cause is confirmed and a documented, tested fix or actionable recommendation is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100