It's probably the VIP you created. First try to make the policy without
the VIP, using only the nat, or second option, restrict the port in the
VIP with the port filter so that it does not apply to all ports. and
select the especific interface for th...
I don't understand why you use a VIP instead of a normal nat. but in
case you want to use the VIP. specify HTTPS port 443 on that VIP to see
if it doesn't conflict with having the port range open on the VIP.
As mentioned above, verify the addresses of the indicated source and
destination objects, that they are correctly created.You could also try
removing the HTTPS service from the policy and leaving it "ALL"
initially to test and confirm if the traffic ...
