OAuth Issue: Incorrect client_id still used despite environment update

[ajax]

Hi everyone,

I'm facing a persistent issue with Google authentication on a self-hosted Chatwoot instance running on Cloudron.

When I click on "Sign in with Google", the OAuth URL that's generated is still the following:

https://accounts.google.com/o/oauth2/auth?access_type=offline&client_id=40481950185-vlajho97rkkpavs7f7tahn0c5j36e0d3.apps.googleusercontent.com&prompt=consent&redirect_uri=https%3A%2F%2Fchatwoot.yobbo.bakbit.com%2Fgoogle%2Fcallback&response_type=code&scope=email+profile+https%3A%2F%2Fmail.google.com%2F

The issue is that this client_id refers to an old OAuth credential, even though I have updated the correct GOOGLE_CLIENT_ID in /app/data/env.sh with a completely different ID.
I've saved the file and restarted both the services and the app multiple times — but the old ID is still being used.

Is there some caching or compilation step I might be missing?
Do I need to recompile Chatwoot or reload something beyond restarting the app?

Thanks

[james]

Hello @ajax
This could even be browser cache. Did you try this in a private window?

[luckow]

@james IMHO the wrong category. This is #librechat. The question refers to Chatwoot.

[joseph]

@ajax said in OAuth Issue: Incorrect client_id still used despite environment update:

The issue is that this client_id refers to an old OAuth credential, even though I have updated the correct GOOGLE_CLIENT_ID in /app/data/env.sh with a completely different ID.

Did you put the export keyword in front of the lines ? Like export GOOGLE_CLIENT_ID=xxx .

You shouldn't have to do anything other than restarting .