Closed pschiffe closed 5 months ago
@pschiffe: Thanks for opening an issue, it is currently awaiting triage.
In the meantime, you can:
FYI we are planning 1.6.1
soon but for yourself, you can use the dev
container tag to get access to this fix.
Awesome, thank you for quick fix. My server is arm64, so I will have to wait for the proper release I think.
What happened?
I cannot connect from crowdsec to loki. Config:
Logs:
I don't have auth configured for internal docker network, but my loki requires
X-Scope-OrgID
header. In the loki logs I see:401
http code means there's noX-Scope-OrgID
header. From inside of the crowdsec container:In the source code here, it looks like the
requestHeader
is not set.Also, a little bit verbose logging would be useful as well, such as the http error status code.
cc @lperdereau
What did you expect to happen?
loki working
How can we reproduce it (as minimally and precisely as possible)?
see above
Anything else we need to know?
No response
Crowdsec version
OS version
Enabled collections and parsers
Acquisition config
Config show
Prometheus metrics
Related custom configs versions (if applicable) : notification plugins, custom scenarios, parsers etc.
No response