Android device (Samsung S21) with Forticlient VPN do connect
successfully (100%), get an IP address and are connected but no traffic
is going through. Via Forticlient Windows everything works as expected
and traffic is allowed and routed normally. Po...
Previously on FortiAp 6.2 I could easily turn on and off the LEDs on the
AP by
following:https://docs.fortinet.com/document/fortiap/7.0.4/fortiwifi-and-fortiap-configuration-guide/948780/led-options
Now after flashing my FortiAP-221E to (v7.0-build00...
Is it possible to. Open 443 on an ip adress through a fortigate (yes
:-)) to an nginx server. To then have that nginx server serving several
urls and lets encrypt to a webserver(s). And then the magic: to have a
url eg. vpn.domain.com serving back to...
On a Fortigate 60E with v6.2.3 - build1066 I have 3 FAP-221C FortiAP's
successfully "connected". Thus 3 AP's have a fortiprofile connected to
them and are working and having clients etc. Now when I want to connect
a 4th FAP-221C I have issues. Whatev...
1 out of 3 221C APs has radio 2 with 3 ssids on 5 ghz. No client are
connected (they cant because ssids are not seen there). The channel
utilisation is99% ans client count 0. NOTHING helps... what can be
wrong?
So some progress. It seems hat after updating to fortios 7.0.x something
changed in the sslvpn settings. After changing from middle to top
setting all is fine again. What is very weird is that this only had
direct influence on the android VPN client ...
Hi, wanted to give this another push. Since my original question was not
so successfully answered.I have tried to change the ssl vpn port to
8443. (management to 10443 first). Instantly I cannot longin to ssl vpn
from KPN 4G mobile. Changing back to ...
Hi ken Felix, thank you very much for taking the time to resond to my
question! Of course it makes sense that the widely accepted port for SSL
and https is 443. other ports are just "workarounds" and possibly not
enabled in a guest network (hence my ...
Ok, so now again trouble after 2 hours of previous post update.
Rebooting was only solution. 50% mem and 4% cpu nothing unusual but
couldn't have too much downtime... fortinet, please advise!
