If you have another GP gateway with no IP configured, it will take precedence and you will see it's certificate when accessing all other gateways which has IP's. You can change the no IP gateway to a loopback with a dummy IP and the issue will be resolved. The portal /gateway with no IP address takes priority over the portal configured with an IP address. Ideally the GP config without an IP is supposed to be done only with DHCP IP and not static IP. So the config using IP as none is incorrect in case of static IP. I think Palo has to alert when this configuration taking place, https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClHRCA0 TLS Certificate of Global Protect portal /gw with no IP address overrides portal with an IP address Global Protect presents wrong TLS certificate of another portal.
... View more
It is supported by PaloAlto: https://www.paloaltonetworks.com/documentation/80/pan-os/web-interface-help/globalprotect/objects-globalprotect-hip-objects/hip-objects-custom-checks-tab Process List To check the host system for a specific process, click Add and then enter the process name. By default, the agent checks for running processes; if you just want to see if a specific process is present on the system even if not running, clear the Running selection.
... View more