# Help after updating from ssh site goes down

**URL:** <https://meta.discourse.org/t/help-after-updating-from-ssh-site-goes-down/216499>\
**Category:** Self-hosting\
**Created:** [January 30, 2022, 5:16pm UTC](https://meta.discourse.org/t/help-after-updating-from-ssh-site-goes-down/216499 "2022-01-30T17:16:07Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![kynic](https://avatars.discourse-cdn.com/v4/letter/k/b487fb/32.png) [@kynic](https://meta.discourse.org/u/kynic)\
**Post date:** [January 30, 2022, 5:16pm UTC](https://meta.discourse.org/t/help-after-updating-from-ssh-site-goes-down/216499/1 "2022-01-30T17:16:07Z")

</div>

I followed this and updated discourse via ssh

> [@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…

After doing this site goes down pls help me I in stress pls help

it shows this when I try to start launcher

```plaintext
./launcher start app
x86_64 arch detected.

starting up existing container
+ /usr/bin/docker start app
Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: sethostname: invalid argument: unknown
Error: failed to start containers: app

```

---

_[View the full topic](https://meta.discourse.org/t/help-after-updating-from-ssh-site-goes-down/216499)._