Blocking site

[feisal]

i am getting block for my site i tried to add webfilter but still it shows the site is blocked. 

the first entry is working fine but the other enter is not releasing the site.

my device is

FortiGate 60E v6.2.3 build1066.   thanks

[sw2090]

Is there a reason why you created this as type "wildcard"?

You set the action to "Allow". This means this rule will alow it. But it also means if there is any other rule matching after this which blocks it it will still be blocked.

I suggest using action type "exempt" to make the url filter stop once it matched a rule to prevent this from happening.

[Daniel_Aguilar]

Hello, I think because you are using a WildCard I will recommend to you to use this wildcard and check what happens:

213.42.230.213:4443/*

Will be very helpful that you show the web filter log when you try to access to that URL.

[Dave_Hall]

There is a port number provided in these URL entries, so I am wondering if the fgt will interpreter that is an http or https connection.  Full SSL security inspection would be needed if you want the fgt to be able to see the full URL if HTTPS. 

I agree with the other posters in this thread - if you want to allow access to this site via URL filtering without further utm processing - - an exempt rule is needed.  a possible example of a common URL wildcard rule would be :  e.g. 213.42.230.213:4443/yaghut/* or 213.42.230.213:4443/* 

But if you simple want to allow direct access to 213.42.230.213 from non HTTP/HTTPS means, you may want to consider setting up a firewall policy allowing access to the IP address (/32) and apply whatever UTM feature on that connect (e.g. IPS) if you think you need it.  Move this firewall rule up in the firewall chain so it can be triggered.  This method is not preferred if 213.42.230.213 is a hosting server for multiple web sites that are outside your own "hosted" website.

[jamesseth]

Thank you for the share information...now I am doing action type "exempt" to make the URL filter.