Request Failed with status code 400: Cases #9039
Replies: 1 comment 5 replies
-
Since you're still on version 2.3.110 which is several months old at this point, I'd recommend starting with upgrading to the latest 2.3.181 version: |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, I had a previous discussion open for this issue, but it was never resolved. #7587
I would really like to get this working on my deployment of security onion. Its currently on version 2.3.110 Below is the error that shows up in /opt/so/log/sensoroni/sensoroni-server.log when trying to escalate an alert.
![image](https://user-images.githubusercontent.com/27656903/199108682-fca1ec34-2723-4d79-939b-73857a9ff518.png)
Please let me know if anymore information is needed
Security Onion version: 2.3.110
On Prem and internet access deployment
Installed from an SO
1 master node
Are you experiencing issues monitoring network traffic? If so, are you sniffing from a tap or span port and what is the traffic volume? No
Does so-status show all services running? Yes
Do you get any failures when you run sudo salt-call state.highstate? No
Does the SOC Grid page show any failures? No
When I input the following query: so-elasticsearch-query "so-case/_mappings" | jq, I noticed the mapping is incorrect
I tried reindexing so-case* using the experimental script but it didnt do anything. Any help is much appreciated
Beta Was this translation helpful? Give feedback.
All reactions