You can simplify. You already got http-to-https redirect on entrypoint and also the X-Forwarded-Proto header is set automatically by Traefik.
Are you sure proxmox-spice-tls with tls: passthrough: true will work? You forward the request encrypted with a Traefik LetsEncrypt TLS cert, but your target service will need access to the TLS cert to decrypt the request.
Tbh I don't really know if that part is being used. I'm just getting started with Traefik so I don't have the complete picture. I just moved from Ngnix Proxy Manager and still getting the hang of it..
This config does work, I can click the "Console" button on my Proxmox instance (while accessing via my proxy subdomain) and it does connect with remote-viewer and I can work with my VM just fine (it's an ubuntu 24.04 install), but I don't really know if the resulting connection is encrypted.
After banging my head against this issue with ChatGPT and this forum thread, ChaptGPT has given me a working âconfig.ymlâ section for making this work. Besides this you need the proper entry points in the âtraefik.ymlâ file as shown above in other comments.
Canât guarantee it will work for everyone or if this is even the proper way to do it or not but it works for my Proxmox VE 9.1.1 cluster.
One thing I have run into is after adding multiple nodes, is that if you bring it up and it says connected but doesnât list a display to enable, just reconnect with a new spice file and it works.
```