Hello, anyone experience any odd issues where it doesn't appear that the ssl-vpn daemon is listening on WAN2? When I enable debugging I never see a connection attempt regardless of what port I set the daemon to listen on. I've tried ports that I know are open and still nothing. I'm guessing this is a bug but wanted to see if I'm the only one experiencing this.
Regards,
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
It turns out that despite the GUI settings being correct, the authentication portion of the SSL VPN config in the CLI showed that it was still tied to WAN1. Changing it to WAN2 fixed the problem. Relevant config section below.
set default-portal "full-access" config authentication-rule edit 1 set source-interface "wan2" set source-address "all" set groups "VPN Users" set portal "full-access" next end
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1705 | |
1093 | |
752 | |
446 | |
230 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.