🐛 Bug Report: Multiple internal curl errors has occurred within the executor! Error Number: 111

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

1. Appwrite - ### 👟 Reproduction steps
2. The first execution after deployment/restart.
3. 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

In gh:appwrite/appwrite#6902 (https://github.com/appwrite/appwrite/issues/6902), the issue reported: ### 👟 Reproduction steps

The first execution after deployment/restart. When you're testing a function, and you have to keep deploying it and running it, and constantly get the CURL error.. it's a pain in the arse. Deploy a (node?) function and execute it.

https://discord.com/channels/564160730845151244/1162099630494973982 (Wasn't actually solved) https://discord.com/channels/564160730845151244/1151439270041628763

👍 Expected behavior

It should run normally

👎 Actual Behavior

Multiple internal curl errors has occurred within the executor! Error Number: 111. Error Msg:... The verified answer: 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.