-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade problems when upgrading from YNH 11>12 and Debian Bookworm #469
Comments
You should try to upgrade peertube after the upgrade from YNH11 to 12 |
Hmm, too late for that now. 😞 Already upgraded Peertube to v7. Anything else to try? |
You can do an upgrade of peertube to the same version after moving to YNH12 |
Right, but I can't (easily?) revert to v6 of Peertube, now that I already upgraded to v7. |
you still have 500 errors ? |
I did the following:
So I don't have a way back to PT 6 unfortunately. No 500 errors (I rolled back to YNH 11, which fixed it), but I'm going to be stuck at YNH 11.3 until I figure out how to resolve it. To be fair, the notes DO say that it might not be stable yet, so perhaps I should just wait on the upgrade for a while? |
I think you should try: |
I recently attempted to upgrade my system from YNH 11.2 to 11.3, and Peertube 6.x to 7.0. That operation succeeded without any trouble, however YNH then also alerted to a pending migration from YNH 11>12 and Debian Bookworm. Before upgrading, YNH gave the following warning:
After running the migration, the base site still loads, but then just about everything else gives 500 errors in the background (favicon, plugins, videos loading, etc). Basically, nothing on the site works. I rolled back the upgrade with a snapshot, and have everything working, but need to figure out what is causing this upgrade to give these 500 errors. Initial thought is that Metronome (xmpp) might be part of the issue, but would appreciate other thoughts.
The text was updated successfully, but these errors were encountered: