Discourse has stopped opening

[itamerlanium]

/shared/log/var-log/nginx

Unfortunately, it gives nothing.

root@discourse:~# ./launcher logs app
-su: ./launcher: No such file or directory

root@discourse:/# cd /shared/log/var-log/nginx
-su: cd: /shared/log/var-log/nginx: No such file or directory

[riking]

Yeah, this is the problem. (“Emerg” = Emergency)

[itamerlanium]

Those emerg entries on the nginx log mean he’s not gonna run. This is a problem with your ssl setup, it is missing deparams.

I recommend setting up ssl again.

I went through this tutorial How To Install Discourse Behind Nginx on Ubuntu 14.04 | DigitalOcean to recreate SSL Certificate on Nginx for Ubuntu 14.04 and got a message.

root@discourse:/opt/letsencrypt# ./letsencrypt-auto certonly --standalone --email tamerlanium@gmail.com --agree-tos -d specknz.me

The program exe (process ID 1304) is already listening on TCP port   │
   │ 443. This will prevent us from binding to that port. Please stop the │
   │ exe program temporarily and then try again.

At least one of the (possibly) required ports is already taken.

root@discourse:/opt/letsencrypt# cd /etc/letsencrypt/live
-su: cd: /etc/letsencrypt/live: No such file or directory

root@discourse:/opt/letsencrypt# ls
acme                        letsencrypt-nginx
certbot                     letshelp-certbot
certbot-apache              letshelp-letsencrypt
certbot-auto                LICENSE.txt
certbot-compatibility-test  linter_plugin.py
certbot-nginx               MANIFEST.in
CHANGES.rst                 pep8.travis.sh
CONTRIBUTING.md             README.rst
docker-compose.yml          readthedocs.org.requirements.txt
Dockerfile                  setup.cfg
Dockerfile-dev              setup.py
docs                        tests
examples                    tools
letsencrypt                 tox.cover.sh
letsencrypt-apache          tox.ini
letsencrypt-auto            Vagrantfile
letsencrypt-auto-source

And didn’t get a response similar to this:

Let’s Encrypt Output
IMPORTANT NOTES:

• If you lose your account credentials, you can recover through
  e-mails sent to sammy@example.com.
• Congratulations! Your certificate and chain have been saved at
  /etc/letsencrypt/live/discourse.example.com/fullchain.pem. Your
  cert will expire on 2016-04-26. To obtain a new version of the
  certificate in the future, simply run Let’s Encrypt again.
• Your account credentials have been saved in your Let’s Encrypt
  configuration directory at /etc/letsencrypt. You should make a
  secure backup of this folder now. This configuration directory will
  also contain certificates and private keys obtained by Let’s
  Encrypt so making regular backups of this folder is ideal.

[tgxworld]

Hmm how was your Discourse instance setup? Are you on the docker based install?

[itamerlanium]

Yeah, it have been installed through the Docker instance.

[tgxworld]

Try following

Setting up Let's Encrypt

So you’d like to add https to your Discourse absolutely free, courtesy of our friends at Let’s Encrypt? :bell: Is everything else on your site ready for HTTPS? Before you start, please bear in mind that for HTTPS to work properly, every single resource on the page must be HTTPS compatible. Consider your CDN, your social logins, your logo files, any third party JavaScript, images, fonts, or css — these all must be available over HTTPS! Note: ./discourse-setup will enable Let’s Encrypt. And …

to install a Let’s Encrypt cert instead

[itamerlanium]

Sorry Guo, should I rebuild the Discourse container?

4. Rebuild your container

./launcher rebuild <container name>

[sam]

Sorry Guo, should I rebuild the Discourse container?

Yes

Can you please try rebuilding?

Please SSH into your server and run:

cd /var/discourse
git pull
./launcher rebuild app

[sam]

See:

Yes Can you please try rebuilding? Please SSH into your server and run: cd /var/discourse git pull ./launcher rebuild app

run ./launcher rebuild app

[itamerlanium]

Ups I missed it
I’ve resized the Droplet to 1Gb by the using SWAP and tried to rebuild it, but it didn’t help me. However, yesterday I rebuild it successfully.

