yuji.fushiguro
yuji.fushiguro
PostsComments
CCoder.com
Created by yuji.fushiguro on 4/29/2025 in #help
failed to WebSocket dial: failed to send handshake request on private EKS
Update: Firewall rule has been updated and confirmed by network guy that it is being allowed in the logs, but error is still persisting.
29 replies
CCoder.com
Created by yuji.fushiguro on 4/29/2025 in #help
failed to WebSocket dial: failed to send handshake request on private EKS
I do have one more problem I would like to resolve. I can't access my dashboard via HTTPS even though I have a certifacte attached to my deployment. From looking at my example files do you know why that might be?
29 replies
CCoder.com
Created by yuji.fushiguro on 4/29/2025 in #help
failed to WebSocket dial: failed to send handshake request on private EKS
I have a request in that will go in tonight and we'll see how it goes.
29 replies
CCoder.com
Created by yuji.fushiguro on 4/29/2025 in #help
failed to WebSocket dial: failed to send handshake request on private EKS
Network guy has confirmed that websocket traffic is being blocked
29 replies
CCoder.com
Created by yuji.fushiguro on 4/29/2025 in #help
failed to WebSocket dial: failed to send handshake request on private EKS
I'm not seeing anything within the helm values for the loadbalancer or ingress controller that would suggest otherwise. I did ping our networking guy so I'll wait to see what he says
29 replies
CCoder.com
Created by yuji.fushiguro on 4/29/2025 in #help
failed to WebSocket dial: failed to send handshake request on private EKS
*being
29 replies
CCoder.com
Created by yuji.fushiguro on 4/29/2025 in #help
failed to WebSocket dial: failed to send handshake request on private EKS
I can ask our network guy if websockets are be block by default but I'm unsure. I do know we are connect to our network via VPN, but any other networking stuff is beyond me 🤯
29 replies
CCoder.com
Created by yuji.fushiguro on 4/29/2025 in #help
failed to WebSocket dial: failed to send handshake request on private EKS
Only through port base routing on port 80 and 443 to my nginx-ingress controller target groups
29 replies
CCoder.com
Created by yuji.fushiguro on 4/29/2025 in #help
failed to WebSocket dial: failed to send handshake request on private EKS
By LB, do you mean Network or Application? I have a Network Load Balancer
29 replies
CCoder.com
Created by yuji.fushiguro on 4/29/2025 in #help
failed to WebSocket dial: failed to send handshake request on private EKS
I have a loadbalancer. I did add a code snippet to my ingress to my ingress as a troubleshooting approach but don't know if I added correctly 
ingress:
    enable: true
    className: nginx
    host: coder.example.com
    wildcardHost: "*.example.com"
    annotations:
      {
        cert-manager.io/cluster-issuer: coder-issuer,
        cert-manager.io/issuer-kind: Issuer,
        nginx.ingress.kubernetes.io/server-snippets: 
          "proxy_set_header Upgrade $http_upgrade;
          proxy_http_version 1.1;
          proxy_set_header X-Forwarded-Host $http_host;
          proxy_set_header X-Forwarded-Proto $scheme;
          proxy_set_header X-Forwarded-For $remote_addr;
          proxy_set_header Host $host;
          proxy_set_header Connection "upgrade";
          proxy_cache_bypass $http_upgrade;"
      }
ingress:
    enable: true
    className: nginx
    host: coder.example.com
    wildcardHost: "*.example.com"
    annotations:
      {
        cert-manager.io/cluster-issuer: coder-issuer,
        cert-manager.io/issuer-kind: Issuer,
        nginx.ingress.kubernetes.io/server-snippets: 
          "proxy_set_header Upgrade $http_upgrade;
          proxy_http_version 1.1;
          proxy_set_header X-Forwarded-Host $http_host;
          proxy_set_header X-Forwarded-Proto $scheme;
          proxy_set_header X-Forwarded-For $remote_addr;
          proxy_set_header Host $host;
          proxy_set_header Connection "upgrade";
          proxy_cache_bypass $http_upgrade;"
      }
29 replies
CCoder.com
Created by yuji.fushiguro on 4/29/2025 in #help
failed to WebSocket dial: failed to send handshake request on private EKS
I did find a work around to be able to push my templates from my local machine and I was able to do so by using port forwarding. It's not ideal but it helped me get to the next step. 
k port-forward svc/coder 8080:80 -n coder
Forwarding from 127.0.0.1:8080 -> 8080
Forwarding from [::1]:8080 -> 8080
k port-forward svc/coder 8080:80 -n coder
Forwarding from 127.0.0.1:8080 -> 8080
Forwarding from [::1]:8080 -> 8080
I still would like to get pass this websocket issuse. This helped me be able to push templates, but then I ran into the same websocket error when my workspace tries to spin up. Here are the logs from the pod that's trying to start the workspace
29 replies
CCoder.com
Created by yuji.fushiguro on 4/29/2025 in #help
failed to WebSocket dial: failed to send handshake request on private EKS
The healthcheck page is showing the same error for Websocket with error code EWS01
29 replies
CCoder.com
Created by nicolas on 3/14/2025 in #help
Installing coder in EKS
Created a new chat called failed to WebSocket dial: failed to send handshake request on private EKS
53 replies
CCoder.com
Created by nicolas on 3/14/2025 in #help
Installing coder in EKS
Yes, I can do that. I think I go pass my current issue by creating an offline image that has a filesystem mirror to the providers and modules. My new error is occuring when I try to push a new template to the server. It states Encountered an error running "coder template push", see "coder templates push --help" for more information error: begin streaming logsL failed to "websocket dial: failed to send handshake request: Get "http://my-coder.example.com/api/v2/template/aoisdf3 . . . ./logs?follow": read tcp connection reset by peer
53 replies
CCoder.com
Created by nicolas on 3/14/2025 in #help
Installing coder in EKS
Hello, I jumped in this chat because I have a similar setup in EKS except my cluster has cert-manager and external DNS. So I'm able to get a TLS cert from Venafi and create a record in Route 53 to access the dashboard. The problem that I'm facing is that my EKS Cluster is private and does not have access to the internet. So I tried 2 approaches and they yield similar results. Problems I'm seeing with my setup 1. When I try to use a K8s Deployment template I see error in the logs that says, "failed to query provider from registry.coder.com". 2. 1. When I try to use a K8s Devcontainer template I see error in the logs that says, "failed to query provider from artifactory.my-company.com" I don't know why 2 templates are creating 2 different errors Steps I took to try to solve my problem 1. In my helm chart, I have an initcontainer that "supposedly" pull a different Terraform binary to use, pull the terraformrc file from the initcontainer image, and also the credentials.tfrc.json file as well. Since my cluster doesn't have access to the internet but it does have access to Artifactory. I thought doing this would remedy my issue. 2. log into the server with the coder CLI and update the templates. This didn't work because when I try to push the template I get a error stating, "Websocket protocol violation: Connection header "close" does not contain Upgrade".
53 replies