My appwrite selfhosted instance is saying google Auth provider isnt enabled when Im staring at it being enabled rn ๐คจ ๐ญ {"message":"This provider is disabled. Please enable the provider from your Appwrite console to continue.","code":412,"type":"project_provider_disabled","version":"1.6.0"}
Code:
const handleGoogleLogin = () => {
account.createOAuth2Session(
'google',
'https://myurl.com/dashboard',
'https://myurl.com/login'
);
};```
Did you double check the project id/endpoint?
Can you share network logs as well?
Yes they are correct
Network Logs:
https://cloud.mindbloomapp.com/v1/account/sessions/oauth2/google?success=https%3A%2F%2Fmindbloomapp.com%2Fdashboard&failure=https%3A%2F%2Fmindbloomapp.com%2Fsignup&project=projectId
Request Method:
GET
Status Code:
412 Precondition Failed (from disk cache)
Remote Address:
my ip...
Referrer Policy:
strict-origin-when-cross-origin```
Didnt know if project id was safe to share or not so removed it
what browser are you using?
Microsoft Edge
Ahh, okay!
Is your app domain allowed in console for cross origin/cors? just verifying if that's what is causing this!
As in on the website? I have just * there for all domains allowed since Im using alot of different domains depending on what device im using. I could switch it quickly though if you think that would fix the error maybe?
Yes, try to make it specific, let's see if that's what causing this! share the screenshot as well.
Ok I updated it but still same {
"message": "This provider is disabled. Please enable the provider from your Appwrite console to continue.",
"code": 412,
"type": "project_provider_disabled",
"version": "1.6.0"
}
but this time its 412 Precondition Failed not (from disk cache)
@Steven got any idea, what might be causing this?
Recommended threads
- Go 1.25 runtime
So I'm trying to use go 1.25 for my functions and I can only find go-1.23 as a function runtime. So I did some searching and found https://github.com/appwrite/a...
- [ENHANCEMENT] Use the custom Next.js dep...
Deployment adapters on Next.js are now stable! This means that we don't have to stick to the limitations of sniffing out build outputs and manually moving or mo...
- NextJS builds sudden runtime_timeout
My builds suddenly stopped working. Activating old prebuilt snapshots work, but redeploying that same code produces builds that throw runtime_timeout FRA region