Google oauth redirect_uri_mismatch
Is there way to get google oauth to work? I'm running into weird issues related to the callback during the redirect.
If I understand, railway proxies things in a special way, which causes the issue.
I read in another post that changing the url to
http rather than https solves the problem, but that isn't a good workaround because google requires clients that are in production to be https.11 Replies
Project ID:
N/Awouldn't this just be something you've missconfigured?
That's what I thought too, but if I make the change as described here:
https://discord.com/channels/713503345364697088/1053388269712322612
It loads the consent screen, but the url is then blocked because its not https
well then use https
https causes verification to fail
with
OAUTH_REQUEST_FAILEDthen it sounds like you've missconfigured something?
but unfortunately this wouldn't be a platform issue, and this question is out of the scope of these help threads
so, actually https doesn't even show the consent screen, it just errors out with
OAUTH_REQUEST_FAILED.
with http shows the consent screen, but the redirect domain is blocked by googlethis would be something you have missconfigured, not an issue with railway
ok, I'll look through it again
thx
What is this comment mean in the other post I linked to?
It looks like you may be experiencing a Google Oauth redirect_uri_mismatch issue, which is likely due to the way the proxy is setup on Railway.
⚠️ experimental feature
What is that talking about?
that is an AI bot answer, pay absolutely no attention to it
oh, ok lol