# Trouble upgrading from 3.3.0.beta1 to 3.3.0.beta6
**URL:** https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376
**Category:** Self-hosting
**Created:** [August 6, 2024, 2:17pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376 "2024-08-06T14:17:29Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@kf\_stbrst](https://meta.discourse.org/u/kf_stbrst)
#### Post date: [August 6, 2024, 2:17pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/1 "2024-08-06T14:17:30Z")
Hi all - we’re having trouble upgrading our Discourse Forum from 3.3.0.beta1 to 3.3.0.beta6.
We followed the instructions in the admin panel:
```plaintext
cd /var/discourse
git pull
./launcher rebuild app
```
We also upgraded other packages that needed so. Things seemed to have been successful, but it’s still showing us 3.3.0.beta1 in our admin panel.
We have stopped and refreshed the docker container as well.
Also to note, we are running on Amazon Linux 2, not Ubuntu.
My initial thoughts are possibly around the `git pull` command? Perhaps we’re not grabbing the correct branch?
Any help or additional insight would be greatly appreciated, as we’d love to upgrade so that we no longer have the “A critical update is available” message.
Thank you.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 6, 2024, 2:41pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/2 "2024-08-06T14:41:43Z")
What happens if you view source? Do you get the right version then?
---
### Author:  [@Firepup650](https://meta.discourse.org/u/Firepup650)
#### Post date: [August 7, 2024, 1:11am UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/3 "2024-08-07T01:11:23Z")
> [@kf\_stbrst](#):
>
> My initial thoughts are possibly around the `git pull` command
You shouldn’t need to do a `git pull`, the rebuild usually does that itself doesn’t it?
---
### Author:  [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [August 7, 2024, 4:43pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/4 "2024-08-07T16:43:58Z")
You don’t usually need the git pull, but what it does is make sure the launcher script is up to date. So it’s a good idea.
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [August 7, 2024, 5:24pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/5 "2024-08-07T17:24:19Z")
`./launcher rebuild app` does it everytime, first before anything else, doesn`t it?
---
### Author:  [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [August 7, 2024, 5:28pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/6 "2024-08-07T17:28:04Z")
In that case you’d be running the existing launcher script. Once or twice, this has made a difference. It’s not a script which changes often, I think.
---
### Author:  [@keith2](https://meta.discourse.org/u/keith2)
#### Post date: [August 8, 2024, 3:52pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/7 "2024-08-08T15:52:25Z")
I’m running into a similar problem going from 3.2.0.beta1-dev to 3.3.0.beta6. It’s telling me there’s a new version, but when I click upgrade the console doesn’t show anything happening.
If I ssh into the box and perform a `git pull` it says `Already up to date`.
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [August 8, 2024, 3:55pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/8 "2024-08-08T15:55:03Z")
AFAIK pure `git pull` doesn`t do anything for that. It is for launcher.
---
### Author:  [@keith2](https://meta.discourse.org/u/keith2)
#### Post date: [August 8, 2024, 4:02pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/9 "2024-08-08T16:02:07Z")
ok, well I’ve also performed a `./launcher rebuild app` and still see the admin telling me that there’s a new version.
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [August 8, 2024, 4:07pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/10 "2024-08-08T16:07:54Z")
Yeah, but that is different thing than `git pull`.
Could it come from this somehow?
> [@Celebrating Discourse release 3.3](https://meta.discourse.org/t/celebrating-discourse-release-3-3/319189/6):
>
> This was bumped/tagged by mistake. We can’t easily remove the commit, but the tag has now been removed. v3.3.0.beta5 was the final beta version of 3.3, and is identical to 3.3.0 stable.
---
### Author:  [@keith2](https://meta.discourse.org/u/keith2)
#### Post date: [August 8, 2024, 4:10pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/11 "2024-08-08T16:10:03Z")
I’m still on 3.2.0.beta1-dev though. Why am I not able to upgrade to 3.3.0?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 8, 2024, 4:15pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/12 "2024-08-08T16:15:55Z")
Can you share your site url? If you view source on your site, what version do you see there?
---
### Author:  [@keith2](https://meta.discourse.org/u/keith2)
#### Post date: [August 8, 2024, 4:17pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/13 "2024-08-08T16:17:06Z")
hmm, maybe it’s due to this lets encrypt issue? I think I saw this on another app I’ve worked on that uses Ubuntu.
---
### Author:  [@keith2](https://meta.discourse.org/u/keith2)
#### Post date: [August 8, 2024, 4:18pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/14 "2024-08-08T16:18:56Z")
> [@pfaffman](#):
>
> If you view source on your site, what version do you see there?
``
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 8, 2024, 4:24pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/15 "2024-08-08T16:24:36Z")
> [@keith2](#):
>
> maybe it’s due to this lets encrypt issue?
It could be, but I doubt it. Unless. . .
You see no errors when you rebuild and it starts the new container? Or do you do a `./launcher start app` after it fails (and you didn’t notice that it failed)?
What does
```plaintext
docker ps
```
show? When was the current container created and started?
---
### Author:  [@keith2](https://meta.discourse.org/u/keith2)
#### Post date: [August 8, 2024, 4:57pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/16 "2024-08-08T16:57:34Z")
Opening all ports during cmd line rebuild allowed the letsencrypt process to run.
If I view source it shows 3.2.0.beta1-dev
If I look at the Upgrade page it still shows that I’m not on the latest version.
Should `./launcher rebuild app` pull the latest version?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 8, 2024, 4:59pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/17 "2024-08-08T16:59:05Z")
> [@keith2](#):
>
> Opening all ports during cmd line rebuild allowed the letsencrypt process to run.
You have to keep ports 80 and 443 open.
> [@keith2](#):
>
> Should `./launcher rebuild app` pull the latest version?
Yes.
> [@pfaffman](#):
>
> What does
>
> ```plaintext
> docker ps
>
> ```
>
> show? When was the current container created and started?
---
### Author:  [@keith2](https://meta.discourse.org/u/keith2)
#### Post date: [August 8, 2024, 5:00pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/18 "2024-08-08T17:00:26Z")
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 8, 2024, 5:07pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/19 "2024-08-08T17:07:19Z")
Unless you changed the `version: tests-passed` to something else. I’m stumped.
---
### Author:  [@keith2](https://meta.discourse.org/u/keith2)
#### Post date: [August 8, 2024, 5:14pm UTC](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376/20 "2024-08-08T17:14:04Z")
I haven’t changed anything. I don’t know enough about how Discourse is built to do anything other than the default install steps. 🙂
Not sure if this is what you’re talking about in the logs. I do see it showing `new tag` up till `v3.3.0.beta6`
[Next page](https://meta.discourse.org/t/trouble-upgrading-from-3-3-0-beta1-to-3-3-0-beta6/320376.md?page=2)