And the Upgrade button is grayed out:
Any advice on how to “Upgrade”?
2 Likes
Perform a command line upgrade.
But you are so very behind I would make sure you have a backup first and you might even consider deploying to a new server completely and use one of your backups to restore.
Once backed up you could try:
./launcher cleanup app then
./launcher rebuild app
But you might find your OS is too old and your docker version is too old. But give it a try.
5 Likes
Old when last updates are an hour and a week ago?
Edit: my view is different, BTW. But that update time doesn’t tell when all of those are updated last time to a forum, but when that list is kind of updated? If so, then OP should upgrade asap via console.
Thanks. Will give that a try when I circle back.
Yeah, not sure what the “an hour ago” is about. It’s been a long time!
That’s when the repos were last updated. Not the site.
3 Likes
Yeah, I realize that when I checked out mine. Everyday something new (well, I don’t use UI updating practically ever, though)
2 Likes
And see also PostgreSQL 15 update.
Was it 4 years ago that you last upgraded?
Your OS is likely out of date too, so I’d probably recommend that you get a new VM and Move a Discourse site to another VPS with rsync, perhaps excluding postgres_* , and then restoring a backup, that way you avoid the database upgrade and instead just restore your data and it’ll get migrated when you restore it.
It’s simpler, and if anything goes wrong, your existing site can keep limping along.
1 Like
Ok getting started. I made a backup, but I can’t download through the UI, it says it sent an email but the server is not sending emails currently.
I got in via SSH and see it is Ubuntu 14.
I think the best bet may be to make a new deployment of latest Discourse on latest OS, and then upload the backup (after I first get the backup via SSH).
This will automatically migrate the DB once I import it right?
1 Like
The commit I’m on is 46d899f9c10ebc0d44ced97d6f724dff295e7741.
And I’ve added a containers/app.yml file (I don’t remember why), for example with stuff like
env:
DISCOURSE_HOSTNAME: 'lume.community'
LETSENCRYPT_ACCOUNT_EMAIL: 'joe@trusktr.io'
I don’t remember if these configs were required. Is it required? The ideal would be I simply start a new Discourse instance, upload a DB, and be on my way.
Gonna try making the new instance now…
4 Likes
The hostname is. The let’s encrypt won’t matter soon.
Restoring your old database to the new site should Just Work. That’s the way I would do it
I currently have this in my app.yml from years ago:
# TODO (joe) remove this line once Discourse fixes the associated problem
# See https://meta.discourse.org/t/upgrade-rebuilds-fail-due-to-maxmind-db-eol/137387/2
DISCOURSE_REFRESH_MAXMIND_DB_DURING_PRECOMPILE_DAYS: 30
Linking to:
Can I delete that with the new instance? Or do I need to do something? I’m assuming that’s been ironed out a long time ago, and I can avoid including this setting in app.yml?
1 Like
Several fixes were made last year related to MaxMind, and I believe it should be safe now. I have not seen any topics for months mentioning an issue with it.
You can test downloading manually with a rake command:
./launcher enter app
rake maxminddb:get
exit
(post deleted by author)
You did not have to delete, I think it’s always useful for others to see a solution associated to an issue.
4 Likes
I am now at this screen on a brand new install, wondering how do I import the DB from the old instance before doing anything:
I’m guessing to Register, then import in the UI, and that maybe I should avoid registering with the email address of my admin account in the DB I will import so it doesn’t conflict.
Gonna try it. I can always start over.
EDIT: Ah, well, it only allows registering with the admin email I specified during setup. Let’s see what happens.
EDIT: I’ll have to circle back, as it is not sending emails. Mailgun seems to have blocked my account “due to a potential compromise”, which I need to get sorted.
EDIT: I bypassed the broken email by importing the backup via the command line.
Looks like it worked!! 
4 Likes
You did it!
If you need to do it again one day, you might want to Restore a backup from the command line
If you have the backups on s3 and put those settings in your yml file, you don’t even have to move the backup file yourself.
3 Likes