Having issues with proxmox connector

[Jake-Schuler]

Howdy, so I'm working on a project and wanted to use rustguac to connect to the VMs for users, however whenever it attempts to connect it the request just hangs indefinitely. The container running rustguac is able to connect to proxmox as it can resolve a bunch of stuff and auto fills the node name, but it's unable to start a session and spiceproxy is running on the the node as well. I would also like some clarification on why it uses the domain name when I'm using an IP address in the request and if there's anyway to change that. I did also try changing my hosts file and had no luck with it.

request:

  --url https://rustguac.example.com/api/sessions \
  --header 'Authorization: Bearer <rustguac token>' \
  --header 'content-type: application/json' \
  --data '{"session_type":"proxmox","proxmox_url":"https://192.168.68.88:8006","proxmox_vmid":9000,"proxmox_node":"proxmox","proxmox_token_id":"<proxmoxtoken>","proxmox_token_secret":"<proxmox token secret UUID","proxmox_verify_tls":false}'

Rustguac logs (with replaced domain name):

Sep 05 21:28:39 vdi-controlplane rustguac[96]: 2026-09-05T21:28:39.777386Z  INFO rustguac::api: Session creation requested admin=admin client_ip=192.168.68.15 session_type=Proxmox target=proxmox/9000
Sep 05 21:28:39 vdi-controlplane rustguac[96]: 2026-09-05T21:28:39.816712Z  INFO rustguac::session: Creating Proxmox VE SPICE console session session_id=63d023a1-a60f-4b50-bc8d-26c61968f66e node=proxmox vmid=9000 proxy=http://proxmox.example.com:3128

[davekempe]

the name resolution stuff is due to the way the api works - the machine you connect to proxies your connection to the target host (in the case of a multinode cluster). Its best you get DNS working, for this reason. The hang is probably related to this or a problem with port 3128 not working. while port 8006 works fine, you need 3128 as well for SPICE itself.

[EdwinPA]

Hello, and sorry for my English, as I am using a translator.

I have also been having issues with SPICE. After reviewing the logs, I noticed that guacd cannot find the SPICE library.

I tried compiling Guacamole Server manually, and with the help of AI I was able to investigate the issue further. According to the information I found, SPICE support is no longer available in the current Guacamole Server version.

I would like to know if this is correct, or if there is any additional configuration or alternative way to enable SPICE support.

[davekempe]

Hi @EdwinPA this is a different issue. However rustguac includes patches for gaucamole-server that enable spice support. These are a copy of the pull requests in the upstream project, with some local modifications. There is an install script that will make it work on debian 13. Are you using debian13? There are many many dependencies in this project, so getting them to work on different distros is just going to be docker otherwise.