Is Socket.io supported with the letsencrypt enabled inside traefik v2?

Traefik Traefik v2
,
1

I'm trying to use traefik as a reverse proxy for websocket here's my traefik labels for the docker container:

      - traefik.enable=true
      - traefik.docker.network=web
      - traefik.http.middlewares.redirect-https.redirectScheme.scheme=https
      - traefik.http.middlewares.redirect-https.redirectScheme.permanent=true
      - traefik.http.routers.api_node-https.rule=Host(`*****`)
      - traefik.http.routers.api_node-https.entrypoints=websecure
      - traefik.http.routers.api_node-https.tls=true
      - traefik.http.routers.api_node-https.service=api_node
      - traefik.http.routers.api_node-http.rule=Host(`*****`)
      - traefik.http.routers.api_node-http.entrypoints=web
      - traefik.http.routers.api_node-http.middlewares=redirect-https
      - traefik.http.routers.api_node-http.service=api_node
      - traefik.http.services.api_node.loadbalancer.server.port=3000

traefik returns a Badgateway response . also there is no log message about this container inside the logs of traefik itself.
Before traefik the socket io app was using the certificates inside itself.
does any body know what am I doing wrong? or does traefik v2 support websockets at all?

2

Is traefik also connected to the web network?

Is the container still doing TLS?

Yes traefik supports websockets. No special configuration required, at least I haven't done any. I have signalr and socket.io endpoints.

3

thank you for your response.
yes. traefik is on the web network that is external.
no. I have disabled the tls part.

4

Curious. I encounter this when the networking is not correct and perhaps when the endpoint is on the wrong port.

Crank the trafik logging up to debug, and see whats what is my advise. After checking out the traefik dashboard of course.