# My install is 16,359 commits behind! Advice?

**URL:** https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327
**Category:** Self-hosting
**Created:** [February 25, 2025, 6:53am UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327 "2025-02-25T06:53:27Z")
**Posts on this page:** 16
**Page:** 1

<div class="post-metadata">

### Author: ![trusktr](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/trusktr/32/116841_2.png) [@trusktr](https://meta.discourse.org/u/trusktr)
#### Post date: [February 25, 2025, 6:53am UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/1 "2025-02-25T06:53:27Z")

</div>

And the `Upgrade` button is grayed out:

 ![Screenshot 2025-02-24 at 10.33.43 PM](https://global.discourse-cdn.com/meta/original/4X/1/d/6/1d672b2411c77935ed533c6f6e8dfb65c69446d2.png)

Any advice on how to “Upgrade”?

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [February 25, 2025, 7:19am UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/2 "2025-02-25T07:19:42Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [February 25, 2025, 7:22am UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/3 "2025-02-25T07:22:01Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![trusktr](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/trusktr/32/116841_2.png) [@trusktr](https://meta.discourse.org/u/trusktr)
#### Post date: [February 25, 2025, 7:25am UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/4 "2025-02-25T07:25:00Z")

</div>

Thanks. Will give that a try when I circle back.

---

<div class="post-metadata">

### Author: ![trusktr](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/trusktr/32/116841_2.png) [@trusktr](https://meta.discourse.org/u/trusktr)
#### Post date: [February 25, 2025, 7:25am UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/5 "2025-02-25T07:25:22Z")

</div>

Yeah, not sure what the “an hour ago” is about. It’s been a long time!

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [February 25, 2025, 7:26am UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/6 "2025-02-25T07:26:09Z")

</div>

> [@Jagster](#):
>
> Old when last updates are an hour and a week ago?

That’s when the repos were last updated. Not the site.

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [February 25, 2025, 7:28am UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/7 "2025-02-25T07:28:22Z")

</div>

Yeah, I realize that when I checked out mine. Everyday something new (well, I don’t use UI updating practically ever, though)

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [February 25, 2025, 5:39pm UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/8 "2025-02-25T17:39:46Z")

</div>

And see also [PostgreSQL 15 update](https://meta.discourse.org/t/postgresql-15-update/349515).

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](https://meta.discourse.org/t/move-a-discourse-site-to-another-vps-with-rsync/43812), 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.

---

<div class="post-metadata">

### Author: ![trusktr](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/trusktr/32/116841_2.png) [@trusktr](https://meta.discourse.org/u/trusktr)
#### Post date: [March 16, 2025, 7:13pm UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/9 "2025-03-16T19:13:40Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![trusktr](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/trusktr/32/116841_2.png) [@trusktr](https://meta.discourse.org/u/trusktr)
#### Post date: [March 16, 2025, 7:50pm UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/10 "2025-03-16T19:50:43Z")

</div>

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

```plaintext
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…

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 16, 2025, 10:04pm UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/11 "2025-03-16T22:04:55Z")

</div>

> [@trusktr](#):
>
> I don’t remember if these configs were required.

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

---

<div class="post-metadata">

### Author: ![trusktr](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/trusktr/32/116841_2.png) [@trusktr](https://meta.discourse.org/u/trusktr)
#### Post date: [March 17, 2025, 1:11am UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/13 "2025-03-17T01:11:09Z")

</div>

I currently have this in my app.yml from years ago:

```plaintext
  # 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:

> [@Upgrade / Rebuilds Fail due to MaxMind DB EOL](https://meta.discourse.org/t/upgrade-rebuilds-fail-due-to-maxmind-db-eol/137387):
>
> Guys, Hope somebody can help here. Ive not had a problem for over 12 months with upgrades to my forum that is running in a docker container on EC2 Ive tried: launcher cleanup but no issues with disk space latest git pull multiple app rebuilds Even tried a discourse-setup and was going to try a DB restore frowningServer reboot apt-get update; apt-get upgrade Here is the tail of the log Done compressing all JS files : 88.88 secs rake aborted! SocketError: Failed to open TCP connection 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?

---

<div class="post-metadata">

### Author: ![Arkshine](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/arkshine/32/298682_2.png) [@Arkshine](https://meta.discourse.org/u/Arkshine)
#### Post date: [March 17, 2025, 1:49am UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/14 "2025-03-17T01:49:37Z")

</div>

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:

```plaintext
./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.

---

<div class="post-metadata">

### Author: ![trusktr](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/trusktr/32/116841_2.png) [@trusktr](https://meta.discourse.org/u/trusktr)
#### Post date: [March 17, 2025, 9:09am UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/15 "2025-03-17T09:09:20Z")

</div>

* * *

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:

 ![Screenshot 2025-03-17 at 2.08.17 AM](https://global.discourse-cdn.com/meta/original/4X/c/2/7/c27edf02b912114c1a475890e64dc85984edaab9.png)

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](https://meta.discourse.org/t/restore-a-backup-from-the-command-line/108034).

# Looks like it worked!! 🥳

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 18, 2025, 11:39pm UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/16 "2025-03-18T23:39:36Z")

</div>

You did it!

If you need to do it again one day, you might want to [Restore a backup from the command line](https://meta.discourse.org/t/restore-a-backup-from-the-command-line/108034)

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.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [April 17, 2025, 11:40pm UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/17 "2025-04-17T23:40:31Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
