- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
08-27-2021 04:09 AM
I turned on Captive Portal a couple days ago on a test rule restricting access between two servers before i turn it on for production.
The rule restricts access to the end server as expected and navigating to http for the target server results in the following URL Redirect: https://172.20.20.9:6082/php/uid.php?vsys=1&rule=0&url=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The Webform is configured for one of the IP's used by the Firewall, but the Port 6082 required for Captive Portal SSL appears to not be listening.
I followed and have checked multiple times the steps in the following guides:
Is there anything else i can check that may shed some light on why this isn't working?
08-27-2021 08:31 PM
Do you decrypt HTTPS traffic that should be matching your captive portal rule for your test?
If not, the firewall denies the traffic but doesn't actually serve up the captive portal. This is to prevent you servicing something that is simply going to cause a certificate warning in the users browser. You don't want to be telling people that running into cert warnings is "normal" and that they should "bypass" it because then they'll do it for everything and those warnings become meaningless, which is a poor thing to teach your user base.
02-28-2024 03:46 PM
I am experiencing a similar issue. While I agree i do not want to make forward untrust behavior normal, I do need a clear mechanism to test the functionality before moving into production. This also occurs when the self signed CA cert of the device is in the endpoint trust store.
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 LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!