Twitter, Github and normal username and password logins not working after upgrade

[AstonJ]

Yes @cpradio

This is in my haproxy config (when it matches the url of my first Discourse forum):

backend discourse_docker
server server2 127.0.0.1:8888 cookie A check
cookie JSESSIONID prefix no cache

And in my container:

expose:

• “8888:80” # fwd host port 80 to container port 80 (http)
• “2222:22” # fwd host port 2222 to container port 22 (ssh)

Full file here:

After making changes to this file, you MUST rebuild for any changes

to take effect in your live Discourse instance:

/var/discourse/launcher rebuild app

Make sure to obey YAML syntax! You can use this site to help check:

http://www.yamllint.com/

this is the all-in-one, standalone Discourse Docker container template

You may add rate limiting by uncommenting the web.ratelimited template.

Out of the box it allows 12 reqs a second per ip, and 100 per minute per ip

This is configurable by amending the params in this file

templates:

• “templates/postgres.template.yml”
• “templates/redis.template.yml”
• “templates/web.template.yml”
• “templates/sshd.template.yml”
• “templates/web.ratelimited.template.yml”

which TCP/IP ports should this container expose?

expose:

• “8888:80” # fwd host port 80 to container port 80 (http)
• “2222:22” # fwd host port 2222 to container port 22 (ssh)

params:
db_default_text_search_config: “pg_catalog.english”

Set db_shared_buffers to a max of 25% of the total memory.

On 1GB installs set to 128MB (to leave room for other processes)

on a 4GB instance you may raise to 1GB

#db_shared_buffers: “256MB”

Set higher on large instances it defaults to 10MB, for a 3GB install 40MB is a good default

this improves 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

TODO: How many concurrent web requests are supported?

With 2GB we recommend 3-4 workers, with 1GB only 2

#UNICORN_WORKERS: 3

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: ‘myemail@gmx.net’

TODO: The domain name this Discourse instance will respond to

DISCOURSE_HOSTNAME: ‘metaruby.com’

TODO: The mailserver this Discourse instance will use

DISCOURSE_SMTP_ADDRESS: mail.myserver.net
DISCOURSE_SMTP_PORT: 25
DISCOURSE_SMTP_USER_NAME: contact@myforum.com
DISCOURSE_SMTP_PASSWORD: password
#DISCOURSE_SMTP_ENABLE_START_TLS: false
DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: ‘none’

The CDN address for this Discourse instance (configured to pull)

#DISCOURSE_CDN_URL: //discourse-cdn.example.com

These containers are stateless, all data is stored in /shared

volumes:

• volume:
  host: /home/metaruby/apps/discourse/shared/standalone
  guest: /shared
• volume:
  host: /home/metaruby/apps/discourse/shared/standalone/log/var-log
  guest: /var/log

The docker manager plugin allows you to one-click upgrade Discourse

http://discourse.example.com/admin/docker

hooks:
after_code:
- exec:
cd: $home/plugins
cmd:
- mkdir -p plugins
- git clone GitHub - discourse/docker_manager: Plugin for use with discourse docker image · GitHub
- git clone GitHub - discourse/discourse-tagging: Tagging functionality for Discourse Forums · GitHub
- git clone GitHub - discourse/discourse-solved: Allow accepted answers on topics · GitHub

Remember, this is YAML syntax - you can only have one block with a name

run:

• exec: echo “Beginning of custom commands”

If you want to set the ‘From’ email address for your first registration, uncomment and change:

#- exec: rails r “SiteSetting.notification_email=‘info@unconfigured.discourse.org’”

After getting the first signup email, re-comment the line. It only needs to run once.

If you want to configure password login for root, uncomment and change:

Use only one of the following lines:

#- exec: /usr/sbin/usermod -p ‘PASSWORD_HASH’ root
#- exec: /usr/sbin/usermod -p “$(mkpasswd -m sha-256 ‘RAW_PASSWORD’)” root

If you want to authorized additional users, uncomment and change:

#- exec: ssh-import-id username
#- exec: ssh-import-id anotherusername

• exec: echo “End of custom commands”
• exec: awk -F# ‘{print $1;}’ ~/.ssh/authorized_keys | awk ‘BEGIN { print “Authorized SSH keys for this container:”; } NF>=2 {print $NF;}’

run:

• file:
  path: /tmp/add-cert
  chmod: +x
  contents: |
  #!/bin/bash -e
  #Download cert
  wget http://mysite.net/crts/cert8.txt -O - > /usr/local/share/ca-certificates/aston-email.crt
  update-ca-certificates

• exec: “/tmp/add-cert”

(I think all of this was set-up in this manner after the advice I got here on Meta.)