Unable to reach Elastic Search from the Logs Data Plateform

Domains and Hosting
1

Hello,

Yesterday I have done some Curl requests to the "https://gra1.logs.ovh.com:9200/ldp-logs/message" endpoint and everything went well.

Today, I launch the exact same request and it fails with the below response :
{
"error": {
"root_cause": [
{
"type": "auth_exception",
"reason": "Couldn't authenticate user logs-nb-xxxxx against any of the backends."
}
],
"type": "auth_exception",
"reason": "Couldn't authenticate user logs-nb-xxxx against any of the backends.",
"caused_by": {
"type": "multi_auth_exception",
"reason": null
}
},
"status": 403
}

The problem seems very similar to this one : https://community.ovhcloud.com/t/32992

The GrayLog plateform is still up and available, but the Elastic Search API button (https://gra1.logs.ovh.com:9200/_cluster/health?pretty=true) returns to me the same error response.

Is there something Down?

My Curl Request :
`curl -H 'Content-Type: application/json' -u 'logs-nb-xxxx:abcdef12345' -XPOST https://gra1.logs.ovh.com:9200/ldp-logs/message -d '{ "X-OVH-TOKEN" : "xxxxxx-xxxxx-xxxx-xxxx-xxxxxxx" , "test_field" : "Hello" , "short_message" : "Hello World", "host" : "OVHcloud_doc" }'`

Thanks

2

Hello @DamienF12,

Thanks for your interest in Logs Data Platform.

Probes and health check do not report us any anomalies.

According our audit logs, it looks that you reset your password 16 hours ago. Can you confirm that the new password is working on Graylog UI located here (logout if already signed in): https://gra1.logs.ovh.com ? but not with curl.

Thanks.

3

Hello Pierre,

Yes I have changed the password yesterday and the new password is working well on Graylog UI (I log out and login with the new password).
Before raising the ticket, I've double-checked the Curl request using the old password and the new one. It's always the same error Response.
Also, the Curl request worked yesterday after the password has been changed (I can see it in the history of my shell console). This is why I supposed that the issue is not on my side, but I'm maybe wrong.

Thanks,