# Problèmes de mise à niveau de 1.6.0.Beta10+9 vers 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:** [Avril 3, 2019, 9:59 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:** 1
**Showing post:** 8

<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: [Avril 3, 2019, 2:39 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…

---

_[View the full topic](https://meta.discourse.org/t/issues-upgrading-from-1-6-0-beta10-9-to-2-3-0-beta6/113324)._
