Fresh Coder helm installation fails Workspace creation
I created a coder instance using helm following step-by-step the docs using a custom TLS ingress that works fine.
The installation has been successful, but when I try to create a workspace using the default kubernetes template, the Coder UI fails to connect with the pod with this error:
While in the coder controller I have these logs:
I attached the screen of what the UI shows, while on kubernetes the pod is in "running" state.

Solution:Jump to solution
@Phorcys I solved it!
The problem was the ingress class I was using, I had to enable websockets in the annotations.
For everyone who users Contour wondering how I solved it, this is the config:
```YAML
ingress:...
10 Replies
<#1349350556233109634>
Category
Help needed
Product
Coder (v2)
Platform
Linux
Logs
Please post any relevant logs/error messages.
I am also not able to connect to the istance using VSCode as I get this error:

hey, are you using a self-signed cert?
Hi, No the certification is issued by letsencrypt and is managed by an AWS load balancer.
So the ingress https://coder.mydomain.com points to the Application Load Balancer that manages the certification and then redirects to the kubernetes masters ips.
Don't know if it helps, but I have also this other error from the UI:

Solution
@Phorcys I solved it!
The problem was the ingress class I was using, I had to enable websockets in the annotations.
For everyone who users Contour wondering how I solved it, this is the config:
I will close the issue on github with the answer.
great! try to see if you can also enable DERP upgrades
Yes I was just looking into it! Thank you very much 🫶🏻
thanks for reporting on this, this will help other users :-)
@Phorcys closed the thread.