Build timeout when trying to deploy Next.js #1427

thomasgauvin · 2024-03-07T14:54:14Z

I'm creating this issue to collect issues related to deploy timeouts/failed deploys for Next.js sites. I've seen a couple other threads get re-purposed into discussions for Next.js deployment issues, though they were originally intended for unrelated past deployment issues.

The asks are the following:

Create a support issue, so that we can use that channel to collect more information and assess the severity of each issue.
Deploy your Static Web Apps to West US 2 region. We have more thorough logging in that region uniquely and will be better enabled to assist.
Share your default host name, and screenshot of failing deploys here.
If standalone is enabled, turn it off and share if this has improved your deployment.

Looking forward to getting to the bottom of this, thanks everyone for the feedback!

felicksLindgren · 2024-03-08T08:50:33Z

Hi, currently having deployment issues for both Free and Standard tier Static Web Apps. Both have Location "Global". I tried with removing 'standalone' without any luck. The host name your asking for, is that the URL to the app?

krisnashaypp · 2024-03-08T13:40:09Z

I'm having this issue today, Nextjs build runs fine in github actions but when "polling on deployment" it gives up after 600 seconds and shows "Deployment Failure Reason: Web app warm up timed out. Please try again later."

thomasgauvin · 2024-03-08T14:29:03Z

@felicksLindgren, yes that's correct, the URL to the app. @krisnashaypp any chance you can also share your URL?

Please deploy your workloads to West US 2 (in the Advanced tab of the create blade) if you are able to, we have more thorough logs in that region.

Also, can you open support tickets so we can use that channel for more direct communication?

felicksLindgren · 2024-03-11T07:24:38Z

@thomasgauvin Where do you want to receive that support ticket? Here in GitHub as a seperate issue, or via Azure as a support request?

krisnashaypp · 2024-03-11T15:25:53Z

@thomasgauvin the URL is lively-grass-00c911a03.3.azurestaticapps.net

I didn't have permission in Azure to create support tickets but I've sent it up the chain.

thomasgauvin · 2024-03-11T15:39:19Z

@felickLindgren, an Azure support request would be ideal so we can collect the information about your resource.

@krisnashaypp thanks for sharing, I'll relay this over to our team to look into it

adziusmaster · 2024-03-11T16:23:51Z

we are facing exactly the same issue for the whole day today, our host: https://ashy-desert-090506203.4.azurestaticapps.net/

felicksLindgren · 2024-03-12T09:16:35Z

@felickLindgren, an Azure support request would be ideal so we can collect the information about your resource.

@krisnashaypp thanks for sharing, I'll relay this over to our team to look into it

@thomasgauvin Here's a Support Request number for one of our affected resources: 2403120050001398

krisnashaypp · 2024-03-12T09:18:20Z

@thomasgauvin
My support ticket 2403120050001076

Thanks!

AaronCTech · 2024-03-12T15:17:36Z

Just an update: this issue is still occurring with our build.

Awaiting approvals to cross-deploy to US West 2 and pending support issue creation.

annikel · 2024-03-12T20:12:49Z

To determine if configured routing might be blocking specific health checks conducted during deployment, could you all please help us investigate the issue by creating a directory within your public folder named .test and include a health check file named health.html within it (public/.test/health.html)? Afterward, start up the application locally and verify if this file is reachable via the path /.test/health.html. If it's inaccessible, please investigate whether the routing rules in for example your middleware might be altering or blocking that path.

AaronCTech · 2024-03-12T20:18:39Z

@annikel

We do have zero-trust auth middleware that would absolutely block this.

Could you provide the specific files/folders that should remain visible, assuming it's not .test/health?

Edit: we did see Thomas's older comment in another issue regarding /public/.swa/health.html, and an early attempt at allowing access to that file did not solve the issue last week :\

annikel · 2024-03-12T20:26:03Z

@AaronCTech In that case please make sure to allow health checks to /.swa/health.html

AaronCTech · 2024-03-12T20:46:21Z

The devil's in the details; this worked!

Note: .swa/health is not the same as .swa/health.html :)

TL;DR: allow .swa/health.html requests through your middleware.

IgnacioAguirre · 2024-03-13T15:07:48Z

