
Are you trying to do an API call? What's your doing?

Okay, try to run this:
ipconfig /flushdns

It's in the console I think

but they said in their app, right?

Using node-appwrite
for my project. So yeah it's api

yeah so the dns flushing has nothing to do with it kinda

What API? What node-appwrite version?

give us more info

what is the code you are trying to run

Yes, because the DNS servers changed and it could be that it's hitting the old IP. At lest that's how another user solved this error before 😅

"node-appwrite": "^14.1.0",

bash

lol

.. bash?

my bad

I read console, haahahaahahaha

try this first

In the CMD

const client = new Client()
.setEndpoint(process.env.NEXT_PUBLIC_APPWRITE_ENDPOINT!)
.setProject(process.env.NEXT_PUBLIC_APPWRITE_PROJECT!);
const session = getCookie(c, AUTH_COOKIE_NAME);
if (!session) {
return c.json({ error: "Unauthorized" }, 401);
}
client.setSession(session);
const account = new Account(client);
const user = await account.get();

yeah done, and starting up the app

It's intermittent so it's difficult so say it's resolved but somehow it's working for now

Thanks guys!

If your issue has been solved, mind adding [SOLVED] in the beginning of the title? Happy appwriting! :appwriterocket:

It's always DNS 💀 😆

@Vignesh Gupta Tell us if it happens again 🙂:appwritepeepo:
Recommended threads
- Looking for Partner
I'm looking for partner for long-term collaborating. Of course, I'll pay for you. If you are interested, Please DM me.
- Issue - Migration From Cloud > Self Host...
Hi team, I’m trying to migrate a few of my Appwrite projects from the cloud to a self-hosted instance. These projects are currently in “archive mode” due to th...
- Why "You’ve reached the limit for your G...
Why did Appwrite send me this alert when the usage reached 10605%? Is it too late? Why not when reached 100% usage? And I can not pay for more usage described ...
