CRITICAL:pymisp:Unknown error: the response is not in JSON
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 491
- Forks
- 290
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 3
Description
Hello everyone, I hope you are well, I would like to tell you that I am new here and I am doing a laboratory for my university, I installed Misp and I have tried to link it to OpenCTI but it gives me the following error
ERROR:root:Error fetching misp event again: Error code 500:
{"name":"An Internal Error Has Occurred.","message":"An Internal Error Has Occurred.","url":"/events/restSearch"}
INFO:root:Connector successfully run (0 events have been processed), storing state (last_run=2023-01-06T05:30:18.816024+00:00, last_event=2000-01-01T00:00:00+00:00, last_event_timestamp=946684800)
I would be very grateful if you could help me
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported OpenCTI-to-MISP connector logs and the MISP /events/restSearch endpoint response. Check the connector and MISP configuration involved in the failing request, then reproduce the 500 response. Done means the request returns the expected JSON and the connector processes events instead of recording zero events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100