- Products
- Learn
- Local User Groups
- Partners
- More
Access Control and Threat Prevention Best Practices
5 November @ 5pm CET / 11am ET
Ask Check Point Threat Intelligence Anything!
October 28th, 9am ET / 3pm CET
Check Point Named Leader
2025 Gartner® Magic Quadrant™ for Hybrid Mesh Firewall
HTTPS Inspection
Help us to understand your needs better
CheckMates Go:
Spark Management Portal and More!
Hi Everyone,
im currently encountering an issue with several drops of different sevices being rejected with the message Not allowed SSL version.
I checked the DB settings: ssl_min_ver is set to sslv3 while max is set to tls1.2 .
I also created a seperate rule for ssl inspect like described in sk34182., yet i still receive the error.
Currently it blocks me from initiating a rdp session within an existing Site 2 Site VPN Connection.
Remote_Desktop_Protocol (TCP/3389)
Reject
Not allowed SSL version
So far i was not able to find any other sk article regarding this issue,
Has anyone else encountered this problem?
Hi everyone,
it turned out that someone configured multiple Services with active protocol signature(TCP,UDP,) under R77.80.
But instead of matching them to the recommended port (e.g. 443 TCP) they were matched for any port. This led to the error that any tcp / UDP traffic which was encypted matched for those services (which were missing in the security and application policy rules). The issue became visible after the update fron 77.30 to 80.20 .
As a solution, i deleted both services.
Thx for all the help
Please check your RDP SSL Inspection is properly set. Look here: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...
If that does not help, you can try HTTPSi bypass rule for RDP specifically
Hi Valeri,
i tried the explicit https bypass rule for RDP, unfortunately the behavior is still the same.
I also tried your link, but i get the message: Solution could not be found in the system.
Yet i found a TCP service which could be a remnant from R77.30
Protocol: SSL_V3
Match By Port: Any
Protocol Signature: checked
Could it be that the service is mismatched since it fulfills the criteria for this object?
Yes, you might need to set up a _new_ RDP service. One inherited from R77.30 is no good
The action is bypass, so it is not the policy. Which HFA are you running at? With R80.30 you need at least Jumbo 50
@PhoneBoy I am afraid you are mistaken, please check the SK I have referenced above
Hi,
i just checked the version of the cluster.
Sorry, it seems i was mistake. R80.30 is the Console.
Currently installed:
HOTFIX_R80_20_JUMBO_HF_MAIN Take: 87
Hi everyone,
it turned out that someone configured multiple Services with active protocol signature(TCP,UDP,) under R77.80.
But instead of matching them to the recommended port (e.g. 443 TCP) they were matched for any port. This led to the error that any tcp / UDP traffic which was encypted matched for those services (which were missing in the security and application policy rules). The issue became visible after the update fron 77.30 to 80.20 .
As a solution, i deleted both services.
Thx for all the help
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
32 | |
17 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
2 | |
2 |
Wed 22 Oct 2025 @ 11:00 AM (EDT)
Firewall Uptime, Reimagined: How AIOps Simplifies Operations and Prevents OutagesWed 22 Oct 2025 @ 11:00 AM (EDT)
Firewall Uptime, Reimagined: How AIOps Simplifies Operations and Prevents OutagesTue 28 Oct 2025 @ 11:00 AM (EDT)
Under the Hood: CloudGuard Network Security for Google Cloud Network Security Integration - OverviewWed 05 Nov 2025 @ 11:00 AM (EST)
TechTalk: Access Control and Threat Prevention Best PracticesAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY