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

Unanswered

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

  				
Posted 
	3 months ago

					More
				  		
  Report
		
					CostlyOstrich36
				
					0

29 Views

0 Answers

3 months ago