
# tail -f /tmp/vmware-root/vmware-horizon-client-593165.log due to the CdkSetLocaleTask error I tried altering the timezone and regional settings to match as those on the Windows client as it might have been an ssl certificate error due to timing but that didn't make any difference on the error
Vmware horizon client http error 503 upgrade#
The same configuration used to work previously except for some local upgrades and upgrade to the more recent vmware 16.2.1 version, so it might be an incompatibility with more recent vmware (however installing it on a fresh ubuntu installation with no vmware resulted in the same which rebuts the this), or more likely incompatibility with more recent debian kernel or libraries that the horizon client uses The exact reason for why this happens is unknown, but it might a bug or a library incompatibility due to a recent upgrade or incompatibility with some of the kernel modules The horizon client stopped working under Linux but works under Windows while trying the to connect to the same remote agent using latest 8.5.0 build or earlier versions - the same has been tried on multiple different debian-based installations, including a fresh Ubuntu VM installation and resulted in the same. Some additional useful information (or TLDR):
Vmware horizon client http error 503 how to#
I found some similar threads which seem to have been mostly left unanswered or resulted in a similar error but caused by reasons of major difference, thus I wondered if the vmware community or engineering team could look at this and advise on how to debug further what seems to be a cumbersome issue. The engineering team responsible for the remote setup confirmed that the issue and the root cause should not be on their side, and is not related to any IP or OS whitelisting. The reason for why the agent stopped working is unknown - I suspect it might be a library incompatibility due to a recent upgrade - reinstalling the agent or trying it from a different Linux configuration or VM did not work either so I believe it might be a bug in horizon on Linux itself. Please note that the same remote configuration works under the Windows client while trying to the same remote agent.

I am posting this thread as I am having an issue with the horizon client under Linux, which suddenly stopped working under Linux.
