Hi Team,
I’ve bricked my comet by setting the power level to 98ma. I followed the guide to reload the firmware HERE and everything worked, until the point I tried to login to the device.
It keeps throwing 502 bad gateway errors in the browser console (tailscale IPs).
It also doesn’t work using just the local IP, same issue.
I need a reset that doesn’t keep my configuration, since that appears to be the source of my problems.
Here is my override.yml:
kvmd: msd: type: disabledotg: vendor_id: "0x046D" product_id: "0xC52B" manufacturer: "Logitech" product: "USB Receiver" serial: "" usb_version: "0x0200" max_power: 98 gadget: "Logitech" config: "RQR12.11_B0032" devices: audio: enabled: true start: true product: "Logitech USB Microphone" msd: start: false default: inquiry_string: cdrom: vendor: "ASUSTek Computer, Inc." product: "Mass Storage Device" revision: "1.01" flash: vendor: "ASUSTek Computer, Inc." product: "Mass Storage Device" revision: "1.01"
minmie
March 6, 2026, 3:14am
2
Could you SSH in and then delete all your changes to override.yml?
Thank you, that gave me the idea to hit the reset button again, and it appears to have fixed it. Will play around with the settings some more.
Actually, from the override.yaml file I sent earlier, is it possible to set the vendor_id, product_id, etc from that yaml file? I haven’t seen any clear examples of how to do this.
When I reboot, none of the changes stick.
Thank you @minmie , is there a way to do it programmatically? There are some parameters that aren’t exposed via the UI, and want to change them via the override.yaml or an API.
It’s much easier for me to configure the devices via the command line vs clicking through a bunch of UI elements.
minmie
March 9, 2026, 1:59am
8
You can view all modifiable configurations by using kvmd -m.Then add it to override.yaml
Thank you @minmie , I tried that, but none of the values are sticking from the /etc/kvmd/override.yaml file.
I’m running the following command after every change:
sync && reboot
The values never change from the UI.
minmie
March 10, 2026, 1:32am
10
If you ever modify USB identify settings on the website, you should remove content of `/etc/kvmd/user/boot.yaml`, or it will finnally be override.
I checked the contents of the file, and there’s nothing inside:
minmie
March 10, 2026, 4:28am
12
your filesystem is broken? Try reset default?
I already reflashed the device, as well as did the button reset.
minmie
March 11, 2026, 2:18am
14
Can you allow us to acccess your KVM remotely by you running comnmand `tmate` and provide us the link in PM or send it to zefu.du@gl-inet.com ?
Hi @minmie , I sent the output to you via DM yesterday. Thank you.
minmie
March 12, 2026, 1:41am
16
your device seems work fine , what is the problem you encounter now?
Yes, the device is functioning. The problem is that changing the override.yaml does nothing.
This is the script I run:
curl -fsSL ``https://pastebin.com/raw/MwXEmsX6`` -o /etc/kvmd/override.yaml && printf '\n' >> /etc/kvmd/override.yamlsync && reboot
minmie
March 12, 2026, 2:15am
18
I see that the content of override.yaml matches what's on your website. Do you mean it will be gone after a restart?
The override.yaml file does not change the configuration of the Comet. The file is fine, and seems to be well-formed.
The expectation is that changing the override.yaml will change the USB characteristics and identifiers of the Comet, which it does not.
minmie
March 12, 2026, 2:20am
20
Of course not, it only changes the underlying actual effects. If you want it to alter the display on the page, you should place it in boot.yaml.
Oh, that’s new information. So if I want to change the usb product id, serial, or disable the mass storage, it has to be written to the boot.yaml?
I don’t see any forum posts or articles about a file called boot.yaml. Is there documentation on this?
