You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Github Oauth, I set the proper Client ID and Client Secret through the admin page. The oauth works perfectly in a development environment, but when pushed to production, it results in a redirect_uri_mismatch as shown above (tested running 'node main.js' with env variables set).
You MUST set the callback URL, and your ROOT_URL to the exact domain name. Not IP address in one, and domain name in another. It is a 'string compare' and will not 'resolve'.
That was quick. It worked. I didn't know it was a string compare between the two values. Guess it wasn't much of an issue after all haha, thanks a ton though.
Using Github Oauth, I set the proper Client ID and Client Secret through the admin page. The oauth works perfectly in a development environment, but when pushed to production, it results in a redirect_uri_mismatch as shown above (tested running 'node main.js' with env variables set).
Authorization callback URL when in production is set to:
http://104.131.8.9/_oauth/github
That IP Address resolves to the production app on the remote server, served with nginx.
The text was updated successfully, but these errors were encountered: