Fortigate 201F on 7.0.14 firmware.Website: www.reliafund.comWe use this
site for ACH transactions on a daily basis, so it's pretty important.
According to the Fortiguard webfilter, this site was updated to a
malicious category on Feb 12, 2024. Prior ...
New to Fortinet, so please bear with me. I have a new Forti network
environment managed by a FortiGate (7.0.12) and have trouble setting up
a standalone switch (7.4). I do not want this switch managed by the FG
at all. When I initially set up this sw...
Oh, need to mention for those who see this down the road... The white
block page is a DNS block. The second block with FortiGuard is the
category violation block. This should help troubleshoot how you work
your bypass in your Fortigate.
Talked with TAC and here is the resolution. Basically, I needed to flush
DNS cache on my test PC or the DNS server. Problem
summary:----------------------------* Unable to allow URL through
FortiGate.* Static domain filter entry doesn't stick after s...
Looks like the site was re-categorized overnight because it is now
accessible. I'd still like to know why I wasn't able to unblock with all
of the known solutions. I have a ticket in with support. If I get an
answer as to why, I'll post back here.
Just figured out the incorrect policy name. Since Reliafund is blocked,
it cannot resolve the FQDN address entry I created. I found the real IP
(72.168.70.153) and then created a subnet address entry and added that
to the policy. When using policy lo...
Yes, this worked great. Thank you!For anyone reading this in the future,
here are the approximate steps I took to resolve this issue...Uplinked
the switch I wanted configured as a standalone.My FG sees this switch
and adopts/authorizes.Deauthorize an...
