I don't now. I'm using betterauth.
My project works on localhost but in POST 500 /api/auth/sign-out
SERVER_ERROR: ,Error: Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler. This is a limitation of Cloudflare Workers which allows us to improve overall performance. (I/O type: Writable)
4 Replies
Hi @Prestgg. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
It looks like you're encountering an error when deploying your Nuxt application to Cloudflare Workers. This error is specific to Cloudflare's environment limitations.
The error message indicates that you're trying to perform I/O operations across different request contexts, which is not allowed in Cloudflare Workers. This typically happens when you try to access request/response objects or streams from one request handler in another request handler.
This is a common issue when deploying applications to Cloudflare Workers due to their architecture. Cloudflare Workers has specific limitations around I/O operations to improve performance.
Here are some potential solutions:
1. Make sure you're not sharing request or response objects between different handlers.
2. If you're using middleware that accesses response headers or bodies, ensure they complete their operations within their own request context.
3. For authentication in Cloudflare Workers, you might need to use a different approach:
- Consider using cookies instead of localStorage for authentication tokens when working with Cloudflare as mentioned here
- Use Cloudflare-specific storage solutions like KV or R2 for session management as described here
4. If you're using WebSockets, make sure you're using the proper adapter for Cloudflare as shown here
For a proper implementation in Cloudflare Workers, you might need to adapt your authentication flow to work within Cloudflare's constraints. The H3 adapter for Cloudflare might also be helpful in properly structuring your application for this environment.
If you need more specific help, please share your authentication implementation code, particularly how you're handling the sign-out process.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
<@582277346934128651> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
But also error 5
POST 503 /api/auth/sign-in/email
Error: Worker exceeded CPU time limit.
Hey this is because of hashing algorithm.
It takes up too much cpu even in paid plans (it’s a cf issue/decision) only work around would to make your own plug-in better auth hasher that is less secure.