Hello. Using Wasabi as storage.
Coded function in dart. Even simple functions cant be deployed.
Runtime: Dart - 2.17 When trying to deploy and activate any function: Logs: No logs recorded Error: Could not resolve host: .s3.eu-central-2.wasabisys.com
When trying to activate: Build with the requested ID is building and not ready for execution.
Also tried to make uploaded file public access in Wasabi console.
Hi
Can you let me know the memory assigned?
You can check _APP_FUNCTIONS_MEMORY
_APP_FUNCTIONS_MEMORY - 0
Can you try setting it to 2048 and try again?
Did that, Nothing chaned
ok, allow me to look into this further since this is not a memory issue
Thank u)
Hi again
So
As you can see in your host the bucket is missing
So what you need to do is
Check your environment variables for the wasabi bucket and once you have it you can append that to your host
Thank you, for ur response. You mean:
_APP_STORAGE_WASABI_BUCKET
_APP_STORAGE_WASABI_REGION And others?
If so, they are all done, and I’m able to upload and manipulate any files in wasabi storage by sdk
If so, they are all done, and I’m able to upload and manipulate any files in wasabi storage by sdk What do you mean by this?
Earlier, there was error on appwrite side, so I wasn’t able to upload any files to wasabi throw appwrite console. This was fixed with new update. So, I was thinking, may be something related to this error?
All env variables a set correctly. So it uploaded tz archive to wasabi. But nothing happens after. Function not deploying and not activated
Does docker compose exec appwrite-executor vars show the right wasabi values?
Recommended threads
- Appwrite-injected variables are not avai...
I am using rust-1.83 as a runtime and try to access APPWRITE_FUNCTION_API_ENDPOINT or APPWRITE_FUNCTION_API_KEY during runtime. Both are not set during my execu...
- Functions in cloud console not works
please advise as all of my runing functions on Appwrite console was working before , but now it give this error [Invalid `headers` param: Value must be a valid...
- [SOLVED] Production down - createExecuti...
Hey, Since 1.9.6 rollout in fra (~17:00 UTC, 14 Aug), POST /v1/functions/{functionId}/executions returns a 400 whenever the body includes an empty headers ob...