appwrite
🐛 Bug Report: 1.5.7 All function builds fail
👟 Reproduction steps
Appwrite 1.5.7 on Ubuntu 24.04 Create a new node-js starter function (I have tried node-16,node-18,node-20,python39,python312 as well). Deployment builds fail The same functions build and deploy on Appwrite Cloud.
👍 Expected behavior
Build function and allow executions
👎 Actual Behavior
All builds fail.
Deployment logs show:
<html>
<head><title>405 Not Allowed</title></head>
<body>
<center><h1>405 Not Allowed</h1></center>
<hr><center>openresty</center>
</body>
</html>
/usr/src/code/src/Executor/Executor.php:97
#0 /usr/src/code/src/Appwrite/Platform/Workers/Builds.php(407): Executor\Executor->createRuntime('6692b8b5d60b64a...', '65b83427546014b...', '/storage/functi...', 'openruntimes/no...', 'v3', true, 'src/main.js', '/storage/builds...', Array, 'tar -zxf /tmp/c...')
#1 [internal function]: Appwrite\Platform\Workers\Builds->Appwrite\Platform\Workers\{closure}()
#2 {main}
openruntimes-executor logs show:
Removing orphan runtimes...
Cleaning up containers...
No containers found to clean up.
Cleanup finished.
Orphan runtimes removal finished.
Pulling v3 images...
Warming up Node.js 18.0 environment...
Warming up Python 3.12 environment...
Successfully Warmed up Node.js 18.0!
Successfully Warmed up Python 3.12!
Image pulling finished.
Starting maintenance interval...
Maintenance interval started.
Starting stats interval...
Stats interval started.
Executor is ready.
appwrite-worker-functions log shows:
[Worker] Worker 0 is ready!
Worker functions started
[Job] Received Job (669477f9a87451.74365263).
Fetched 1 functions...
[Job] (669477f9a87451.74365263) successfully run.
[Job] Received Job (669477fb202657.21750661).
Fetched 1 functions...
[Job] (669477fb202657.21750661) successfully run.
🎲 Appwrite version
Version 1.5.x
💻 Operating system
Linux
🧱 Your Environment
Appwrite 1.5.7 on Ubuntu 24.04 Proxmox VM behind Nginx Proxy Manager on separate host Cloudflare is setup for DNS however I have tried with everything grey-clouded
👀 Have you spent some time to check if this issue has been raised before?
- [X] I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- [X] I have read the Code of Conduct
_APP_EXECUTOR_HOST=http://exc1./v1 resolved my issue which was due to name resolution of just having _APP_EXECUTOR_HOST=http://exc1/v1 which resolved in my DNS search domains. Updating the default .env for self hosting would be ideal.
_APP_EXECUTOR_HOST=http://exc1./v1resolved my issue which was due to name resolution of just having_APP_EXECUTOR_HOST=http://exc1/v1which resolved in my DNS search domains. Updating the default .env for self hosting would be ideal.
thanks, I have the same problem and now it is working
