🐛 Bug Report: Multiple internal curl errors has occurred within the executor! Error Number: 111
Shows how to fix 🐛 Bug Report: Multiple internal curl errors has occurred within the executor! Error Number: 111. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Fixes that worked in the thread: upgrade self-hosted Appwrite to 1.5.7, which includes executor improvements that dropped the error rate to zero for the reporter's repro; and give the executor more memory, running on native Linux instead of WSL plus Docker.
Steps
- Appwrite - ### 👟 Reproduction steps
- The first execution after deployment/restart.
- Appwrite functions failing with 'Multiple internal curl errors... Error Number: 111' (connection refused) on the first run after deploy or restart is a resource problem: the executor containers are not fully up when the first call lands. Fixes that worked in the thread: upgrade self-hosted Appwrite to 1.5.7, which includes executor improvements that dropped the error rate to zero for the reporter's repro; and give the executor more memory, running on native Linux instead of WSL plus Docker. On a tiny droplet, expect the first few calls to fail while things warm up.
When to use
You are seeing this: Appwrite functions failing with 'Multiple internal curl errors... Use this skill when you run into "🐛 Bug Report: Multiple internal curl errors has occurred within the executor! Error Number: 111".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: 1.5.7. If you are on something much newer or older, the details may have shifted.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Sources
- https://github.com/appwrite/appwrite/issues/6902