- Products
- Learn
- Local User Groups
- Partners
- More
The Great Exposure Reset
24 February 2026 @ 5pm CET / 11am EST
CheckMates Fest 2026
Watch Now!AI Security Masters
Hacking with AI: The Dark Side of Innovation
CheckMates Go:
CheckMates Fest
Found a block action reason: Blocking request as configured in engine settings of Application Control...
Precise Error: Internal system error in HTTPS Inspection due to categorization service timeout...
So I went to Blades/Application Control & URL Filtering Settings/General and changed Fail mode to 'allow all requests (fail-open) and installed policy.
Problem solved, any input on what's happening?
There's a few different possibilities on this.
The TAC can assist you with troubleshooting the exact cause.
I'll give you 100 points for the 'few different possibilities'.
As admin, I can give myself all the points I want ![]()
Unfortunately the information is in an internal SK.
And now that I read it more closely, it says "gather the following debugs" and doesn't provide much of an explanation.
I'm chatting with TAC and they are struggling...can you give me the sk# please?
I searched SK for the error message you provided, which brought up sk118440.
My guess is they will have to get R&D involved.
With Access Mode set to Allow, I am seeing a very small number of Alerts on this today. Does anyone know how SSL inspection reacts to a SSLv3 connection? I know they should not exist but just asking the question, maybe a client is doing this.
Thanks..
I believe, by default, this is allowed.
You can prevent that as described here: Check Point response to the POODLE Bites vulnerability (CVE-2014-3566)
I am experiencing this issue today. The only changes we made in the FW cluster was to enable enhanced SSL inspection. For some reason two banking related sites were not working until we configured enhanced SSL inspection. The day after we did these we started seeing many alerts for the Rad service not responding and that categorization was timing out for application control. However, TAC said enabling enhanced SSL inspection did not cause this. Plus we tested by turning it off. I am not sure why this is suddenly happening, but in the interim, I had to do the same which was setting the fail mode for application control to Fail-Open. I've scheduled an advanced debug with TAC to figure this out. Very strange. Anyone have any new or updated info on this?
Calling Aaron Vivadelli !!
Just hit this today for a brand new https inspection turnup on newly upgrade R80.30 cluster. Opened TAC case, grabbed debugs. We'll see what the issue is.
I'm having the same issue with URL filtering and SSL inspection R80.30, brand new turn up.
Any clues yet?
Ok, our issue ended up being an issue with the gateway and outbound traffic. Make sure the gateway can get outbound to do http/https requests. It needs to do this for categorization.
Once we fixed this, we were quickly online and https inspecting for a few test workstations.
Interesting enough, once we turned it on for the testing hosts, we also some issues with other hosts that we also had to put an override in place for. This traffic went over a VPN and was NOT internet bound so did not match the policy for bypass.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 26 | |
| 21 | |
| 10 | |
| 9 | |
| 8 | |
| 8 | |
| 7 | |
| 7 | |
| 7 | |
| 5 |
Thu 19 Feb 2026 @ 03:00 PM (EST)
Americas Deep Dive: Check Point Management API Best PracticesTue 24 Feb 2026 @ 11:00 AM (EST)
Under The Hood: CloudGuard Network Security for Azure Virtual WANThu 19 Feb 2026 @ 03:00 PM (EST)
Americas Deep Dive: Check Point Management API Best PracticesTue 24 Feb 2026 @ 11:00 AM (EST)
Under The Hood: CloudGuard Network Security for Azure Virtual WANAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY