I’m currently trying to patch the supervisor api /v1/device/host-config and it doesn’t seem like the change is taking effect.
I sent a patch request including all the proxy details I wanted the host to use and the supervisor api responded with a [200] OK message. Then I got back the host-config and nothing had changed. I got the host config… then changed host_config[“network”][“proxy”] = {“ip”: “xxx.xxx…” …} sent that as a patch to the supervisor api and then even issued a reboot api call (reboot worked) but when the device came online again I got the host-config nothing ever seemed to change. I’m at a loss for how to troubleshoot this since the api keeps giving me OK responses. Please can anyone help me out here??
When I try to patch the host-config I still get an [200] okay with nothing happening and on the host there is no /mnt/boot/system-proxy/redsocks.conf which I assume the patch would make.
Also It seems like it could be a bug that the proxy config file has to exist before the host-config can be gotten. Or perhaps that file is supposed to exist by default in the boot mount and my boot config is messed up.
Thanks for updating! Indeed, the first few patch versions of Supervisor 14.4.x had that bug, and it should be fixed with v14.4.6. Let us know if there are any further issues with host config!