Trouble with patreon on multisite

installation
1

I’ve got a multisite instance in which every thing seems to be fine, but one of them is using Patreon. The nginx error logs show some logs like

2019/05/18 18:15:26 [error] 47#47: *285159 upstream prematurely closed connection while reading response header from upstream, client: 1.2.3.4, server: _, request: "GET /auth/patreon/callback?code=4QiVgXA8EG6spf9c0r42ZXSMyG4oUp&state=0bfa04facfd36bfdded7a54d0e9c1ba8038f00c2c7cb6352 HTTP/1.1", upstream: "http://127.0.0.1:3000/auth/patreon/callback?code=4QiVgXA8EG6spf9c2ZXSMyG4oUp&state=0bfa0d36bfdded7a54d0e9c1ba8038f00c2c7cb6352", host: "hostname"

I don’t know why it would be referring to 127.0.0.1:3000. That’s not the port that anything should be reverse proxying to.

The site works fine when using /u/admin-login.

[default] Failed to process hijacked response correctly : execution expired
2

Oh. Doh! 127.0.0.1:3000 is where Discourse is running. From inside the container, curl to there works fine, but curl to https://www.patreon.com/oauth2/callback times out.

The pop-up Patreon login window comes up with a 502 bad gateway

https://theactualhostname/auth/patreon/callback?code=rDXXUwuIZB8&state=88ad43f5fb2321810

I don’t think it’s a multisite issue, but I don’t know what it might be.

3

It was a networking issue that broke (some?) networking in Docker.

3 Likes
4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.