When testing with the client I found out, that the latest connect client 2.1 does not connect to the gateway when:
1. connection has been deployed by .pro file
2. .pro file contains setting check_remote_availability": true
"gateway": "vpn.test.lan",
"user_portal_port": 4442,
"check_remote_availability": true,
3. connection has been updated when userportal was enabled before
4. userportal is then disabled on WAN zone after the config has been loaded by connect client
it brings you the error: no response from gateway 443
Connect client then tries to check remote gateway availability on VPN Port 4442 or whatever configured for userportal, but not on the SSL VPN port 443.
So the error message is wrong because it indicates VPN port 443 is not responding but in fact it wants to connect to userportal port 4442.
If you change the .pro file to
"check_remote_availability": false,
Then connect, with userportal enabled, the config is downloaded.
You can then disable the userportal on WAN and the client does still connect without the error.
I don't think it makes sense to check the userportal port and not the SSL VPN port. At least the error message should contain the real port number, not something else.
This behaviour can be captured with tcpdump.
This thread was automatically locked due to age.
