# Site unreachable after failed attempt to upgrade **URL:** \ **Category:** Support\ **Created:** [November 3, 2016, 2:20pm UTC](https://meta.discourse.org/t/site-unreachable-after-failed-attempt-to-upgrade/52442 "2016-11-03T14:20:31Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![lostintime](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lostintime/32/54115_2.png) [@lostintime](https://meta.discourse.org/u/lostintime)\ **Post date:** [November 3, 2016, 2:20pm UTC](https://meta.discourse.org/t/site-unreachable-after-failed-attempt-to-upgrade/52442/1 "2016-11-03T14:20:31Z")
Hi guys, I justr tried the automatic upgrade from 17beta6 to 17beta7. The upgrade didn’t succeed and the last messages I had on the console screen were: ``` Bundle complete! 99 Gemfile dependencies, 177 gems now installed. Gems in the group development were not installed. Bundled gems are installed into ./vendor/bundle. bundle exec rake multisite:migrate ``` As expected, Ningx gives me an error message when I try to access the site: 504 gateway timeout I ssh-ed into the server but I really don’t know what to do next. The docker daemon does not seem to be running: ``` alex@community:/var/discourse$ ./launcher logs app Cannot connect to the docker daemon - verify it is running and you have access ``` Could someone please advise how to get the site back up and running? Thanks! ---
**Author:** ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)\ **Post date:** [November 3, 2016, 2:30pm UTC](https://meta.discourse.org/t/site-unreachable-after-failed-attempt-to-upgrade/52442/2 "2016-11-03T14:30:10Z")
Have you tried rebuilding? After ssh’ing to the server, ```plaintext cd /var/discourse git pull ./launcher rebuild app ``` ---
**Author:** ![lostintime](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lostintime/32/54115_2.png) [@lostintime](https://meta.discourse.org/u/lostintime)\ **Post date:** [November 3, 2016, 2:46pm UTC](https://meta.discourse.org/t/site-unreachable-after-failed-attempt-to-upgrade/52442/3 "2016-11-03T14:46:33Z")
Thanks for that Joshua. I am rebuilding now and keeping my fingers crossed … ---
**Author:** ![lostintime](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lostintime/32/54115_2.png) [@lostintime](https://meta.discourse.org/u/lostintime)\ **Post date:** [November 3, 2016, 3:01pm UTC](https://meta.discourse.org/t/site-unreachable-after-failed-attempt-to-upgrade/52442/4 "2016-11-03T15:01:12Z")
Whew, the site is back up (and I have a few more grey hairs …) Thanks again Joshua, you guys rock. ---
**Author:** ![dcgavril](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dcgavril/32/121449_2.png) [@dcgavril](https://meta.discourse.org/u/dcgavril)\ **Post date:** [November 3, 2016, 3:07pm UTC](https://meta.discourse.org/t/site-unreachable-after-failed-attempt-to-upgrade/52442/5 "2016-11-03T15:07:50Z")
Same thing happened to my installation while upgrading from 17 beta 6 to beta 7. Had to rebuild app to set it back up… Thanks @jomaxro ---
**Author:** ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)\ **Post date:** [November 3, 2016, 5:42pm UTC](https://meta.discourse.org/t/site-unreachable-after-failed-attempt-to-upgrade/52442/6 "2016-11-03T17:42:21Z")
FYI: the failed upgrade was due to a nasty bug in a library we use to execute JavaScript on the server-side. It has since been fixed.