if ($http_host != $$ENV_DISCOURSE_HOSTNAME) {
   rewrite (.*) https://$$ENV_DISCOURSE_HOSTNAME$1 permanent;
} in /etc/nginx/conf.d/discourse.conf
I, [2016-07-27T06:45:30.779342 #13]  INFO -- : > if [ -z "$LETSENCRYPT_ACCOUNT_EMAIL" ]; then echo "LETSENCRYPT_ACCOUNT_EMAIL ENV variable is required and has not been set."; exit 1; fi
I, [2016-07-27T06:45:30.782199 #13]  INFO -- : LETSENCRYPT_ACCOUNT_EMAIL ENV variable is required and has not been set.

I, [2016-07-27T06:45:30.789702 #13]  INFO -- : Terminating async processes
I, [2016-07-27T06:45:30.790433 #13]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/9.5/bin/postmaster -D /etc/postgresql/9.5/main pid: 42
2016-07-27 06:45:30 UTC [42-2] LOG:  received fast shutdown request
2016-07-27 06:45:30 UTC [42-3] LOG:  aborting any active transactions
2016-07-27 06:45:30 UTC [49-2] LOG:  autovacuum launcher shutting down
I, [2016-07-27T06:45:30.801912 #13]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 155
155:signal-handler (1469601930) Received SIGTERM scheduling shutdown...
2016-07-27 06:45:30 UTC [46-1] LOG:  shutting down
2016-07-27 06:45:30 UTC [46-2] LOG:  database system is shut down
155:M 27 Jul 06:45:30.851 # User requested shutdown...
155:M 27 Jul 06:45:30.852 * Saving the final RDB snapshot before exiting.
155:M 27 Jul 06:45:30.990 * DB saved on disk
155:M 27 Jul 06:45:30.990 # Redis is now ready to exit, bye bye...


FAILED
--------------------
Pups::ExecError: if [ -z "$LETSENCRYPT_ACCOUNT_EMAIL" ]; then echo "LETSENCRYPT_ACCOUNT_EMAIL ENV variable is required and has not been set."; exit 1; fi failed with return #<Process::Status: pid 3087 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cmd"=>["if [ -z \"$LETSENCRYPT_ACCOUNT_EMAIL\" ]; then echo \"LETSENCRYPT_ACCOUNT_EMAIL ENV variable is required and has not been set.\"; exit 1; fi", "/bin/bash -c \"if [[ ! \\\"$LETSENCRYPT_ACCOUNT_EMAIL\\\" =~ ([^@]+)@([^\\.]+) ]]; then echo \\\"LETSENCRYPT_ACCOUNT_EMAIL is not a valid email address\\\"; exit 1; fi\""]}
b723307a27a32d6c808e520b0cc3000fa2cbfe732291dd1bb312e7c9b8bfb375
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
root@discourse:/var/discourse#

[sam]

LETSENCRYPT_ACCOUNT_EMAIL ENV variable is required and has not been set.

hmmm… is that set?

[itamerlanium]

Yep, I’ve put some дштуы to the app.yml file then rebuilded the application.

containers/app.yml

templates:
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/web.template.yml"
  - "templates/web.ratelimited.template.yml"
## Uncomment these two lines if you wish to add Lets Encrypt (https)
  - "templates/web.ssl.template.yml"
  - "templates/web.letsencrypt.ssl.template.yml"

## which TCP/IP ports should this container expose?
## If you want Discourse to share a port with another webserver like Apache or $
## see https://meta.discourse.org/t/17247 for details
expose:
  - "80:80"   # fwd host port 80 to container port 80 (http)
  - "443:443" # https

params:
  db_default_text_search_config: "pg_catalog.english"

  ## Set db_shared_buffers to a max of 25% of the total memory.
  ## will be set automatically by bootstrap based on detected RAM, or you can o$
  #db_shared_buffers: "256MB"

  ## can improve sorting performance, but adds memory usage per-connection
  #db_work_mem: "40MB"

  ## Which Git revision should this container use? (default: tests-passed)
  #version: tests-passed

env:
  LANG: en_US.UTF-8
  # DISCOURSE_DEFAULT_LOCALE: en
  # LETSENCRYPT_ACCOUNT_EMAIL: '*********@gmail.com'

[cpradio]

# LETSENCRYPT_ACCOUNT_EMAIL: ‘tamerlanium@gmail.com’

You still have it commented out. You need to remove the # in front of LETSENCRYPT_ACCOUNT_EMAIL

[itamerlanium]

Thanks mate, I uncommented this line and I’ve just rebuilt the app, however http://specknz.me/ is still not working

Removing old container
+ /usr/bin/docker rm app
app

+ /usr/bin/docker run -d --restart=always -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=3 -e UNICORN_SIDEKIQS=1 -e RUBY_GLOBAL_METHOD_CACHE_SIZE=131072 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e LETSENCRYPT_DIR=/shared/letsencrypt -e LETSENCRYPT_ACCOUNT_EMAIL=********@gmail.com -e DISCOURSE_HOSTNAME=speckme.nz -e DISCOURSE_DEVELOPER_EMAILS=********@gmail.com -e DISCOURSE_SMTP_ADDRESS=smtp.gmail.com -h discourse-app -e DOCKER_HOST_IP=172.17.0.1 --name app -t -p 80:80 -p 443:443 -v /var/discourse/shared/standalone:/shared -v /var/discourse/shared/standalone/log/var-log:/var/log --mac-address 02:f9:8c:dd:3d:63 local_discourse/app /sbin/boot
8196afcbe767c649b3cb20dcb76c607d5267e3e8eaff323f98050de085769137
root@discourse:/var/discourse#

[cpradio]

You’ll have to paste more of your app.yml, be sure to remove any sensitive information, such as, passwords and email addresses (that you don’t what publicized).

Seems the rebuild was successful though…

[itamerlanium]

Sure

    ## this is the all-in-one, standalone Discourse Docker container
    ## template
    ##
    ## After making changes to this file, you MUST rebuild
    ## /var/discourse/launcher rebuild app
    ##
    ## BE *VERY* CAREFUL WHEN EDITING!
    ## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT!
    ## visit http://www.yamllint.com/ to validate this file as needed

    templates:
      - "templates/postgres.template.yml"
      - "templates/redis.template.yml"
      - "templates/web.template.yml"
      - "templates/web.ratelimited.template.yml"
    ## Uncomment these two lines if you wish to add Lets Encrypt (https)
      - "templates/web.ssl.template.yml"
      - "templates/web.letsencrypt.ssl.template.yml"

    ## which TCP/IP ports should this container expose?
    ## If you want Discourse to share a port with another webserver like Apache or nginx,
    ## see https://meta.discourse.org/t/17247 for details
    expose:
      - "80:80"   # fwd host port 80 to container port 80 (http)
      - "443:443" # https

    params:
      db_default_text_search_config: "pg_catalog.english"

      ## Set db_shared_buffers to a max of 25% of the total memory.
      ## will be set automatically by bootstrap based on detected RAM, or you can override
      #db_shared_buffers: "256MB"

      ## can improve sorting performance, but adds memory usage per-connection
      #db_work_mem: "40MB"

      ## Which Git revision should this container use? (default: tests-passed)
      #version: tests-passed

    env:
      LANG: en_US.UTF-8
      # DISCOURSE_DEFAULT_LOCALE: en
      LETSENCRYPT_ACCOUNT_EMAIL: '**********@gmail.com'

    ## How many concurrent web requests are supported? Depends on memory and CPU cores.
      ## will be set automatically by bootstrap based on detected CPUs, or you can override
      #UNICORN_WORKERS: 3

      ## TODO: The domain name this Discourse instance will respond to
      DISCOURSE_HOSTNAME: 'speckme.nz'

      ## Uncomment if you want the container to be started with the same
      ## hostname (-h option) as specified above (default "$hostname-$config")
      #DOCKER_USE_HOSTNAME: true

      ## TODO: List of comma delimited emails that will be made admin and developer
      ## on initial signup example 'user1@example.com,user2@example.com'
      DISCOURSE_DEVELOPER_EMAILS: '********@gmail.com'

      ## TODO: The SMTP mail server used to validate new accounts and send notifications
      DISCOURSE_SMTP_ADDRESS: smtp.gmail.com         # required
      DISCOURSE_SMTP_PORT: 587                        # (optional, default 587)
      DISCOURSE_SMTP_USER_NAME: ***********@gmail.com      # required
      DISCOURSE_SMTP_PASSWORD: **********               # required, WARNING the char '#' in pw can cause problems!
      DISCOURSE_SMTP_ENABLE_START_TLS: true           # (optional, default true)

      ## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate
      LETSENCRYPT_ACCOUNT_EMAIL: ************@gmail.com

      ## The CDN address for this Discourse instance (configured to pull)
      ## see https://meta.discourse.org/t/14857 for details
      #DISCOURSE_CDN_URL: //discourse-cdn.example.com

    ## The Docker container is stateless; all data is stored in /shared
    volumes:
      - volume:
          host: /var/discourse/shared/standalone
          guest: /shared
      - volume:
          host: /var/discourse/shared/standalone/log/var-log
          guest: /var/log

    ## Plugins go here
    ## see https://meta.discourse.org/t/19157 for details
    hooks:
      after_code:
        - exec:
            cd: $home/plugins
            cmd:
              - git clone https://github.com/discourse/docker_manager.git

    ## Any custom commands to run after building
    run:
      - exec: echo "Beginning of custom commands"
      ## If you want to set the 'From' email address for your first registration, uncomment and change:
      ## After getting the first signup email, re-comment the line. It only needs to run once.
      #- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'"
      - exec: echo "End of custom commands"

[cpradio]

Wait… now you have LETSENCRPYT_ACCOUNT_EMAIL in there twice. You only need it once (your prior subset didn’t indicate that it was there twice).

I’m not seeing anything obvious however. Do you have apache/nginx sitting in front of Discourse and hosting other sites on the same box, or does this box only run Discourse via Docker?

[itamerlanium]

Yep, I initialised Nginx to handle two websites, then decided to don’t use this approach for the $5 Droplet.

[cpradio]

Any chance you still have parts of nginx configured and it is intefering with serving Discourse?

[itamerlanium]

The settings should be sitting there. How could I switch it off or maybe uninstalling can help in this case, but I’m not sure that it could be help to clean the settings.