# Unable to install Discourse following the official instructions

**URL:** <https://meta.discourse.org/t/unable-to-install-discourse-following-the-official-instructions/56157>\
**Category:** Self-hosting\
**Created:** [January 22, 2017, 10:28am UTC](https://meta.discourse.org/t/unable-to-install-discourse-following-the-official-instructions/56157 "2017-01-22T10:28:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pablostarter](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pablostarter/32/93984_2.png) [@pablostarter](https://meta.discourse.org/u/pablostarter)\
**Post date:** [January 22, 2017, 10:28am UTC](https://meta.discourse.org/t/unable-to-install-discourse-following-the-official-instructions/56157/1 "2017-01-22T10:28:25Z")

</div>

Hi,

I’m trying to install Discourse into a VPS following the [provided instructions](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md) but after doing everything they say, step by step when I try to visit the site, the server doesn’t respond.

I spent the last to day trying to find out what is the problem and until now the only piece of information that I found and I think it’s useful is the next error message form the nginx log(shared/standalone/log/var-log/nginx/error.log):

> [emerg] 2928#2928: BIO\_new\_file(“/shared/ssl/startups.startuc3m.com.cer”) failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen(‘/shared/ssl/startups.startuc3m.com.cer’,‘r’) error:2006D080:BIO routines:BIO\_new\_file:no such file)

Any idea what could be happening?

The OS I’m using is Ubuntu 16.04

---

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [January 22, 2017, 1:20pm UTC](https://meta.discourse.org/t/unable-to-install-discourse-following-the-official-instructions/56157/2 "2017-01-22T13:20:11Z")

</div>

Are you trying to use let’s Encrypt?

What does your app.yml look like?

---

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [January 22, 2017, 3:02pm UTC](https://meta.discourse.org/t/unable-to-install-discourse-following-the-official-instructions/56157/4 "2017-01-22T15:02:16Z")

</div>

Does the domain name that you used resolve to your droplet? If not lets encrypt cannot work.

You might disable (comment out with a # at the start of the line) the two lines that have to do with letsemcrypt, or start again and don’t define the let’s encrypt email address.

---

<div class="post-metadata">

**Author:** ![pablostarter](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pablostarter/32/93984_2.png) [@pablostarter](https://meta.discourse.org/u/pablostarter)\
**Post date:** [January 22, 2017, 3:50pm UTC](https://meta.discourse.org/t/unable-to-install-discourse-following-the-official-instructions/56157/5 "2017-01-22T15:50:10Z")

</div>

Ok! I found the problem, I had changed the A record so the subdomain was pointing to my server, what I forgot is that I had another server monitoring that subdomain ip and changing it to point to it.

I just stoped the monitoring process, changed the A record again, ./launcher rebuild app and now it’s working lika a charm.

Thank yo very much.

---

<div class="post-metadata">

**Author:** ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)\
**Post date:** [June 8, 2024, 12:45pm UTC](https://meta.discourse.org/t/unable-to-install-discourse-following-the-official-instructions/56157/6 "2024-06-08T12:45:03Z")

</div>

This topic was automatically closed after 2694 days. New replies are no longer allowed.