No, on vps server
regardless, 500 means there's an issue with the server. easiest way to troubleshoot, is to restart the appwrite instance
have you tried that?
docker compose down
docker compose up -d
Let me try
yep
After restart the appwrite instance, i have same issues
is it only the functions page? or other pages too?
Can you open the browser network logs, try to reproduce the issue, and see what endpoint resulted in 500?
Only settings Functions
sure
So the variables API returned the 500 error.
Would you please look through your docker logs for the appwrite container to find the 500 error for the variables endpoint?
How do I proceed?
Run this command on your VPS server where appwrite is hosted
docker compose logs appwrite
and check if you see any errors.
Try this just after you have reproduced the error
ok
hmm i haven't seen that error before...did you maybe have an older version of appwrite and then not run the migrate command fully when upgrading?
Maybe, but when I do an update I always run the migration command.
maybe it didn't run correctly?
What can I do? Run the migration command again?
What version are you on now?
1.2.1
You can try to backup and then run:
docker compose exec appwrite exec migrate version=1.0.3
In fact I just made an observation, I noticed that it is only the projects that existed before the migration that are affected. While the new ones work without any problem.
Recommended threads
- Invalid document structure: missing requ...
I just pick up my code that's working a week ago, and now I got this error: ``` code: 400, type: 'document_invalid_structure', response: { message: 'Inv...
- custom domain with CloudFlare
Hi all, it seems that CloudFlare has blocked cross-domain CNAME link which made my app hostname which is in CloudFlare, unable to create a CNAME pointing to clo...
- Custom emails
What happen if I use a third party email provider to customize my emails and my plan run out of emails/month? Appwrite emails are used as fallback sending emai...