Appwrite Storage error 503s for automated temporary uploads and downloads for AI tool (Feedback)
- 0
- Cloud
I'm facing error 503s from Appwrite after about 5-6 seconds of making AI requests from my tool with images and files above 20MB (=> not inline base64 used, but temporary uploads to Appwrite Storage, retrieval and let the AI provider's APIs download the object via the Storage URL a few seconds after). Didn't get it working, tried everything and eventually ended up switching to Cloudflare Storage (in addition to having to switch to Cloudflare Workers since Appwrite still lacks SSE support that Vercel/Cloudflare/Supabase have), but I would still like to use Appwrite Storage eventually. Seems like a bug / security/spam-prevention or bot-protection measurement on Appwrite's end. The Node.js function has enough RAM and CPUs. Permisssions are sufficient as well with even an API key used for the function. Appwrite is currently not really usable for anything AI sadly. Is this another known limitation of Appwrite?
Recommended threads
- Weird permission failure
when creating an account I use following methods: ``` Future<void> register(String email, String password, String username) async { final user = await accoun...
- Flutter Android oAuth is no more working
I currently don't get the oAuth login to work in flutter android. it works on ios and on web. but when try to use it on Android, i get to the point where the ca...
- [SOLVED] Paused project can't activate
~~Error: **Invalid console fingerprint** last usage: **daily** no idea why it's paused tried relogin~~ tried relogin in incognito mode and it asked for email...