Why when blocking https does that stop access to the XG GUI?

Because basically the firewall can block access to itself. There is no "Overwrite own process" rule hidden in the system. If you explicitly block HTTPs, it will block https. If you block https, this could mean, the webproxy is getting involved. The web proxy can potentially block port 4444 as well, if it is  https request. 

Because basically the firewall can block access to itself. There is no "Overwrite own process" rule hidden in the system. If you explicitly block HTTPs, it will block https. If you block https, this could mean, the webproxy is getting involved. The web proxy can potentially block port 4444 as well, if it is  https request. 

Thank you for the answer, but to me that does not make sense.The firewall rule does not have the web proxy enabled and having the web proxy intercept firewall management traffic does not make sense unless you specifically setup a firewall to do that. Further why isn't the traffic logged so you can analyse what has happened? Yes, there is a report that shows all the changes made and who made them.

Ian

Looking at the drop rule: 

It has proxy enabled. That is the reason, you see a green firewall entry in logviewer but the web proxy is dropping. 

That is only true, if you use the proxy on your client. Simply because the proxy will pick up this traffic: 

While you answer is logical, i am not using the proxy on the client.

Ian

Do you see anything in Logviewer for Port4444?