Hi @AaronCTech,
Would you mind to give more details regarding how did you remove authentication on route ".swa/health.html".
Were you using matchers as mentioned in https://next-auth.js.org/configuration/nextjs#middleware ?

cerimorse · 2024-03-13T17:22:14Z

Hey @IgnacioAguirre, you can definitely make use of the Next.js matcher in middleware.js. You can use regex, so negative lookaheads would work well here. There's a few things we didn't want matched in our app so we just added the .swa path to our matcher config. If it's just .swa you want to exclude then you can do something like this:

export const config = {
  matcher: [
    /*
     * Match all request paths except for the ones starting with:
     * - .swa (Azure static web apps)
     */
    '/((?!.swa).*)',
  ],
}

Our builds started working again this morning after adding .swa to the matcher so hopefully this is useful!

ps thanks @annikel and @AaronCTech for the tips and solution!

mateubo · 2024-03-15T07:40:07Z

Hi @thomasgauvin,
Since last Thursday, we suddenly have been facing many issues with all ours Azure Static Web Apps (~20 instances), one of them being deployment timeouts.
Our support ticket TrackingID#2403080050002476 is mainly about the apps randomly being unavailable for seconds/minutes/even an hour, and engineers have been unable to resolve this so far.

But as for the deployment timeout. I tried disabling output: 'standalone', but this causes the Oryx build to fail:

Installing production dependencies in '/7ee63406-bafe-445c-8668-bf980c30bca5-swa-oryx/app/.oryx_prod_node_modules'...

Running 'yarn workspaces focus --all || yarn install --production'...

node:internal/modules/cjs/loader:1137
  throw err;
  ^

