Execution error: general_argument_invalid

I am not sure what's going on. If I understood it right, I should be able to call my function through the domain I have set to it, but It doesn't work. I am always getting the error above.

No idea of what I am supposed to do, may you help me pls?

TL;DR

User is experiencing an "Execution error: general_argument_invalid" when trying to call a function through the domain. They are unsure of what to do. They also noticed that when deploying a new version of a function, the execute access roles are lost. User sets execution access to any role and the function responds as expected. User then runs `docker-compose down` and `docker-compose up -d` but the issue persists. It is discovered that the _APP_DOMAIN_FUNCTIONS environment variable is empty. Fixed by setting the env _APP_DOMAIN_FUNCTIONS=*.mydomain.com. Another user is experiencing the same issue on a Ubuntu 22.04

What did you pass for the body?

that env var should not match your custom function domain

can you try running this on your server where your docker-compose.yml file is?

TypeScript

CONTAINER=appwrite-mariadb

docker exec -it $CONTAINER sh -c 'mysql -uroot -p$MYSQL_ROOT_PASSWORD $MYSQL_DATABASE -e "select projectId as \"Project ID\", domain as \"Domain\", resourceType as \"Resource\", resourceId as \"Resource ID\" from _console_rules;"'

hmm that's all correct

do you have a reverse proxy in front of appwrite?

there's only appwrite running on a Ubuntu 22.04 server

Having the same issue here

Nvm, Fixed it by setting the env _APP_DOMAIN_FUNCTIONS=*.mydomain.com

@Lucas Reis, what's the domain functions env var if you run docker compose exec appwrite vars?

interesting, it's empty even though I have it set in my .env file

Did you run docker compose up -d to apply the changes?

docker-compose restart

so now I run docker-compose down and then docker-compose up -d

This won't apply changes

This does

now I see it set as _APP_DOMAIN_FUNCTIONS=*.appwrite.ssw.lol

lemme make a request to see what happens

awesome, now I have got "Execution error: No permissions provided for action 'execute'", and as expected after I set execution access to any role it responded as expected 😄

I just noticed when I deploy a new version of a function it loses the execute access roles. Is it the expected behaviour?

Are you deploying with the CLI like appwrite deploy function?

yes

I see, it's about this option right?

"execute": [],

Reply to this thread by joining our Discord

Reply on Discord