Discord Login - OAuth2 - NodeBB

[phenomlab]

@Sampo2910 phenomlab#0581

[Sampo2910]

@phenomlab

I need to add you as friend before I can invite

UPDATE Invited To Test App.

[phenomlab]

@Sampo2910 Hmm - don’t see it in the teams section ?

[Sampo2910]

@phenomlab

[phenomlab]

@Sampo2910 Strange. Accepted it, but still can’t see it.

[Sampo2910]

@phenomlab

Can you try now. I had to put test mode on through main Discord application. Sorry. Forgot about that.

[phenomlab]

@Sampo2910 Still nothing.

[Sampo2910]

@phenomlab

[phenomlab]

@Sampo2910 I think you need to create a team ?

[Sampo2910]

@phenomlab

Done

Good to know all this.

[phenomlab]

@Sampo2910 Now you need to invite me - you probably need to enable 2FA for this also (for obvious security reasons)

[Sampo2910]

@phenomlab

[phenomlab]

@Sampo2910 Am in. Will create a new OAUTH app under this team.

[phenomlab]

@Sampo2910 Having issues with this. Can you let me know if your server is running NGINX, and if it is, can you please post the nginx.conf (obviously remove sensitive information)

[phenomlab]

@phenomlab After checking in various places (including the nginx.conf file), the reason as to why this fails is because of the trailing / in the url within config.json. Now that we’ve removed that and restarted NodeBB, Discord OAUTH works as intended.

[Sampo2910]

@phenomlab

Thank you so much for your time. Very much appreciated.

[Galaxian]

Hi guys. I’m trying to get this Discord plugin to work, but it throws a 502 Bad Gateway error on the /auth/discord/callback URL (but only when it contains the returning GET parameters from Discord).

Any ideas?

[Galaxian]

Hi guys. I’m trying to get my nodeBB setup with this Discord plugin, but the redirect URL gets a 503 Bad Gateway whenever it has the parameters that Discord redirects with it (going straight to /auth/discord/callback loads a vanilla error saying login failed or something to that effect).

Any ideas on how to fix that Bad Gateway problem?

[phenomlab]

@Galaxian hi, and welcome to Sudonix
Can you check your config.json file and ensure that your forum URL doesn’t have a trailing backslash or forward slash in it ? This was the issue @Sampo2910 had.