topic Re: VPNSSL - Portal Settings in SASE and Remote Access

VPNSSL - Portal Settings

scddaniel83 — Tue, 11 Oct 2022 20:24:38 GMT

Hello guys,

We have a sslvpn configuration, which started to behave differently from yesterday, I know that the default address of the portal is https://vpn.xxx.xxx.xx/sslvpn , but many users always connected via https:/ /vpn.xxx.xxx.xx and were redirected to the correct address, I don't know if indirectly any recent changes may have impacted the behavior, but I would like to know how I can redirect the page when the user uses the other url? I thank the attention.

Re: VPNSSL - Portal Settings

PhoneBoy — Wed, 12 Oct 2022 21:06:32 GMT

What version/JHF of gateway?
What actions did you take prior to this occurring?

Re: VPNSSL - Portal Settings

the_rock — Wed, 12 Oct 2022 23:28:39 GMT

Is it possible port for web UI changed that could conflict? You can verify this by running from clish -> show web ssl-port. I second what phoneboy asked...what happened before you noticed this? Any changes in the environment?

Re: VPNSSL - Portal Settings

scddaniel83 — Thu, 13 Oct 2022 15:09:29 GMT

Thanks for the reply and sorry for the delay in the information.

We are on version R81.1.
What we changed was inserting a certificate in HTTPS>GATEWAYS, as we are in the process of implementing HTTPS Ispection. This certificate that I have already removed.

Re: VPNSSL - Portal Settings

scddaniel83 — Thu, 13 Oct 2022 15:31:49 GMT

We didn't change the UI web port. This is weird I'll look again at the logs.
>show web ssl-port
>web-ssl-port 443

Re: VPNSSL - Portal Settings

the_rock — Thu, 13 Oct 2022 15:34:14 GMT

I think as a test, you should, as ports might be conflicting.

set web ssl-port 4434

save config

test again

Andy