Error: Cannot find module '/7ee63406-bafe-445c-8668-bf980c30bca5-swa-oryx/app/.oryx_prod_node_modules/.yarn/releases/yarn-classic.cjs'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)
    at Module._load (node:internal/modules/cjs/loader:975:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.19.1
node:internal/modules/cjs/loader:1137
  throw err;
  ^

Error: Cannot find module '/7ee63406-bafe-445c-8668-bf980c30bca5-swa-oryx/app/.oryx_prod_node_modules/.yarn/releases/yarn-classic.cjs'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)
    at Module._load (node:internal/modules/cjs/loader:975:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.19.1


---End of Oryx build logs---
Oryx has failed to build the solution.

mburumaxwell · 2024-03-19T07:16:24Z

Picked the starter (https://github.com/staticwebdev/nextjs-hybrid-starter) and set it up with WestEurope which failed after 600 seconds. It did work with WestUS2 after 226 seconds.

@thomasgauvin is there any timeline or estimate on having this working in West Europe?

RenMen · 2024-03-19T08:17:01Z

Thanks annikel. The build time out error resolved after adding .swa matcher in middleware.

mateubo · 2024-03-19T11:28:32Z

@annikel we do not have any auth middleware, and /.swa/health.html is reachable. We have Static Web Apps deployed in West Europe, and we need to rerun the deployments (AzureStaticWebApp@0 DevOps task) multiple times until it finally comes through

thomasgauvin · 2024-03-20T00:40:52Z

Thank you all for the feedback, opening support issues and sharing your default hostnames/site identifiers, we are going to be looking into this.

aKroken · 2024-03-20T09:22:06Z

Hi @thomasgauvin, Since last Thursday, we suddenly have been facing many issues with all ours Azure Static Web Apps (~20 instances), one of them being deployment timeouts. Our support ticket TrackingID#2403080050002476 is mainly about the apps randomly being unavailable for seconds/minutes/even an hour, and engineers have been unable to resolve this so far.

But as for the deployment timeout. I tried disabling output: 'standalone', but this causes the Oryx build to fail:

Installing production dependencies in '/7ee63406-bafe-445c-8668-bf980c30bca5-swa-oryx/app/.oryx_prod_node_modules'...

Running 'yarn workspaces focus --all || yarn install --production'...

node:internal/modules/cjs/loader:1137
  throw err;
  ^

Error: Cannot find module '/7ee63406-bafe-445c-8668-bf980c30bca5-swa-oryx/app/.oryx_prod_node_modules/.yarn/releases/yarn-classic.cjs'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)
    at Module._load (node:internal/modules/cjs/loader:975:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.19.1
node:internal/modules/cjs/loader:1137
  throw err;
  ^

Error: Cannot find module '/7ee63406-bafe-445c-8668-bf980c30bca5-swa-oryx/app/.oryx_prod_node_modules/.yarn/releases/yarn-classic.cjs'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)
    at Module._load (node:internal/modules/cjs/loader:975:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.19.1


---End of Oryx build logs---
Oryx has failed to build the solution.

Hello! We have experienced exactly the same scenario as you.
It started on Tuesday 12 March.
We find that static web apps go to sleep and take anywhere from seconds to minutes to work.
Also experience that our pipeline step AzureStaticWebApp@0 fails when the static web app is "sleeping". Otherwise it works.
Have you found anything out around this problem?
We are considering setting up an App service instead and see if it works better.

thomasgauvin mentioned this issue Mar 7, 2024

Oryx Pipeline Timeout - deploying Next.js #1035

Closed

thomasgauvin mentioned this issue Mar 11, 2024

Upload Timed Out. Unsure if deployment was successful or not. #942

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Build timeout when trying to deploy Next.js #1427

Build timeout when trying to deploy Next.js #1427

thomasgauvin commented Mar 7, 2024 •

edited

felicksLindgren commented Mar 8, 2024 •

edited

krisnashaypp commented Mar 8, 2024

thomasgauvin commented Mar 8, 2024

felicksLindgren commented Mar 11, 2024

krisnashaypp commented Mar 11, 2024

thomasgauvin commented Mar 11, 2024

adziusmaster commented Mar 11, 2024 •

edited

felicksLindgren commented Mar 12, 2024 •

edited

krisnashaypp commented Mar 12, 2024

AaronCTech commented Mar 12, 2024

annikel commented Mar 12, 2024

AaronCTech commented Mar 12, 2024 •

edited

annikel commented Mar 12, 2024 •

edited

AaronCTech commented Mar 12, 2024

IgnacioAguirre commented Mar 13, 2024 •

edited

cerimorse commented Mar 13, 2024 •

edited

mateubo commented Mar 15, 2024

mburumaxwell commented Mar 19, 2024

RenMen commented Mar 19, 2024 •

edited

mateubo commented Mar 19, 2024

thomasgauvin commented Mar 20, 2024

aKroken commented Mar 20, 2024

Build timeout when trying to deploy Next.js #1427

Build timeout when trying to deploy Next.js #1427

Comments

thomasgauvin commented Mar 7, 2024 • edited

felicksLindgren commented Mar 8, 2024 • edited

krisnashaypp commented Mar 8, 2024

thomasgauvin commented Mar 8, 2024

felicksLindgren commented Mar 11, 2024

krisnashaypp commented Mar 11, 2024

thomasgauvin commented Mar 11, 2024

adziusmaster commented Mar 11, 2024 • edited

felicksLindgren commented Mar 12, 2024 • edited

krisnashaypp commented Mar 12, 2024

AaronCTech commented Mar 12, 2024

annikel commented Mar 12, 2024

AaronCTech commented Mar 12, 2024 • edited

annikel commented Mar 12, 2024 • edited

AaronCTech commented Mar 12, 2024

IgnacioAguirre commented Mar 13, 2024 • edited

cerimorse commented Mar 13, 2024 • edited

mateubo commented Mar 15, 2024

mburumaxwell commented Mar 19, 2024

RenMen commented Mar 19, 2024 • edited

mateubo commented Mar 19, 2024

thomasgauvin commented Mar 20, 2024

aKroken commented Mar 20, 2024

thomasgauvin commented Mar 7, 2024 •

edited

felicksLindgren commented Mar 8, 2024 •

edited

adziusmaster commented Mar 11, 2024 •

edited

felicksLindgren commented Mar 12, 2024 •

edited

AaronCTech commented Mar 12, 2024 •

edited

annikel commented Mar 12, 2024 •

edited

IgnacioAguirre commented Mar 13, 2024 •

edited

cerimorse commented Mar 13, 2024 •

edited

RenMen commented Mar 19, 2024 •

edited