coder / coder/code-server

[Bug]: Socket connection to 'wss://domain.com/ng-cli-ws' failed: in chrome's developer console when running angular in code-server

Aberta
#6,205 7 comentários 0 reações 0 responsáveis Ver no GitHub
bug
Linguagem predominante
TypeScript
Estrelas
79.3k
Forks
6.8k
Merge médio
2d 6h
PRs com merge (30d)
41

Descrição

### Is there an existing issue for this?

- [X] 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

1. Deploy code-server as pod and create service in EKS cluster
2. Use Emissary-ingress as proxy and create mapping to code-server userpod (eg /tempmap/ --> userpod service)
3. Access the userpod at the URL www.domain.tld/tempmap/
4. Install Nvm , npm and angular
5. switch to the created directory and do ng serve and access the browser
6. Now we will get white screen error
7. Follow the code-server proxy guidelines
8. try a) use in src/index.html
b) add --serve-path /absproxy/4200 to ng serve in your package.json
9. 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?

- [X] I cannot reproduce this in VS Code.
- [X] I cannot reproduce this in GitHub Codespaces.

### Are you accessing code-server over HTTPS?

- [X] 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.

Guia de contribuição

Abrir o guia de contribuição

Avaliação

Esta issue ainda não foi avaliada.

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.