-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Hello,
first of all, thank you for your amazing project – I really appreciate the tremendous amount of work that has clearly gone into it.
I recently had to reinstall my home workstation running Proxmox. One of the components is a Kasm server with autoscaling Windows 11 VMs. I followed the official guide at:
The VM is provisioned correctly and the Kasm startup script finishes successfully according to its logs. However, I’m running into an issue with the Kasm service contacting the Kasm server. When I check the Kasm service logs at C:\Program Files\Kasm\logs.txt, I see the following:
2025-11-29 23:45:35,361 - INFO - load_startup_parameters C:\Program Files\Kasm 2025-11-29 23:45:35,391 - INFO - Flag --await-domain is set to False and domain is not joined 2025-11-29 23:45:35,393 - INFO - Refreshing auth token which expires 1969-12-31 16:00:00 2025-11-29 23:45:35,393 - ERROR - Missing token in api config 2025-11-29 23:45:35,393 - INFO - Starting Kasm Upload Server (version: 1.7.c54746a5) On Port 4902 2025-11-29 23:45:40,992 - INFO - load_startup_parameters C:\Program Files\Kasm 2025-11-29 23:45:41,013 - INFO - Flag --await-domain is set to False and domain is not joined 2025-11-29 23:45:41,013 - INFO - Refreshing auth token which expires 1969-12-31 16:00:00 2025-11-29 23:45:41,013 - ERROR - Missing token in api config 2025-11-29 23:45:41,116 - ERROR - Registration failed: Registration failed with an exception: 'server_id' 2025-11-29 23:45:41,116 - ERROR - Traceback (most recent call last): File "agents\base.py", line 529, in register KeyError: 'server_id' 2025-11-29 23:45:51,895 - INFO - load_startup_parameters C:\Program Files\Kasm 2025-11-29 23:45:51,919 - INFO - Flag --await-domain is set to False and domain is not joined 2025-11-29 23:45:51,919 - INFO - Refreshing auth token which expires 1969-12-31 16:00:00 2025-11-29 23:45:51,919 - ERROR - Missing token in api config 2025-11-29 23:45:51,921 - INFO - Starting Kasm Upload Server (version: 1.7.c54746a5) On Port 4902
From these logs, it appears that the service is complaining about missing server_id and API token values in the config.yaml file, and these entries are indeed not present in the file. When I switched back to the old startup version in "3670335" everything works again.
Thank you for reviewing this problem