Vercel deployment failure with internal error during deploying outputs phase

Help
, ,
199

I’m also expriencing same issue.

200

!!!MIGRATE FROM MIDDLEWARE TO PROXY for nextjs - WILL FIX IT!!!

201

Working for me in setting region to france (cdg1)

202

renaming middleware.ts to proxy.ts worked for me.

203

I didn’t change anything meaningful but getting the same error

204

It’s working well now!:slightly_smiling_face:

205

Thanks, my deploy is working now.

206

Thanks! Build is working again!

207

It’s working :sob:

208

Glad it’s working!

Latest update:

Due to operational issues in the dxb1 region, traffic is currently re-routed to bom1. Additionally, dxb1 is currently unavailable as a Function Region for new deployments.

209

I’m experiencing the same issue and I’m not in Dubai. Is my issue related or not?

210

The issue has been fixed. I’m now able to deploy the app successfully.

211

I think it’s fixed in some places. It works for me now.

212

I am also having this issue.
What I do not understand is how they could design a platform to be so fragile.
And now that War has broken out, this kind of thing is going to make Vercel a less attractive solution.
Anyone have any alternatives to Vercel in production?

214

:backhand_index_pointing_right: Upgrading NextJS to latest solved my problem