For some reason after the 1.4.2 update i cannot simply create a nodejs runtime function through the console. The only availiable runtimes can be seen below in the picture. Also the template-starter page presents 5 different runtimes(including node-18), but when using the CLI to init functions(because the console doesnt work), i can only pick node-16 runtime.
Weird 🤔 Can you pls open your .env file and provide me with your value for _APP_FUNCTIONS_RUNTIMES? That might give me some direction towards finding the bug
Checked some other issues: https://discord.com/channels/564160730845151244/1147311089135132703/1147320828791365663 Says one needs to enable node-18. Should _APP_FUNCTIONS_RUNTIMES be changed to node-18.0 instead?
_APP_FUNCTIONS_RUNTIMES=node-16.0,php-8.0,python-3.9,ruby-3.0
Ah. I found it here: https://github.com/appwrite/appwrite/discussions/4826. Have to update the .env.
[SOLVED] Can't create node function from console
Can't create node function from console
I jumped the gun, after changing the .env, the appwrite console breaks. I get gateway timeout
Okay, it seems to work now. However i have an existing function created with node-16.0 runtime. How can i update this to use node-18.0 instead, so i dont have to delete it?
You'll have to recreate to use the new function syntax. otherwise you can try to update the function runtime in the function settings
[SOLVED] Can't create node function from console
Recommended threads
- Dotnet functions on cloud
I'm trying to deploy my .Net8 functions to my project on cloud.appwrite through the CLI. I'm getting this error.
- TablesDB can't be used in Appwrite Funct...
I have written a function (DART) and it won't deploy. Here is what I get : 2026-03-14T17:09:41.459693680Z Compiling ... 2026-03-14T17:09:42.915619217Z ../build...
- Local appwrite run functions --user-id n...
Hi, I'm running into an issue when testing Appwrite functions locally with user impersonation. I'm using a self-hosted Appwrite instance and running functions ...