Random Execution Timeouts and getaddrinfo ENOTFOUND on Self-Hosted Appwrite
- 0
- Self Hosted
- Functions
- REST API
Hi, I’m running a self-hosted Appwrite (v1.5.10) on a VPS. My setup involves calling an external API many times from Appwrite Functions. Under higher load, I occasionally get random failures like:
Synchronous function execution timed out. Use asynchronous execution instead, or ensure the execution duration doesn't exceed 30 seconds. Error Code: 408 This happens randomly, especially when there’s heavier traffic. I’ve already verified that I have enough function executors available, so it’s not a simple scaling issue.
While testing another script that deletes older documents from a database collection (loop with deleteDocument calls), I started getting errors like:
deleteDocument <id> failed: getaddrinfo ENOTFOUND appwrite.myprojectdomain.com deleteDocument <id> failed: getaddrinfo ENOTFOUND appwrite.myprojectdomain.com These were just sequential deleteDocument calls in a loop, so nothing extreme — yet they failed with DNS resolution errors.
Given that both the random execution timeouts and the getaddrinfo ENOTFOUND occur under load, I’m wondering:
Could this be related to DNS resolver overload in Docker / the VPS?
Is there any known issue with DNS lookups in Appwrite functions under heavy load?
Any best practices for configuring DNS servers for self-hosted Appwrite in production to avoid this?
I’ve tested on another server with a newer Appwrite version, but the issue persisted, so it doesn’t seem version-specific.
Any ideas or similar experiences would be appreciated.
Recommended threads
- MariaDB refuses to connect to appwrite
Earlier, I tried updating my Appwrite version from 18.1.x to the latest release because my Flutter package required it to function properly. I used the official...
- executeFunction intermittently throws Fo...
Environment: Flutter app using the Appwrite Flutter SDK, calling executeFunction for [describe endpoint, e.g. live-stream-related function]. *Description*: Int...
- Console display all Databases as TablesD...
While looking at an issue with <@1231860789355347971> we saw that the console was displaying ALL databases as `TablesDB` even if the real type in the API is `le...