- CheckMates
- :
- Products
- :
- Quantum
- :
- Remote Access VPN
- :
- VPNSSL - Portal Settings
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VPNSSL - Portal Settings
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What version/JHF of gateway?
What actions did you take prior to this occurring?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think as a test, you should, as ports might be conflicting.
set web ssl-port 4434
save config
test again
Andy
