TypeScript
at Client.call (/usr/local/server/src/function/node_modules/node-appwrite/lib/client.js:195:15)
at async Databases.getDocument (/usr/local/server/src/function/node_modules/node-appwrite/lib/services/databases.js:1749:16)
at async Module.default (file:///usr/local/server/src/function/src/main.js:28:18)
at async execute (/usr/local/server/src/server.js:208:16)
at async action (/usr/local/server/src/server.js:225:7)
at async /usr/local/server/src/server.js:14:5```
NodeJS 16.0
Appwrite v1.6.0 (self hosted)
The function in question:
```try {
client.setEndpoint('https://mywebsite.com:6000/v1')
.setProject(process.env.APPWRITE_FUNCTION_PROJECT_ID)
.setKey(process.env.APPWRITE_API_KEY);
const result = await databases.getDocument(
database_id,
collection_id,
id
);
log(result);
} catch (e) {
error(e);
}```
Possibly relevant, if I use APPWRITE_FUNCTION_API_ENDPOINT as the endpoint I instead receive a generic Nginx 404 error response - the same behaviour if I leave off the port in the current endpoint.
TL;DR
Error message "fetch failed" is appearing when trying to get a document in NodeJS 16.0 using Appwrite v1.6.0 (self-hosted). Switching the endpoint to APPWRITE_FUNCTION_API_ENDPOINT causes a generic Nginx 404 error.Recommended threads
- Appwrite console is too heavy
The Appwrite console is too heavy And all of my services broken Any support , please
- router_deployment_not_found
I updated my function a few times and now i am getting the error: router_deployment_not_found I even reverted back to my original code but i am still getting th...
- Usage of the new Client() and dealing wi...
Hey guys, just a quick one - we had some web traffic the other day and it ended up bombing out - To put in perspective of how the app works, we have a Nuxt Ap...