Miso

Sure. Re-index is done, and the user in question is "kdokoza". Once logged in as that user, on Elasticsearch it showed tons of feeds under "Content I Follow", in mySQL it doesn't show any for some reason, just to mention again.

Ok, reindexing is at 42%. Should be done within the hour or so. Did you want me to post the username here or PM you or...? I don't mind either.

Same here. Actually prefer MariaDB for speed and faster updates + error logging plugin...

Litespeed is not on the official support list, but it works just fine, or rather waaaay better than Apache for some of us. If I was you I'd only consider keeping it if the extra $10-15/month isn't an issue for you for that Litespeed license.

Well, let's try this - can we troubleshoot this issue with mySQL not indexing/showing some of the user accounts' "My Feeds -> Content I Follow" and shows them empty, even though they should have content (as shown once we switch over to Elasticsearch and from testing with known users who follow tons of specific feeds on the forum)? That way we won't have to deal with Elasticsearch at all - and I'd rather not deal with something we aren't familiar with using or configuring and something that will be bogging the server down anyway. MySQL has been working out great and the search results are instant, really... except for this issue of missing feed content for certain users.

Ok, good to know. We'll troubleshoot those one by one then, to see which one is the offending one. That's somehow the effect of Elasticsearch running the indexing in the background... not sure how to deal with that - do you have any suggestions on what sort of settings to use for Elasticsearch to improve that? And the actual reason why we are trying to use Elasticsearch is because when we use MySQL engine for search index, some of the user accounts have their "My Feeds -> Content I Follow" feeds empty, even though there should be quite a few feeds and content in there, and we can't figure out why this is happening. It's not likely that mySQL index is skipping the exact same users every time we run it... when we switch to Elasticsearch that content shows up just fine for specific users, but in mySQL it doesn't. But then again, if Elasticsearch indexing will be this straining on the server...

Updated the FTP access details. Forum admin details shouldn't have changed at all, so those should be good to go.

Ok, so how do we go about it and where do we go from here?

Ok, so if I flip it over to 8.1 and you assume that we're on 8.1 from here on, can you help with this issue then?

Well, we've gone through half a dozen upgrades just fine on 8.3, without a single issue, and haven't seen anything or haven't had anything reported over the last few months on 8.3 from users or admins, so I'll assume it's working just fine until proven otherwise and until we see some sort of issues with the board on 8.3. You might say it's not working 100%, but unless you can point out some specifics that aren't working properly on 8.3 I'll stick with our assumption and 8.3, thank you very much. Anyway, back to this Elasticsearch issue instead... which, I mentioned, happens in exact same way on PHP 8.1 and 8.3, so it's not PHP related, that's for sure.

Yes, literally installed the latest v7 (7.17 I believe?) yesterday from the 7.* repo. https://prnt.sc/KMY_dtm1EaZm

As I noted in the original post, both 8.1 and 8.3 produced the same result/error, so I highly doubt the PHP version has anything to do with this problem. What I do suspect is that it has something to do with the Invision Board code, as per some other posts on this topic where Invision team has admitted that similar errors were caused by bugs in the current Invision code, and they fixed them at some point. I have a feeling this is one of those bugs that they didn't foresee or anticipate either... p.s. Even though 8.3 is not "officially" supported, Invision Board works perfectly fine on it and we haven't seen ANY issues on 8.3, so there's that.

Ok, here's what's happening on our setup (Elasticsearch 7, MariaDB 11.4, PHP 8.3 while testing on 8.1 and getting the same results)... on the front-end we are getting this error for any search conducted on the forum: TypeError: array_map(): Argument #2 ($array) must be of type array, null given (0) #0 /home/domain/public_html/forums/system/Content/Search/Elastic/Query.php(1315): array_map(Object(Closure), NULL) #1 /home/domain/public_html/forums/applications/core/modules/front/search/search.php(760): IPS\Content\Search\Elastic\_Query->search('digital', NULL, 17, 'or') #2 /home/domain/public_html/forums/applications/core/modules/front/search/search.php(126): IPS\core\modules\front\search\_search->_results() #3 /home/domain/public_html/forums/system/Dispatcher/Controller.php(118): IPS\core\modules\front\search\_search->manage() #4 /home/domain/public_html/forums/system/Dispatcher/Dispatcher.php(153): IPS\Dispatcher\_Controller->execute() #5 /home/domain/public_html/forums/index.php(13): IPS\_Dispatcher->run() #6 {main} and in the backend it shows that + the backtrace: #0 /home/domain/public_html/forums/init.php(1049): IPS\_Log::log('TypeError: arra...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(TypeError)) #2 {main} Any idea what's happening here and how to fix this?