# Upgrade without SSH access
**URL:** https://meta.discourse.org/t/upgrade-without-ssh-access/122815
**Category:** Support
**Created:** [July 12, 2019, 5:01pm UTC](https://meta.discourse.org/t/upgrade-without-ssh-access/122815 "2019-07-12T17:01:17Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [July 12, 2019, 5:01pm UTC](https://meta.discourse.org/t/upgrade-without-ssh-access/122815/1 "2019-07-12T17:01:17Z")
I have an instance with `docker_discourse` stuck at `1b83bcc`. The [next commit](https://github.com/discourse/docker_manager/commit/39ea15921c5f5b9d25756a9ae05dffcf3aaab698), in my reading, requires running `./launcher rebuild app` from the SSH console. I am tempted to upgrade to the latest version from the admin UI and see what happens, but I do not have SSH access to the server, so I expect this upgrade to leave the site with a message to run the command line.
**Am I right, and I need SSH access, or can I proceed and upgrade via the admin?**
My understanding is that the `expected_version` will trigger a requirement to rebuild the Docker container from scratch to avoid dangling images.
Thank you for your help.
---
### Author:  [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [July 12, 2019, 5:06pm UTC](https://meta.discourse.org/t/upgrade-without-ssh-access/122815/2 "2019-07-12T17:06:48Z")
Not having SSH to the server is an unsupported way to maintain Discourse as you will need to update the base image from time to time. I highly recommend you figure out how to get SSH access to the forums you maintain.
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [July 12, 2019, 5:12pm UTC](https://meta.discourse.org/t/upgrade-without-ssh-access/122815/3 "2019-07-12T17:12:34Z")
I know, this is a special case of the sysadmin disappearing. So I guess you solved it. Thanks for the confirmation.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [July 12, 2019, 5:30pm UTC](https://meta.discourse.org/t/upgrade-without-ssh-access/122815/4 "2019-07-12T17:30:46Z")
If the sysadmin is _really_ gone you can (and probably should) take a backup, set up a new server, and restore the data there.
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [July 12, 2019, 5:34pm UTC](https://meta.discourse.org/t/upgrade-without-ssh-access/122815/5 "2019-07-12T17:34:39Z")
Yes, this would be the simple, straightforward, rational solution. But it entails a number of problems, including changing the domain name, etc. I’ve been trying to take it easy, give some time to the sysadmin, and have the community make a collective decision. These things are not always a question of solving a technical issue, the human factor is important to take into account.
What you propose is a last resort solution that might eventually be taken.
Thank you for your concern!
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [July 12, 2019, 5:36pm UTC](https://meta.discourse.org/t/upgrade-without-ssh-access/122815/6 "2019-07-12T17:36:03Z")
I see. I had assumed that you had control over the domain name, which is separate from the server itself. It sounds much more complicated. ☹
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [August 11, 2019, 5:36pm UTC](https://meta.discourse.org/t/upgrade-without-ssh-access/122815/7 "2019-08-11T17:36:12Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.