- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Checkpoint Operation is not allowed - Local reques...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Checkpoint Operation is not allowed - Local requests only
HI, All!
I'm getting the error above - "Checkpoint Operation is not allowed - Local requests only" when trying to execute Test Feed on R81.20.
Does anyone know what this means?
BTW, I think both the management and the firewall can reach the target IP on the specified port (I succeeded in telnet from both).
Thanks
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks!
I still got the same error, but after that modal was closed, I could test the feed and get a positive result!
So, I think this error should be ignored.
Again, many thanks!
(Should I mark this post as the solution?... 😊 )
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you send a screenshot?
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I know it may sound trivial, but make sure you are not possibly logged in as read-only?
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The session I'm in is shown as read-write. I saw a similar message in google, referring to read-only mode, but this is not the case here, imho
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you make sure whatever user you are logging in with has super user profile assigned to it, as per below?
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That's what it looks like - and thanks for your help!... (I also checked the modal you referenced)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There's only one TAC case that mentions this error and it has something to do with the username used (seems to be too short or a reserved word, not sure which from the notes).
I would have to see an unredacted screenshot of what you entered into the Network Feed to see if this applies or not.
Even so, I suggest a TAC case: https://help.checkpoint.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I edited the feed data, but I still see the same message.
And again - Thanks for your help. I guess this will eventually go to TAC...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sounds like the best idea.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you try this feed, see what you get?
Andy
https://rules.emergingthreats.net/fwrules/emerging-Block-IPs.txt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks!
I still got the same error, but after that modal was closed, I could test the feed and get a positive result!
So, I think this error should be ignored.
Again, many thanks!
(Should I mark this post as the solution?... 😊 )
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just did 🙂
