# Issues upgrading from 1.6.0.Beta10+9 to 2.3.0.beta6

**URL:** https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324
**Category:** Self-hosting
**Created:** [April 3, 2019, 9:59am UTC](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324 "2019-04-03T09:59:33Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![Ashwani\_K\_Goel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ashwani_k_goel/32/129382_2.png) [@Ashwani\_K\_Goel](https://meta.discourse.org/u/Ashwani_K_Goel)
#### Post date: [April 3, 2019, 9:59am UTC](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324/1 "2019-04-03T09:59:33Z")

</div>

Hi

I am trying to upgrade my discourse forum from 1.6.0.Beta10+9 to 2.3.0.beta6, using the “Click Here to Upgrade” option, inside the Admin panel

See this screen shot: [https://www.intecons.com/AMB%2067.png](https://www.intecons.com/AMB%2067.png)

However, after doing some stuff for a while, it just hangs up at “Building Assets”, see this screen shot: [https://www.intecons.com/AMB%2066.png](https://www.intecons.com/AMB%2066.png)

I am not a NGINX expert, just Apache

That’s why I am not trying to upgrade it using terminal window, but I have no idea now where to go from here

Any helps will be highly appreciated

Thanks

Ashwani

PS: Attaching the log which it has created so far. It’s here: [https://www.intecons.com/Discourse%20upgrade%20log.txt](https://www.intecons.com/Discourse%20upgrade%20log.txt)

---

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [April 3, 2019, 10:21am UTC](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324/2 "2019-04-03T10:21:31Z")

</div>

The error is probably happening before, we can’t see it in your screenshot.

---

<div class="post-metadata">

### Author: ![Ashwani\_K\_Goel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ashwani_k_goel/32/129382_2.png) [@Ashwani\_K\_Goel](https://meta.discourse.org/u/Ashwani_K_Goel)
#### Post date: [April 3, 2019, 10:33am UTC](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324/3 "2019-04-03T10:33:28Z")

</div>

Hi Joffery

Thanks for replying, that’s why I attached the whole log link too. It’s here: [https://www.intecons.com/Discourse upgrade log.txt](https://www.intecons.com/Discourse%20upgrade%20log.txt)

Hopefully this helps

---

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [April 3, 2019, 10:36am UTC](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324/4 "2019-04-03T10:36:37Z")

</div>

So your error is:

```plaintext
Sass::SyntaxError: Invalid CSS after "...le:none}:root{-": expected number or function, was "-blue:#007bff;-..."

```

Not sure it’s coming from Discourse, might be a plugin.

---

<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: [April 3, 2019, 1:38pm UTC](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324/5 "2019-04-03T13:38:10Z")

</div>

If you’re updating from 1.6 you’ll have to do a rebuild from the command line.

---

<div class="post-metadata">

### Author: ![Ashwani\_K\_Goel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ashwani_k_goel/32/129382_2.png) [@Ashwani\_K\_Goel](https://meta.discourse.org/u/Ashwani_K_Goel)
#### Post date: [April 3, 2019, 1:55pm UTC](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324/6 "2019-04-03T13:55:41Z")

</div>

Hi Jay

Thanks for the reply

But how will my data get transferred if I do a rebuild from command line

Sorry, I am a newbie

Can you give me some starting steps

---

<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: [April 3, 2019, 2:36pm UTC](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324/7 "2019-04-03T14:36:32Z")

</div>

```
 cd /var/discourse
  git pull
 ./launcher rebuild app
 ./launcher rebuild app 

```

You will not lose your data. I believe that you’ll need to rebuild twice because the first one will upgrade the database.

For $300 or year I’ll do command line upgrades when they are required. [Redirecting…](https://www.literatecomputing.com/automatic-rebuilds-when-they-are-needed/)

---

<div class="post-metadata">

### Author: ![Stranik](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stranik/32/85638_2.png) [@Stranik](https://meta.discourse.org/u/Stranik)
#### Post date: [April 3, 2019, 2:39pm UTC](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324/8 "2019-04-03T14:39:22Z")

</div>

Small addition. If you had an error through the admin interface, you will have a high probability of error through the console. In order not to risk it can be immediately disable all third-party plugins and make a rebuild.

> [@Manually update Discourse and Docker image to latest](https://meta.discourse.org/t/how-do-i-manually-update-discourse-and-docker-image-to-latest/23325):
>
> bookmark This guide provides step-by-step instructions for manually updating Discourse, the Docker container, and the Ubuntu operating system on a self-hosted setup. person_raising_hand Required user level: System Administrator warning SSH access to the server. If you self-host Discourse, you occasionally need to run a manual update via the command line to get the latest security releases and newest libraries. These updates are not picked up in admin/upgrade, which is why you’ll occa…

---

<div class="post-metadata">

### Author: ![Ashwani\_K\_Goel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ashwani_k_goel/32/129382_2.png) [@Ashwani\_K\_Goel](https://meta.discourse.org/u/Ashwani_K_Goel)
#### Post date: [April 4, 2019, 12:34am UTC](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324/9 "2019-04-04T00:34:32Z")

</div>

Hi Jay

I get this

ERROR: Docker version 1.8.2 not supported, please upgrade to at least 17.03.1, or recommended 17.06.2

When I try to upgrade via console

Any help?

You think you can take it further from here?

Here is the full log of what it shows: [https://www.intecons.com/result%20of%20upgrade%20through%20terminal.txt](https://www.intecons.com/result%20of%20upgrade%20through%20terminal.txt)

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [April 4, 2019, 4:45am UTC](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324/10 "2019-04-04T04:45:54Z")

</div>

How was this installed originally? What version of Ubuntu is this?

Assuming you have updated everything in apt and are running 16.+ then docker can usually be taken care of with:

```
wget -qO- https://get.docker.com/ | sh

```

---

<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: [April 4, 2019, 12:08pm UTC](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324/11 "2019-04-04T12:08:03Z")

</div>

If docker was installed from an old Ubuntu version it is best to

```
apt purge docker.io

```

(or widget docker it is) first. You can see what it is with

```
dpkg -l |grep docker

```
