-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Bug Report: Multiple internal curl errors has occurred within the executor! Error Number: 111. #6902
Comments
I am facing same issue. Any update ? |
I am having the same problem with node functions. For me it is not only happening after deployment or restarts, but also if i haven't tested the functions for a few hours (or minutes even?) and i come back to it. The first few executions always fail with I am using appwrite with the DigitalOcean marketplace droplet (https://marketplace.digitalocean.com/apps/appwrite). I tried to investigate yesterday and found the pattern, that whenever I call my function via REST and it fails, i will see the following when running ![]() So this already made me optimistic about finding the underlying issue (redis?) but this morning, when trying again, i could not get this output anymore on failing REST calls. Which actually makes this even weirder. Any help would be appreciated. The current situation is devastating because cloud functions that don't always respond properly are - of course - worth nothing :/ UPDATE (a few minutes later): ![]() Could be that the logs changed because i upgraded the redis docker container. |
I am also encountering the same issue. Multiple internal curl errors on first time, then have to re execute for it to go away. |
Question to all the others who are having similar issues here: |
The thing is, it never used to happen. And now it's been present for like 6 months. |
Okay that's quite a long time, I wasn't aware of that since I only recently started using appwrite. |
It's been since 6 month now. i am still facing same issue. Any update on this ? It is stopping us to make apps live. so it's blocker for us |
It doesn't happen on the paid version, so they probably won't fix it. |
I really hope you are wrong, but yeah... which way are you guys going, Supabase? Firebase? Anything else? |
Literally struggle busing through it and making snarky remarks in discord until it gets addressed. |
I just upgraded my DigitalOcean Appwrite instance to the new For now i am thinking about staying with Appwrite but using a separate express app for some additional backend logic and skipping functions completely. |
I'm on plenty of resources using a dedicated test bed, with version 1.5.3, the same problem still exists. |
Yeah it doesn’t matter and shouldn’t matter. It never used to happen prior to 1.4. I’ve been using the same VM since 0.6. |
We're looking into this problem. Feel free to share any logs that you think might be relevant or steps to reproduce. |
Hi, we used to experience this using WSL and docker, we were able to fix it by switching to linux and having more memory available for appwrite executor/containers. |
In other words - as i assumed - the resources do matter - but i agree with @JakeAi on the other statement, that it should not matter. |
I am having the same issue and daily CRON jobs are inconsistent due to frequent fails. |
We've made some improvements to functions in Cloud and The reproduction case I created previously no longer throws this error so this is looking good. If you are still experiencing this error in your self-hosted setup, please ensure that you've upgraded to |
👟 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: Connection refused\nError Code: 500
🎲 Appwrite version
Version 1.4.x
💻 Operating system
Linux
🧱 Your Environment
Appwrite: 1.4.5
Linux docker-01 5.15.0-73-generic #80-Ubuntu SMP
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: