
Yes I had it enabled!

On it

if (App::getEnv('_APP_OPTIONS_FORCE_HTTPS', 'disabled') === 'enabled') { // Force HTTPS
The default is disabled
so you can remove it altogether - in the new appwrite-functions container

Removed and worked like charm.

馃憤

I can't thank you enough. You'll be remembered.

So cool

Glad it worked <a:ablobattention:492776678742032395>

In the Appwrite console, from the duration column, I can see that it takes around the same amount of time as before during the execution. Is it normal or should it have taken less time?

How complex is the function? If you don't cross the max workers in a given time then it should take the same, as this is just Appwrite.
The benchmarks that you can see in the issue are showing faster times when Appwrite is out of workers.
So if you have 10 concurrent connection, then you won't notice any different. But, if you more connection then your available workers - 12 in your case - then you'll see a significant changes - some time even crucial ones as you can see in the Benchmark table.

What this semi-solution guarantee is that you'll never ran out of workers, and all of your request will be respected - maybe no in the same second but eventually - all of them will get execute.

The function brings 20 posts. Then for each post, it also brings the user's information from another collection.

That is all I need. I just don't want it to fail, that's all.

Exactly

Again, many many thanks to you. It's 5 AM in the morning and I feel so relieved.

Thanks to this

I would just do this client side 馃槄

But what you do in case you need it to be done through a server sdk?

Function then, ya

[SOLVED] Cloud functions fail under little to moderate load

Hello! Sorry to disturb you, @Binyamin
I was using your tunneling method with great success. But I just updated Appwrite to the latest version, 1.4.4. Now I get an error that saysThis domain is not connected to any Appwrite resource yet. Please configure custom domain or function domain to allow this request.
, which is obviously implying http://appwrite-functions
that I have in my functions. How do I fix it?
I tried adding this domain in the Appwrite console but it can't seem to pass the certificate validations for obvious reasons.

If anyone could help it'd be very awesome.

I think that's because the new changes in the new Appwrite functions

Binyaming will guide you better than me 馃槄

Check this https://discord.com/channels/564160730845151244/1149007631223107665/1149330021777932398
You'll need to set the _APP_DOMAIN_FUNCTIONS
as appwrite-functions
Recommended threads
- 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"...
- Function running in cloud but not locall...
Hi everyone, I have an appwrite function which is on python3.12 runtime. I have a library (hnswlib) which builds wheels during installation. This works on appwr...
- Permissions for bulk operation
Hi team, I have a question: 鈥淚n the databases.createDocuments bulk API, can I set document-level permissions? If yes, how exactly should I include the permissio...
