Some edge functions returns a random 405 error

[mattiaz9]

Summary

In the past few days some edge functions (which are POST requests) stopped working returning a 405 error.

This is weird because is not a Method not allowed problem. In fact, looking at the logs, it turned out to be a 500 internal error of the edge function:

[POST] /api/documents/save?nxtPparams=documents%2Fsave
reason=INTERNAL_EDGE_FUNCTION_UNHANDLED_ERROR, status=500, upstream_status=500, user_error=false

It seems to be related to only edge runtime, because switching to runtime = 'nodejs' fixed the issue.

I also put some logs inside the POST handler and none of those were printed, probably meaning the endpoint was never called in the first place.

Example

No response

Steps to Reproduce

It's not easy reproducible. It seems to happen only for POST request on the edge runtime, but not every one have this issue.

[robinrogowski]

This happens on our implementation as well. Keep us posted if you find anything.

[amyegan]

There are some Edge Functions limitations that could be causing errors. A common one is that many Node.js APIs are not available. You can find a more complete list in the Edge Function docs at https://vercel.com/docs/concepts/functions/edge-functions/limitations#

I also found a few other posts about 405 errors which could be related to your situation:

• 405 (Method Not Allowed) when using server actions next.js#51984
• 405 Error in Browser Console When Sending POST Request Via Form (no redirects) #3081
• NEXT.js@latest net::ERR_ABORTED 405 #3138

[mattiaz9]

I don't think that is the case.

The local environment should simulate the edge runtime APIs, so it should also crash locally, which is not the case with my issue.
Also my endpoint is a catch all segment, meaning there are many other endpoints that works just fine that are in the same bundled function.

The weird thing is that it doesn't even enter the POST handler.

[poweroutlet2]

Did you ever find the cause of this or a solution? Running into the same problem

[mattiaz9]

nope! my guess it might be some internal edge runtime bug. For the moment I have to stick with nodejs.

[Yidadaa]

I also encountered the same problem, which is very strange. It seems to be caused by the unstable operation of the Edge Runtime, and there is no Error Log to trace back to!

[shardbearer-shri]

Has anyone found a solution to this? Iam still facing this issue with the edge runtime

[mdatsev]

I was getting the same random 405 responses and I was not even using edge runtime, just plain node runtime.

What I noticed though is that I had used up 94% of my free plan bandwidth.

Once I upgraded to pro and redeployed the errors went away.

[ymc9]

Same here, getting random 405 response on edge runtime with next.js and vercel postgres.

reason=INTERNAL_EDGE_FUNCTION_INVOCATION_FAILED, status=500, upstream_status=500, user_error=false

[amyegan]

What version of Next.js does your project use?

[ymc9]

I'm using Next.js 14.1.4

[robinrogowski]

We recently upgraded to Next 13.2.0 to start a migration by using the app router for some API routes that we have.

…

________________________________ From: Amy ***@***.***> Sent: Monday, April 8, 2024 2:09 PM To: vercel/community ***@***.***> Cc: Robin Rogowski ***@***.***>; Manual ***@***.***> Subject: Re: [vercel/community] Some edge functions returns a random 405 error (Discussion #3475) External: What version of Next.js does your project use? — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/orgs/vercel/discussions/3475*discussioncomment-9050398__;Iw!!IfJP2Nwhk5Z0yJ43lA!MX3lAdKIgTGYFC8ZGkfCwwseEOpN9hFozwIVV-dqe2eo4Zetbz7rnvLzv0AZlw5mnws017zpv1nZIy5C6nBqmSMl96tGxQ$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AHTK6MDN3CZNIZZNJ3X5AFDY4LTOBAVCNFSM6AAAAAA3BBS5C6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TANJQGM4TQ__;!!IfJP2Nwhk5Z0yJ43lA!MX3lAdKIgTGYFC8ZGkfCwwseEOpN9hFozwIVV-dqe2eo4Zetbz7rnvLzv0AZlw5mnws017zpv1nZIy5C6nBqmSPP6jVBbA$>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>