Yes it’s on Next.js
added headers for api routes inside config as the guy in the link you provided but didn’t resolve
also I don’t think that guy found a solution to this issue either.
Not to mention this always worked fine for years and Next.js version as well as other npm remained the same.
To add to it, Vercel log of errors doesn’t display the error 405, so I can’t debug it.