Access GUI port.

Reply
Highlighted
L0 Member

Access GUI port.

 There are two locations where the only dedicated link is (X) access to the management of the security teams is through publication (https: // xxxx: port) All security teams have a management IP and are published with the same public ip 200.15.21.1 After the upgrade, from version 7.1.25 to 8.1.15-h3, it is observed that when you want to access the master firewall and backup through the GUI, both are closed. When GUI access is open through IPsec VPN, it is not affected when you want to access the firewall through GUI (master or backup). When you have GUI open in master and you try to open GUI in backup, after a few seconds they close both and vice versa the result is the same. It is as if both publications that have the same public IP but different port cannot coexist.
They will have some workaround for this behavior.

Highlighted
Cyber Elite

@David.Arellano So if I understand what you are talking about you essentially have a NAT rule that directions for example  https://x.x.x.x:8443 to your primary firewall GUI and https://x.x.x.x:9443 to your secondary GUI? Is that right? If this is accessed through the public IP have you ensured that you aren't running into any DoS limit that you potentially have setup? 

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!