Same issue here. I’m on Washington region (default). No functions.
Same here from ARG
middleware to proxy migration worked for my nodejs project
1 Like
Same here from Indonesia.
Function region: iad1
Same here, fra1 region (EU). Any workaround?
1 Like
Thanks for sharing this. Please upvote this post to get more eyeballs.
Same for me
same problem, EU area
for me running npx @next/codemod@canary middleware-to-proxy . seems to work
There was this 1 build that was success. After that I did some changes in the code, and then deployed again. The build is failing but passing on local system. I tried to debug this, but nothing helped. To test that is it because of me or not, I re-deployed the build that was earlier successful on vercel, but now that build is also failing. Not, sure why this is happening. Any suggestion on what i can try to debug this ? this is what i am getting in error. Build is success, but deploying the build its failing.
I am already using proxy.ts and this is failing for me, so not sure that is a direct fix
1 Like
same for me
I was working on ProxyBase OpenClaw Skill — Unlock the Internet for Your AI part and tried to deploy my feature branch, but ended up with this error.
My latest Production build is fine when I redeploy it, a new code change is failing to deploy to Preview though.
Having the same issue here.
Temporary fix it by rename into middleware.disabled.ts
I have the same error as well. Running convex with next.js
same issue for me in the UK,
i think its related with middleware (changed to proxy) and experimental Next.js models
same issue here
