
I am running Appwrite self-hosted on a dedicated VM and trying to just do the Starter Function (tried with Node 16 and Node 20) after my more complicated one failed. Everything seems to be linked to github correctly and pushing a commit kicks off a deployment however they fail almost immediately. The logs for the deployment just show:
<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}```
The subdomain that is linked to the function also resolves but just shows:
```Error 404
Deployment not found. Create a deployment before trying to execute a function
Type
deployment_not_found```

My appwrite-worker-builds container's log shows this:
Worker builds started
[Job] Received Job (6692b5f6d9b7b7.19762980).
Creating build for deployment: 6692b5f5e9b9f1267c3a
[Job] (6692b5f6d9b7b7.19762980) successfully run.```
Recommended threads
- Index with the requested key already exi...
I'm using appwrite cli to create DB and I'm getting index_already_exists Is there a way to undestand the index name and maybe to skip if it's already exits?
- Hola equipo de soporte,
Hola equipo de soporte, Estoy desarrollando una Function en Appwrite Cloud con Node.js 22 y el siguiente package.json: { "name": "upload-whitelist", "type"...
- Issue - Migration From Cloud > Self Host...
Hi team, I’m trying to migrate a few of my Appwrite projects from the cloud to a self-hosted instance. These projects are currently in “archive mode” due to th...
