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

**URL:** <https://meta.discourse.org/t/twitter-github-and-normal-username-and-password-logins-not-working-after-upgrade/51854>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [Outubro 21, 2016, 12:58pm UTC](https://meta.discourse.org/t/twitter-github-and-normal-username-and-password-logins-not-working-after-upgrade/51854 "2016-10-21T12:58:57Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![AstonJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/astonj/32/215041_2.png) [@AstonJ](https://meta.discourse.org/u/AstonJ)\
**Post date:** [Outubro 21, 2016, 5:53pm UTC](https://meta.discourse.org/t/twitter-github-and-normal-username-and-password-logins-not-working-after-upgrade/51854/19 "2016-10-21T17:53:48Z")

</div>

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/](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](http://metaruby.com)’
> 
> ## TODO: The mailserver this Discourse instance will use
> 
> DISCOURSE\_SMTP\_ADDRESS: [mail.myserver.net](http://mail.myserver.net)  
> DISCOURSE\_SMTP\_PORT: 25  
> DISCOURSE\_SMTP\_USER\_NAME: [contact@myforum.com](mailto: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](https://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](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](https://github.com/discourse/docker_manager.git)  
> - git clone [GitHub - discourse/discourse-tagging: Tagging functionality for Discourse Forums · GitHub](https://github.com/discourse/discourse-tagging.git)  
> - git clone [GitHub - discourse/discourse-solved: Allow accepted answers on topics · GitHub](https://github.com/discourse/discourse-solved.git)
> 
> ## 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](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.)

---

_[View the full topic](https://meta.discourse.org/t/twitter-github-and-normal-username-and-password-logins-not-working-after-upgrade/51854)._