[Bug]: Socket connection to 'wss://domain.com/ng-cli-ws' failed: in chrome's developer console when running angular in code-server
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- angular, aws, kubernetes, typescript
- Domain
- cloud, networking, web-dev
Research direction
Start with the code-server proxy guidelines and reproduce the deployment through EKS and Emissary-ingress, then inspect the src/index.html base href and package.json ng serve settings. Use Chrome's developer console to compare the failing WebSocket path with the configured mapping; done means the Angular app loads without the ng-cli-ws connection error.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this?
- I have searched the existing issues
OS/Web Information
- Web Browser: Chrome
- Local OS: Ubuntu
- Remote OS: Ubuntu
- Remote Architecture: amd64
code-server --version: 4.12.0
Steps to Reproduce
- Deploy code-server as pod and create service in EKS cluster
- Use Emissary-ingress as proxy and create mapping to code-server userpod (eg /tempmap/ --> userpod service)
- Access the userpod at the URL www.domain.tld/tempmap/
- Install Nvm , npm and angular
- switch to the created directory and do ng serve and access the browser
- Now we will get white screen error
- Follow the code-server proxy guidelines
- try a) use in src/index.html
b) add --serve-path /absproxy/4200 to ng serve in your package.json - Socket connection to 'wss://domain.tld/ng-cli-ws' failed: not found error in chrome's developer console
Expected
Not getting Socket connection to 'wss://domain.tld/ng-cli-ws' failed: error in chrome developer consoleWebSocket
Actual
Getting webSocket connection to 'wss://domain.tld/ng-cli-ws' failed error
Logs
No response
Screenshot/Video
No response
Does this issue happen in VS Code or GitHub Codespaces?
- I cannot reproduce this in VS Code.
- I cannot reproduce this in GitHub Codespaces.
Are you accessing code-server over HTTPS?
- I am using HTTPS.
Notes
Code-server is deployed on AWS EKS cluster, and I am using emissary-ingress as proxy to access code-server. SSL is attached to AWS application load balancer used to access code-server. We are getting this error not always but getting them randomly.
- Dominant language
- TypeScript
- Stars
- 79.4k
- Forks
- 6.9k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 39
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.
More from coder/code-server
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
coder/code-server#8017 · 2 comments ·
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
coder/code-server#8013 · 4 comments ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
coder/code-server#7976 · 2 comments ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
coder/code-server#7962 · 3 comments ·
-
bug needs-investigation
Difficulty 4/5 3-5 days Newbie friendliness 55/100
coder/code-server#7955 · 1 comment ·
All issues in coder/code-server
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
vercel-labs/just-bash#464 ·
-
looksLikeSlug() is ASCII-only, so non-Latin entity slugs (e.g. Korean) skip exact match and collapse Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
TanStack/tanstack.com#1293 ·