Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coraza SPOA Error: "response id is empty" #182

Open
Mkiings opened this issue Feb 6, 2025 · 0 comments
Open

Coraza SPOA Error: "response id is empty" #182

Mkiings opened this issue Feb 6, 2025 · 0 comments

Comments

@Mkiings
Copy link

Mkiings commented Feb 6, 2025

Hi everyone,

I'm running Coraza SPOA on a HAProxy VM and encountering a recurring error in the logs:

root@haproxyvm:~/coraza-spoa# tail -f /var/log/coraza-spoa/coraza-agent.log
3:44PM PNC Error handling request error="response id is empty"
3:44PM PNC Error handling request error="response id is empty"
3:44PM PNC Error handling request error="response id is empty"
3:44PM PNC Error handling request error="response id is empty"
3:44PM PNC Error handling request error="response id is empty"
3:54PM PNC Error handling request error="response id is empty"
3:54PM PNC Error handling request error="response id is empty"
3:55PM PNC Error handling request error="response id is empty"
4:10PM PNC Error handling request error="response id is empty"
4:15PM PNC Error handling request error="response id is empty"

This error keeps appearing, and I suspect it might be related to SPOA's communication with HAProxy.

My setup:
HAProxy Version: version 2.8.13
Coraza-SPOA Version: Core version (v3.2.2)
OS: Debian 12 (Bookworm)
Deployment: Running Coraza-SPOA as a service on HAProxy VM
Configuration Details:
HAProxy and Coraza-SPOA are communicating over a Unix socket
No firewall rules blocking communication
HAProxy is properly configured with the SPOA settings
Steps I've Tried:

  • Checking permissions

  • Verifying HAProxy and SPOA configuration

  • Ensuring the Coraza agent process is running

Despite these, the issue persists.

Has anyone encountered this before? Any ideas on what could be causing it or how to debug further?

Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant