Miss_B

In addition to what Marc mentioned above, it may be a good idea to contact the developers first to confirm whether or not their plugins have been updated to work on v5 if they are a necessity for your community after upgrading.

If you don't plan to use them in the future by way of upgrading them, personally I would uninstall them before the upgrade, but make sure to make a backup of their stuff that they have added to the database. Otherwise simply disable them prior to the upgrade.
My advice, if I may, is to delete them prior to the upgrade.
You can upgrade them from the Applications section of your Admin Panel, but only if their authors have released their Ips 5 versions.

Okay, thank you! I have updated these details and I believe they are correct now. Please let me know if you are able to access successfully!

I have been strongly considering this. My host used to be amazing, completely above and beyond, until they were aquired by another company a little over a year ago, and their support has really gone down the drain since then. Budget is definitely concern for me when it comes to switching hosts, but I'm also aware that you get what you pay for!

Thank you, everything worked out

Do you mean data as in posts, topics, members etc? The answer is no. All that stuff is preserved in the database. As long as you make a backup of it regularly nothing will be lost.

I disagree. XenFor is no way better than Ips. XenForo is a dead project and the support that they offer over there leaves a lot to be desired imo.
That said, if you can't always ask people for help then you must learn how to deal with the technical issues yourself. The thing is that you caused this issue yourself by upgrading to a beta version. Add when you run into issues, which is to be expected with betas, on any platform and not only with Ips, instead of asking for support in a correct/right way you start immediately with that going to XenForo nonsense. Good luck with it. See how you would like to be yelled at by their staff whenever you ask for support on their forum.

I disagree. XenFor is no way better than Ips. XenForo is a dead project and the support that they offer over there leaves a lot to be desired imo.
That said, if you can't always ask people for help then you must learn how to deal with the technical issues yourself. The thing is that you caused this issue yourself by upgrading to a beta version. Add when you run into issues, which is to be expected with betas, on any platform and not only with Ips, instead of asking for support in a correct/right way you start immediately with that going to XenForo nonsense. Good luck with it. See how you would like to be yelled at by their staff whenever you ask for support on their forum.

I disagree. XenFor is no way better than Ips. XenForo is a dead project and the support that they offer over there leaves a lot to be desired imo.
That said, if you can't always ask people for help then you must learn how to deal with the technical issues yourself. The thing is that you caused this issue yourself by upgrading to a beta version. Add when you run into issues, which is to be expected with betas, on any platform and not only with Ips, instead of asking for support in a correct/right way you start immediately with that going to XenForo nonsense. Good luck with it. See how you would like to be yelled at by their staff whenever you ask for support on their forum.

I disagree. XenFor is no way better than Ips. XenForo is a dead project and the support that they offer over there leaves a lot to be desired imo.
That said, if you can't always ask people for help then you must learn how to deal with the technical issues yourself. The thing is that you caused this issue yourself by upgrading to a beta version. Add when you run into issues, which is to be expected with betas, on any platform and not only with Ips, instead of asking for support in a correct/right way you start immediately with that going to XenForo nonsense. Good luck with it. See how you would like to be yelled at by their staff whenever you ask for support on their forum.

I'll second your opinion. A lot of the time they act like it's a bother to answer support questions (Not everyone on staff there but certain ones) and they talk to you like you should know every line of code in the software. It's like they forget who matters and that's the customer. There's only two forum software support forums that I've dealt with that actually treat you like you matter and those two support forums are here and Flarum. I'm sure there are others but I've truly ever only dealt with 3.
That's great you've had a good experience with xenForo there are some people that have a good experience but it's becoming more and more common that people have a bad experience with it. At the end of the day you just have to use what you're most comfortable with. I can say from having used xenForo and IC is that xenForo feels old and dated like how vBulletin feels. Whereas IC feels modern and less like a forum but more like a community.

I disagree. XenFor is no way better than Ips. XenForo is a dead project and the support that they offer over there leaves a lot to be desired imo.
That said, if you can't always ask people for help then you must learn how to deal with the technical issues yourself. The thing is that you caused this issue yourself by upgrading to a beta version. Add when you run into issues, which is to be expected with betas, on any platform and not only with Ips, instead of asking for support in a correct/right way you start immediately with that going to XenForo nonsense. Good luck with it. See how you would like to be yelled at by their staff whenever you ask for support on their forum.

But you said you PAID someone $10 on Fiverr for help. And then you did not know your own password?
Well, if you change your mind and want us to help you just post in support. We're happy to help... for free.

What error message(s) are you getting? It would help if you posted the exact error messages. Regarding the 500 errors, they are almost always host/server related.
One a side note, imo it's always best to wait until a version becomes stable and then upgrade to it rather than upgrading to a beta version as betas are likely to have bugs and throw errors.

The only way to fix this would be to fix the relevant code. Personally I think it's better to wait until the bug has been officially fixed.

This is probably irrelevant here, as we know he wrong PHP version was being used which would cause errors, and as such the upgrader cant have been run either

Going back to the beginning here, it sounds like you need to do the following before touching recovery mode. Recovery will not work, because you have uploaded files, changed PHP version etc, and havent yet, as far as I can tell, upgraded
From an older version, you would need to
Back up your site
Update your PHP version, which it seems you have, however you need to update to PHP 8.1 not 8.0
Once thats done, use the requirement checker to ensure everything is then met - https://invisioncommunity.com/files/file/7046-invision-community-requirements-checker/
Once thats done, upload the latest files for version 4 (NOT version 5. You need to have upgraded to the latest version 4 first)
Upgrade from /admin/upgrade
If you are then looking to get to version 5, you can of course do this, and you would do the last 2 item again, but this time upload version 5. Again after backing up

Not that I know of.
Assuming you are on the 4.7.x series, check out the Manual Upgrading section of the following guide:

Not that I know of.
Assuming you are on the 4.7.x series, check out the Manual Upgrading section of the following guide:

This is indeed a bug, which has been fixed for the next release

This will require a custom app imo as it can't be done with the out of the box features.

This will require a custom app imo as it can't be done with the out of the box features.

Switching to mysql solved the problem. Elasticsearch seems to be the problem marking the read posts.

This has been resolved for you. Please see your ticket.

This is an access log, you'll want to get the error log to find the actual error.

You have an internal server error being caused by the 3rd party application 'videobox', based on that message.