- Products
- Learn
- Local User Groups
- Partners
- More
Firewall Uptime, Reimagined
How AIOps Simplifies Operations and Prevents Outages
Introduction to Lakera:
Securing the AI Frontier!
Check Point Named Leader
2025 Gartner® Magic Quadrant™ for Hybrid Mesh Firewall
HTTPS Inspection
Help us to understand your needs better
CheckMates Go:
SharePoint CVEs and More!
I heard another customer had this issue and they rolled back to previous jumbo and worked fine again. Definitely seems like an issue with take 79.
I am using Take 79 and RADIUS is working fine for me. But I didnt install any older Takes, only Take 79 on top of R81.10 (new deployment).
That said, are you able to uninstall any of previously installed Takes and install only Take 79 on R81.10 ? Maybe there is some conflict between different Takes...
Curious, are you using RADIUS to authenticate Gaia administrators?
Please take it with TAC
Val, I post on here so I can avoid talking to TAC.
Lol, I appreciate it, but sometimes we have to. If it is a bug, there is no other way.
Hi,
Val is correct, the proper way is to open a ticket to TAC
As we’ve noticed your post we are looking into it and working on this in R&D
As a work around you can add a server or update one attribute and the RADIUS will return
Regardless a solution will be introduced in the coming jumbos
same issue on every cluster updated with Take 79...
it's looks like this jumbo "forget" the radius key .
try to remove the radius config and add it again and it will works
🙂
I can confirm, this also happens on management too (seen it on MDS and a dedicated SmartEvent server). Deleting the aaa radius-servers from CLISH and then re-adding them fixes it.
I've had a similar problem after upgrading to latest jumbo on R81.10. I think the problem could be the PSK got corrupted somewhere.... after configuring it again in the GAIA the RADIUS auth started working again. Did you try that? Also try to remove and re-add the RADIUS servers again if the PSK workaround didn't work
Hi, I would like to update that a Jumbo containing a fix will be released in the coming one
Strange we have the same issue on all gateways and SMS upgraded to r81.10 take 81 was this already fixed or do we need to manually reconfigure the radius on all manually?
Try only to configure the preshared key again and check if that fixes the issue. It worked fine for me... I didn't have to reconfigure all regarding RADIUS, only the PSK
According to the JHF documentation it was fixed in take 82:
The following was resolved in T82:
After an upgrade, the RADIUS Server is unavailable and authentication fails.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
18 | |
12 | |
6 | |
6 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 |
Tue 07 Oct 2025 @ 10:00 AM (CEST)
Cloud Architect Series: AI-Powered API Security with CloudGuard WAFThu 09 Oct 2025 @ 10:00 AM (CEST)
CheckMates Live BeLux: Discover How to Stop Data Leaks in GenAI Tools: Live Demo You Can’t Miss!Thu 09 Oct 2025 @ 10:00 AM (CEST)
CheckMates Live BeLux: Discover How to Stop Data Leaks in GenAI Tools: Live Demo You Can’t Miss!Wed 22 Oct 2025 @ 11:00 AM (EDT)
Firewall Uptime, Reimagined: How AIOps Simplifies Operations and Prevents OutagesAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY