CAF Page (port 9443) not accessible in proxy enabled environments
It impacts CG where the machine does have internet access, and is using a proxy.
This can also occur when the environment is upgraded, and a proxy is used to register appliance, and upgrade it afterwards.
Change Guardian 5.1, 5.1.1, 5.2
There is a known issue with CAF 2.0.3 or older versions, where CAF is not able to handle space in the No Proxy Domains field. Removing the space and rebooting the appliance should solve the issue.
1. To access proxy settings open Yast2-> Network Services -> Proxy2. Find the "No Proxy Domains" section.3. Remove any spaces:
4. RebootE.g. change "localhost, 127.0.0.1" to "localhost,127.0.0.1"
Afterwards the CAF interface should be available.
There is a known issue with CAF 2.0.3 or older versions, where CAF is not able to handle space in the No Proxy Domains field.We found out that vabase-jetty.service (which should serve port 9443) fails.As we see from the service logs, jetty service is not able to come up.
# systemctl status vabase-datamodel.service vabase-jetty.service vabase.service------------------vabase-jetty.service - Jetty Web Application Server failed to start
------------------...while rest of the given services are active and running.
General recommendation, in case of hitting problem after upgrade, is to revert back to CG 5.1, include the fix, and then upgrade to CG 5.2, yet again, which ensures upgrade is clean.
This is a recommended step, not mandatory.