Indexing errors result in wrong error message "The connection to the server could not be established."

Since this happens on generic error code 0. I've made the error message even more generic. Now when something weird with the code happens, it will say Search API Meilisearch error(s) occurred. Please check the logs for more information. more details are always logged in dblogs.

This will also have to be merged with 2.x.

So is most likely also something that Meilisearch itself should provide better messages and error codes for.
For the situations where we do get code 0 back, this is definitely a better error message.

I wonder whether there might be explicit cases of an unreachable server which the old message should still be shown for.
But on the other hand, looking into the logs is never a bad idea, so setting this RTBC.

Commited to 1.x, needs porting to 2.x

Ported to 2.x as well, thanks.

Automatically closed - issue fixed for 2 weeks with no activity.