Unanswered
Rolling Back To 1.15.0 Seemed To Fix The Error For Now. Is There Something One Should Be Aware Of Between Server Versions 1.15 And 1.16 Related To Versions Of The
I think its possible there was an upgrade in Elastic, I'd suggest going over the release notes to see if this happened with the server
19 Views
0
Answers
2 months ago
2 months ago