# Discourse in Docker + NGINX reverse proxy + SSL everywhere + OAuth2 Custom

**URL:** <https://meta.discourse.org/t/discourse-in-docker-nginx-reverse-proxy-ssl-everywhere-oauth2-custom/52280>\
**Category:** Self-hosting\
**Created:** [November 1, 2016, 2:15am UTC](https://meta.discourse.org/t/discourse-in-docker-nginx-reverse-proxy-ssl-everywhere-oauth2-custom/52280 "2016-11-01T02:15:31Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![lightweight](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lightweight/32/116381_2.png) [@lightweight](https://meta.discourse.org/u/lightweight)\
**Post date:** [November 13, 2016, 10:57pm UTC](https://meta.discourse.org/t/discourse-in-docker-nginx-reverse-proxy-ssl-everywhere-oauth2-custom/52280/12 "2016-11-13T22:57:23Z")

</div>

Crikey, Maarten, your tip fixes things for me - I removed the token-related argument on the end of the “user json url” and it all bursts into life. I will back out my SSL configuration between the Nginx reverse proxy and the Docker container running my Discourse instance and see if it continues to work! Many thanks for posting!

---

_[View the full topic](https://meta.discourse.org/t/discourse-in-docker-nginx-reverse-proxy-ssl-everywhere-oauth2-custom/52280)._