Switching domain provider and also forum domain so better upgrade first… bad idea, forgot that 50% of my discourse upgrades fail :frowning: . Maybe a problem with “gem ‘mini_racer’” and found some too old distro/gcc comments but with 9 days before the domain expires I just decided to restore the ba…

if you are having trouble with mini-racer it’s likely your install of Ubuntu is too old. Take a look at this similar issue in Dev: [이미지] Chat not working after dev install Support @merefield @j.jaffeux Thanks for the help!! The root cause of this issue…

Hell yes, we are talking 16.04.3 LTS here. For now, I just want to go back to the previous version. Then, with enough time, I’ll check if it’s even possible to upgrade “easily” or if I finally after 10 years do a new Ubuntu from scratch and move stuff there. But remembering what ELSE I have done o…

[이미지] Peter Bäckgren: Hell yes, we are talking 16.04.3 LTS here. Wowzers, just move to a new server.

[이미지] Peter Bäckgren: But remembering what ELSE I have done over the years… uh oh. If you move to a new server using backup/restore, and keep the changes in app.yml then everything should move with it.

Yeah, but setting up a new server and considering whether to move the source control as well and whatever I have installed over the years to have in a 24/7 cloud droplet… Something I prefer to have at least a day to do. Which I don’t have now. Ok, for now I’m just restoring last nights droplet and …

[이미지] Peter Bäckgren: Seriously, if an upgrade fails there should be an automatic failsafe return to the previous state. With the standard install you can try just restarting the container.

When your os is 4 years past end of life you can’t expect any upgrades to work. Move to a new vm. It’s unlikely that there is anything on the old server you need. I don’t know what source control you might be talking about.

Yeah, a look in the mirror is in order :smiley: . But, it took me 2 years to upgrade all home instances to WIN11 (=always short on time). Finland is switching to HD only TV at the end of this month (someone actually doesn’t netflix everything = yes) and been working on that for months. Still have …

So just stay on the old version until you’re ready to upgrade. It’s actually almost easier to move to a new vm than to do the PostgreSQL 15 update anyway. Or just don’t upgrade anything and wait another for years. :wink:

Well, had to update app.yml because of the domain switch and did app rebuild instead of restart by mistake without taking a snapshot in Digital Ocean first. So kinda forced myself into upgrading right now :frowning: . Which eventually worked. Since I hit a few snags (laughs allowed) I’ll publish my…

업그레이드가 실패합니다 (다시 :) )

지원

merefield (Robert) 3월 1, 2025, 10:47오전 4

Wowzers, just move to a new server.

글		댓글	조회수
Determining whether my VPS needs any upgrades (generally) Support	20	773	3월 10, 2025
Upgrade to 3.3 is failing for me Self-hosting	22	519	10월 22, 2024
Old installation failing upgrade Self-hosting unsupported-install	7	259	10월 2, 2024
2.6.0 beta 3 update failed on disk and/or memory space Self-hosting server-resources	28	2854	9월 26, 2020
Failed upgrade from 2.9.0.beta14 to 3.1.0.beta Self-hosting	10	1268	1월 25, 2023

업그레이드가 실패합니다 (다시 :) )

Related topics