
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
- phantom relationships appear on parent c...
i have this bug were my past deleted collection apears as relationship to my parent collection. when i try to delete that relationship from parent it gives me e...
- Attributes Problem - Cloud
I am not able to see the attribute columns and their context on cloud. Can you help?
- Authorization header not working in Appw...
I have an Appwrite function that takes a custom bearer token as authentication. The function works fine locally when I test it with `appwrite run functions`, bu...
