[SOLVED] Cannot deploy nor execute functions: File not found

Self-hosted version 1.4.4

Upon executing an already-deployed function, I receive the error in docker logs openruntimes-executor

When attempting to redeploy a function - either manually uploaded or from github, I get this error:

Setting "_APP_EXECUTOR_HOST" to "http://executor/v1" caused an error when deploying or executing functions: Could not resolve host: executor with status code 0 (I did run docker compose up -d after modifying the env file)

I've searched the other support threads on this error and have followed the suggested solutions without luck.

I do use backblaze for storage.

Thank you

after following the guide you got everything up and running and doing docker ps -a shows all appwrite containers running normally?

Its an installation from 1.3.X. docker ps -a shows all containers running normally; here's the output for reference

so 1.3.X vs 1.4.X installs changed, a lot was added

Yeah, this function is developed around 1.4, it was working on 1.4.3

your _EXECUTOR_HOST should, in theory, point to your executor container on the stacks network

yeah what i mean is

hm

_APP_EXECUTOR_HOST=http://executor/v1 didn't work for me; Could not resolve host: executor with status code

so executor is working fine now?

so I had to revert it

Yeah, that makes sense, I've had issues with the executor too, usually the EXECUTOR_HOST needs to be the internal DNS name of the Executor on the Appwrite stack as far as I am aware, but I will wait for Steven or someone to chime in

Here's what happened: Executor was working fine, along with my function. Today my function quit working with error

I restarted appwrite and appwrite-executor booted back up, but now I get file not found when executing already-deployed functions or trying to deploy new functions

Is this a self host in terms of not using anything to manage it?

I've also tried multiple dart runtimes

Yes

hm, you could consider getting another instance up and seeing if the second instance does the same thing because you can export and import data now

or import the data to the cloud, run your program there temporarily and debug the other, a few options to test out different stacks thanks to the import/migrate

did you follow all the steps in https://discord.com/channels/564160730845151244/1156583888261484634 ?

that's a message in the other thread

How did you upgrade?

1.4.3 ---> 1.4.4

Are your storage environment variables correct?

I just tried updating to

And did docker down.. docker up -d

No success