Browser Error connecting to SSL VPN Page

Our users have also been getting this intermittent error when connecting to the SSL-VPN portal page. But for me the only way to fix it is to change the SSL-Cert in the VPN>Config section to ' self-signed' apply it, then change it back to our company ssl cert OR to reboot the device. Currently running FWF60B - v4.0,build0639,120906 (MR3 Patch 10) it also was happening in the previous firmware version. Luis

Fortigate 5.0 Patch 1. I too, had users unable to connect to ssl vpn (10443) port. They would receive " http Error 400" . Had to reboot to resolve.

I' m having this issue as well - 1240B running 4.0MR3 (Patch 7) with IE 8 / Firefox 18 (IE 7 on an older laptop continues to work fine). The FortiClient VPN 4.3.5.0472 reports an error - VPN server may be unreachable -5 (again older laptop with FortiClient 4.2.6.294 works). Using a self-signed certificate on the FG for SSL VPN. Pam Keetch

I updated to the latest firmware for my device (v4.0,build0646,121119 (MR3 Patch 11) and so far two days without the problem, this is a new record, so maybe it' s fixed. Luis

Our issue seemed to be resource-related; during peak traffic hours the SSL VPN webpage would not load. Have rebooted and so far so good. Pam Keetch

I just want to follow up and clarify the problem I was having. I am not talking about using the ssl-vpn client or even doing anything ssl-vpn related other than connecting to the ssl-vpn portal site to just get to the login screen. My users would not even be able to get to the login screen of the ssl-vpn portal, it would work then randomly it would stop working (site would time out). The only two ways to fix it was to restart the device (which was not good in the middle of the way) or to change the ssl-cert to a different one, apply changes, browser to the portal page, then go back to the admin and change it back to your original ssl-cert. Oh and I did verify it also happened to the self-signed Fortinet ssl-cert, so it doesn' t matter if you are using your company' s ssl-cert or Fortinets. Anyway ever since I updated the firmware this problem has not occurred. Luis