# Discourse Installation Fudged **URL:** \ **Category:** Support\ **Created:** [April 21, 2017, 1:49am UTC](https://meta.discourse.org/t/discourse-installation-fudged/61367 "2017-04-21T01:49:50Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Tyler\_Humphress](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tyler_humphress/32/68618_2.png) [@Tyler\_Humphress](https://meta.discourse.org/u/Tyler_Humphress)\ **Post date:** [April 21, 2017, 1:49am UTC](https://meta.discourse.org/t/discourse-installation-fudged/61367/1 "2017-04-21T01:49:50Z")
I’ve installed Discourse successfully and have set it up. I attempted to add the [Steam login plugin](https://github.com/discourse/discourse-steam-login) to `app.yml`, then ran `./launcher rebuild app` and it gets stuck at > cd /var/www/discourse && su discourse -c 'bundle install --deployment --verbose --without test --without development until the network connection is lost. When running `./launcher logs app` I see nothing that indicates any sort of error. What should I do to troubleshoot this issue? ---
**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\ **Post date:** [April 21, 2017, 1:55am UTC](https://meta.discourse.org/t/discourse-installation-fudged/61367/2 "2017-04-21T01:55:07Z")
(Mmm… fudge…) The first thing to check is whether there’s a firewall or other network middlebox between wherever you’re installing Discourse and the Internet, that could be getting in the way. If `bundle install` is hanging, it almost certainly means that the container can’t contact `rubygems.org` to download the packages it needs. Also, when you say “the network connection is lost”, which connection do you mean? The complete log of the rebuild session, containing everything between the command start and termination, may show something that you don’t realise is important, but has meaning to someone more experienced with diagnosing these problems. Finally, a complete description of the environment you’re trying to run Discourse in (OS, hosting provider, etc) may be helpful. ---
**Author:** ![Tyler\_Humphress](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tyler_humphress/32/68618_2.png) [@Tyler\_Humphress](https://meta.discourse.org/u/Tyler_Humphress)\ **Post date:** [April 21, 2017, 1:59am UTC](https://meta.discourse.org/t/discourse-installation-fudged/61367/3 "2017-04-21T01:59:11Z")
I’ll go more in depth 🙂 - DigitalOcean, the $10/mo 1GB RAM/30GB SSD Server, **Ubuntu 16.04** (forgot to add) - Using [PuTTY](http://www.putty.org/) for SSH, and when rebuilding it takes about 15 minutes or so (while changing other settings before, SMTP settings in particular, it took roughly 5 minutes or less) but never actually completes afaik. The connection is lost and I’m forced to restart the connection. Not sure if it’s still working in the background and I need to give it more time, or if something is going wrong. When I rebuild the container/app, should I wait for it to drop connection to then run `./launcher logs app`? ---
**Author:** ![Tyler\_Humphress](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tyler_humphress/32/68618_2.png) [@Tyler\_Humphress](https://meta.discourse.org/u/Tyler_Humphress)\ **Post date:** [April 21, 2017, 2:19am UTC](https://meta.discourse.org/t/discourse-installation-fudged/61367/4 "2017-04-21T02:19:51Z")
So I rebuilt yet again after doing `./launcher stop app` and it worked after a few minutes. I have no idea what happened, but it’s fixed. 😛 ---
**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\ **Post date:** [April 21, 2017, 2:20am UTC](https://meta.discourse.org/t/discourse-installation-fudged/61367/5 "2017-04-21T02:20:48Z")
If the rebuild isn’t completing, then `./launcher logs app` won’t help (that’s for logs generated while the app is running, not while it’s building). It’s a bit troubling that (it sounds like) your SSH connection is dropping; that sounds like a networking problem between you and the droplet, but DO networking is usually pretty solid. Couple that with apparent networking troubles to `rubygems.org`, and I’m inclined to think it was transient networking problems at DO that are now fixed, since everything is working again. The Internet is a Mystery. ---
**Author:** ![kraml](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kraml/32/68627_2.png) [@kraml](https://meta.discourse.org/u/kraml)\ **Post date:** [April 21, 2017, 2:23am UTC](https://meta.discourse.org/t/discourse-installation-fudged/61367/6 "2017-04-21T02:23:27Z")
When SSH to a remote server to run some long running task, you’d better start tmux or screen tool, and run your command inside it. In case your lost SSH connection due to some reason, you can always connect again and reattach to the same tmux or screen session, your long running task won’t be interrupted. If I remember correctly, the command you saw that launcher stuck at, is about installing and building some gems, that would take a couple minutes on your type of DO instance. You can either open another SSH connection or open another terminal window if you are using tmux/screen, and use `top` command to see what the system is busy doing. If there are busy processes(from CPU utilization perspective) then it probably is fine, just keep waiting. If no process is busy running, you may run into problem such as get blocked on network side. ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [April 21, 2017, 3:38am UTC](https://meta.discourse.org/t/discourse-installation-fudged/61367/7 "2017-04-21T03:38:21Z")