at=error code=H10 desc="App crashed" status: 503

[NaseerAkbari]

What is the problem?

I have published the app on Heroku and it just showed me such errors.

Paste all your error logs here:

at=error code=H10 desc="App crashed" method=GET path="/" host=naseer-second.herokuapp.com request_id=422e227a-20c7-4efa-a402-5b8775bebbfe fwd="46.125.250.63" dyno= connect= service= status=503 bytes= protocol=https

Paste all relevant code snippets here:

firs logs are here:

2021-06-01T18:56:08.484038+00:00 app[web.1]: npm ERR! 
2021-06-01T18:56:08.484227+00:00 app[web.1]: npm ERR! Failed at the nsr@1.0.0 start:production script.
2021-06-01T18:56:08.484410+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-06-01T18:56:08.495227+00:00 app[web.1]: 
2021-06-01T18:56:08.495687+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2021-06-01T18:56:08.495955+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2021-06-01T18_56_08_485Z-debug.log
2021-06-01T18:56:08.589617+00:00 heroku[web.1]: Process exited with status 1
2021-06-01T18:56:08.678882+00:00 heroku[web.1]: State changed from starting to crashed
2021-06-01T18:56:11.043046+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=naseer-second.herokuapp.com request_id=6c2c21e8-d4ab-4ea2-9662-cad0bca56fcf fwd="46.125.250.63" dyno= connect= service= status=503 bytes= protocol=https
2021-06-01T18:56:43.130273+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=naseer-second.herokuapp.com request_id=d4508bbd-6ada-4d2e-bea6-3d54b119df50 fwd="46.125.250.63" dyno= connect= service= status=503 bytes= protocol=https

all logs here.

-----> Building on the Heroku-20 stack
-----> Determining which buildpack to use for this app
-----> Node.js app detected
       
-----> Creating runtime environment
       
       NPM_CONFIG_LOGLEVEL=error
       NODE_VERBOSE=false
       NODE_ENV=production
       NODE_MODULES_CACHE=true
       
-----> Installing binaries
       engines.node (package.json):  unspecified
       engines.npm (package.json):   unspecified (use default)
       
       Resolving node version 14.x...
       Downloading and installing node 14.17.0...
       Using default npm version: 6.14.13
       
-----> Installing dependencies
       Prebuild detected (node_modules already exists)
       Rebuilding any native modules
       
       > @prisma/client@2.20.1 postinstall /tmp/build_649c92f5/node_modules/@prisma/client
       > node scripts/postinstall.js
       
       Prisma schema loaded from db/schema.prisma
       
       ✔ Generated Prisma Client (2.20.1) to ./node_modules/@prisma/client in 207ms
       You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
       ```
       import { PrismaClient } from '@prisma/client'
       const prisma = new PrismaClient()
       ```
       
       > blitz@0.36.3 postinstall /tmp/build_649c92f5/node_modules/blitz
       > node scripts/postinstall.js
       
       
       > esbuild@0.11.23 postinstall /tmp/build_649c92f5/node_modules/esbuild
       > node install.js
       
       
       > @prisma/engines@2.19.0-39.c1455d0b443d66b0d9db9bcb1bb9ee0d5bbc511d postinstall /tmp/build_649c92f5/node_modules/@prisma/engines
       > node download/index.js
       
       
       > core-js@3.13.1 postinstall /tmp/build_649c92f5/node_modules/core-js
       > node -e "try{require('./postinstall')}catch(e){}"
       
       
       > sodium-native@3.2.1 install /tmp/build_649c92f5/node_modules/sodium-native
       > node-gyp-build "node preinstall.js" "node postinstall.js"
       
       
       > core-js-pure@3.13.1 postinstall /tmp/build_649c92f5/node_modules/core-js-pure
       > node -e "try{require('./postinstall')}catch(e){}"
       
       
       > prisma@2.20.1 preinstall /tmp/build_649c92f5/node_modules/prisma
       > node scripts/preinstall-entry.js
       
       
       > prisma@2.20.1 install /tmp/build_649c92f5/node_modules/prisma
       > node scripts/install-entry.js
       
       
       > @prisma/engines@2.20.0-26.60ba6551f29b17d7d6ce479e5733c70d9c00860e postinstall /tmp/build_649c92f5/node_modules/prisma/node_modules/@prisma/engines
       > node download/index.js
       
       @prisma/client@2.20.1 /tmp/build_649c92f5/node_modules/@prisma/client
       @prisma/engines-version@2.20.0-26.60ba6551f29b17d7d6ce479e5733c70d9c00860e /tmp/build_649c92f5/node_modules/@prisma/engines-version
       @types/react@17.0.8 /tmp/build_649c92f5/node_modules/@types/react
       @types/prop-types@15.7.3 /tmp/build_649c92f5/node_modules/@types/prop-types
       @types/scheduler@0.16.1 /tmp/build_649c92f5/node_modules/@types/scheduler
       csstype@3.0.8 /tmp/build_649c92f5/node_modules/csstype
       @types/preview-email@2.0.0 /tmp/build_649c92f5/node_modules/@types/preview-email
       @types/nodemailer@6.4.2 /tmp/build_649c92f5/node_modules/@types/nodemailer
       @types/node@15.6.1 /tmp/build_649c92f5/node_modules/@types/node
       blitz@0.36.3 /tmp/build_649c92f5/node_modules/blitz
       @blitzjs/babel-preset@0.36.3 /tmp/build_649c92f5/node_modules/@blitzjs/babel-preset
       @babel/helper-module-imports@7.13.12 /tmp/build_649c92f5/node_modules/@babel/helper-module-imports
       @babel/types@7.14.4 /tmp/build_649c92f5/node_modules/@babel/types
       @babel/helper-validator-identifier@7.14.0 /tmp/build_649c92f5/node_modules/@babel/helper-validator-identifier
       to-fast-properties@2.0.0 /tmp/build_649c92f5/node_modules/to-fast-properties
       babel-plugin-superjson-next@0.3.0 /tmp/build_649c92f5/node_modules/babel-plugin-superjson-next
       hoist-non-react-statics@3.3.2 /tmp/build_649c92f5/node_modules/hoist-non-react-statics
       react-is@16.13.1 /tmp/build_649c92f5/node_modules/react-is
       @blitzjs/cli@0.36.3 /tmp/build_649c92f5/node_modules/@blitzjs/cli
       @blitzjs/display@0.36.3 /tmp/build_649c92f5/node_modules/@blitzjs/display
       @blitzjs/config@0.36.3 /tmp/build_649c92f5/node_modules/@blitzjs/config
       esbuild@0.11.23 /tmp/build_649c92f5/node_modules/esbuild
       fs-extra@9.1.0 /tmp/build_649c92f5/node_modules/fs-extra
       at-least-node@1.0.0 /tmp/build_649c92f5/node_modules/at-least-node
       graceful-fs@4.2.6 /tmp/build_649c92f5/node_modules/graceful-fs
       jsonfile@6.1.0 /tmp/build_649c92f5/node_modules/jsonfile
       universalify@2.0.0 /tmp/build_649c92f5/node_modules/universalify
       pkg-dir@5.0.0 /tmp/build_649c92f5/node_modules/pkg-dir
       find-up@5.0.0 /tmp/build_649c92f5/node_modules/find-up
       locate-path@6.0.0 /tmp/build_649c92f5/node_modules/locate-path... (93 KB left)

What are detailed steps to reproduce this?

1.is based on the tutorial

Run blitz -v and paste the output here:

latest version

Please include below any other applicable logs and screenshots that show your problem:

[flybayer]

Like I said in Discord, I need to see more runtime logs to see what the actual error is. The build log looks good.

Double check to make sure you followed all the heroku deploy instructions in our docs exactly including adding all required environment variables.

Try running blitz build && blitz start locally.

[reggie3]

@flybayer

These are the logs from a fresh deployment to Heroku:

2021-07-25T14:05:57.239050+00:00 app[release.3447]:     Error: Cannot find module 'prisma'
2021-07-25T14:05:57.239093+00:00 app[release.3447]:     Require stack:
2021-07-25T14:05:57.239094+00:00 app[release.3447]:     - /app/noop.js
2021-07-25T14:05:57.239094+00:00 app[release.3447]:     Code: MODULE_NOT_FOUND
2021-07-25T14:05:57.406945+00:00 heroku[release.3447]: Process exited with status 1
2021-07-25T14:05:57.517752+00:00 heroku[release.3447]: State changed from up to complete
2021-07-25T14:05:59.463239+00:00 app[api]: Release v7 command failed by user reggie3@protonmail.com
2021-07-25T14:06:02.000000+00:00 app[api]: Build succeeded
2021-07-25T14:06:19.653548+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=blitz-app-two.herokuapp.com request_id=7a02b149-2596-42ee-b2df-f761401ec65b fwd="47.132.235.53" dyno= connect= service= status=503 bytes= protocol=https
2021-07-25T14:06:20.140582+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=blitz-app-two.herokuapp.com request_id=3a1d82ca-c21c-4212-9895-29a3f7f88d79 fwd="47.132.235.53" dyno= connect= service= status=503 bytes= protocol=https

I followed the deployment directions here: https://blitzjs.com/docs/deploy-heroku.
I add a SESSION_SECRET_KEY since I was getting a different error without it. The SESSION_SECRET_KEY exists in my .env file.

Running blitz build && blitz start results in no errors, and I am able to run the locally successfully. Here is the end of the output for that command. Please let me know if you need more:

Here is the entirety of my console when running git push heroku main

λ git push heroku main

> blitz-app-two@1.0.0 lint C:\Users\rej_i\OneDrive\Development\blitz-app-two
> eslint --ignore-path .gitignore --ext .js,.ts,.tsx .


C:\Users\rej_i\OneDrive\Development\blitz-app-two\app\pages\index.tsx
  57:11  warning  Do not use <img>. Use Image from 'next/image' instead. See https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element

✖ 1 problem (0 errors, 1 warning)


> blitz-app-two@1.0.0 test C:\Users\rej_i\OneDrive\Development\blitz-app-two
> jest

 PASS   SERVER  app/auth/mutations/forgotPassword.test.ts (10.538 s)
 PASS   SERVER  app/auth/mutations/resetPassword.test.ts (7.109 s)

Test Suites: 1 skipped, 2 passed, 2 of 3 total
Tests:       1 skipped, 3 passed, 4 total
Snapshots:   0 total
Time:        23.815 s
Ran all test suites in 2 projects.
Enumerating objects: 26, done.
Counting objects: 100% (26/26), done.
Delta compression using up to 12 threads
Compressing objects: 100% (16/16), done.
Writing objects: 100% (18/18), 147.37 KiB | 9.82 MiB/s, done.
Total 18 (delta 5), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote: 
remote: -----> Building on the Heroku-20 stack
remote: -----> Using buildpack: heroku/nodejs
remote: -----> Node.js app detected
remote:        
remote: -----> Creating runtime environment
remote:        
remote:        NPM_CONFIG_LOGLEVEL=error
remote:        NODE_VERBOSE=false
remote:        NODE_ENV=production
remote:        NODE_MODULES_CACHE=true
remote:
remote: -----> Installing binaries
remote:        engines.node (package.json):  unspecified
remote:        engines.npm (package.json):   unspecified (use default)
remote:
remote:        Resolving node version 14.x...
remote:        Downloading and installing node 14.17.3...
remote:        Using default npm version: 6.14.13
remote:        
remote: -----> Restoring cache
remote:        - node_modules
remote:        
remote: -----> Installing dependencies
remote:        Installing node modules
remote:        
remote:        > core-js-pure@3.15.2 postinstall /tmp/build_03b4e1e5/node_modules/core-js-pure
remote:        > node -e "try{require('./postinstall')}catch(e){}"
remote:
remote:        
remote:        > esbuild@0.11.23 postinstall /tmp/build_03b4e1e5/node_modules/esbuild
remote:        > node install.js
remote:
remote:        
remote:        > sodium-native@3.2.1 install /tmp/build_03b4e1e5/node_modules/sodium-native
remote:        > node-gyp-build "node preinstall.js" "node postinstall.js"
remote:
remote:        
remote:        > core-js@3.15.2 postinstall /tmp/build_03b4e1e5/node_modules/core-js
remote:        > node -e "try{require('./postinstall')}catch(e){}"
remote:
remote:        
remote:        > @prisma/engines@2.19.0-39.c1455d0b443d66b0d9db9bcb1bb9ee0d5bbc511d postinstall /tmp/build_03b4e1e5/node_modules/@prisma/engines
remote:        > node download/index.js
remote:
remote:        
remote:        > blitz@0.38.6 postinstall /tmp/build_03b4e1e5/node_modules/blitz
remote:        > node scripts/postinstall.js
remote:
remote:        
remote:        > @prisma/client@2.27.0 postinstall /tmp/build_03b4e1e5/node_modules/@prisma/client
remote:        > node scripts/postinstall.js
remote:
remote:        Environment variables loaded from .env
remote:        Prisma schema loaded from db/schema.prisma
remote:        
remote:        ✔ Generated Prisma Client (2.27.0) to ./node_modules/@prisma/client in 129ms
remote:        You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client       
remote:        ```
remote:        import { PrismaClient } from '@prisma/client'
remote:        const prisma = new PrismaClient()
remote:        ```
remote:        
remote:        > prisma@2.27.0 preinstall /tmp/build_03b4e1e5/node_modules/prisma
remote:        > node scripts/preinstall-entry.js
remote:
remote:        
remote:        > @prisma/engines@2.27.0-43.cdba6ec525e0213cce26f8e4bb23cf556d1479bb postinstall /tmp/build_03b4e1e5/node_modules/prisma/node_modules/@prisma/engines
remote:        > node download/index.js
remote:
remote:        
remote:        > prisma@2.27.0 install /tmp/build_03b4e1e5/node_modules/prisma
remote:        > node scripts/install-entry.js
remote:
remote:        
remote:        > blitz-app-two@1.0.0 prepare /tmp/build_03b4e1e5
remote:        > husky install
remote:
remote:        husky - not a Git repository, skipping hooks installation
remote:        added 1571 packages in 42.143s
remote:        
remote: -----> Build
remote:        Running build
remote:        
remote:        > blitz-app-two@1.0.0 build /tmp/build_03b4e1e5
remote:        > blitz build
remote:
remote: - Compiling
remote: ✔ Compiled
remote:        info  - Loaded env from /tmp/build_03b4e1e5/.env
remote:        info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5 
remote:        warn  - No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
remote:        Attention: Blitz.js now collects completely anonymous telemetry regarding usage.
remote:        This information is used to shape Blitz.js' roadmap and prioritize features.
remote:        You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
remote:        https://nextjs.org/telemetry
remote:
remote:        info  - Checking validity of types...
remote:        info  - Creating an optimized production build...
remote:        info  - Compiled successfully
remote:        info  - Collecting page data...
remote:        info  - Generating static pages (0/7)
remote:        info  - Generating static pages (1/7)
remote:        info  - Generating static pages (3/7)
remote:        info  - Generating static pages (5/7)
remote:        info  - Generating static pages (7/7)
remote:        info  - Finalizing page optimization...
remote:
remote:        Page                                    Size     First Load JS
remote:        ┌ ○ /                                   4.62 kB         119 kB
remote:        ├   /_app                               0 B             114 kB
remote:        ├ ○ /404                                2.63 kB         117 kB
remote:        ├ λ /api/auth/mutations/changePassword  0 B             114 kB
remote:        ├ λ /api/auth/mutations/forgotPassword  0 B             114 kB
remote:        ├ λ /api/auth/mutations/login           0 B             114 kB
remote:        ├ λ /api/auth/mutations/logout          0 B             114 kB
remote:        ├ λ /api/auth/mutations/resetPassword   0 B             114 kB
remote:        ├ λ /api/auth/mutations/signup          0 B             114 kB
remote:        ├ λ /api/users/queries/getCurrentUser   0 B             114 kB
remote:        ├ ○ /forgot-password                    3.27 kB         117 kB
remote:        ├ ○ /login                              2.79 kB         117 kB
remote:        ├ ○ /reset-password                     3.31 kB         117 kB
remote:        └ ○ /signup                             3.32 kB         117 kB
remote:        + First Load JS shared by all           114 kB
remote:          ├ chunks/framework.e3dc62.js          43.7 kB
remote:          ├ chunks/main.2b99a2.js               27.2 kB
remote:          ├ chunks/pages/_app.cb3c0d.js         42.4 kB
remote:          └ chunks/webpack.6aa242.js            812 B
remote:
remote:        λ  (Server)  server-side renders at runtime (uses getInitialProps or getServerSideProps)      
remote:        ○  (Static)  automatically rendered as static HTML (uses no initial props)
remote:        ●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps)
remote:           (ISR)     incremental static regeneration (uses revalidate in getStaticProps)
remote:
remote:        
remote: -----> Caching build
remote:        - node_modules
remote:        
remote: -----> Pruning devDependencies
remote:        removed 132 packages and audited 1440 packages in 13.236s
remote:        
remote:        134 packages are looking for funding
remote:          run `npm fund` for details
remote:
remote:        found 2 moderate severity vulnerabilities
remote:          run `npm audit fix` to fix them, or `npm audit` for details
remote:        
remote: -----> Build succeeded!
remote: -----> Discovering process types
remote:        Procfile declares types -> release, web
remote:
remote: -----> Compressing...
remote:        Done: 114.4M
remote: -----> Launching...
remote:  !     Release command declared: this new release will not be available until the command succeeds.  
remote:        Released v7
remote:        https://blitz-app-two.herokuapp.com/ deployed to Heroku
remote:
remote: Verifying deploy... done.
remote: Running release command...
remote:
remote:     Error: Cannot find module 'prisma'
remote:     Require stack:
remote:     - /app/noop.js
remote:     Code: MODULE_NOT_FOUND
remote: Waiting for release... failed.
To https://git.heroku.com/blitz-app-two.git
   dec4e24..d67aa78  main -> main

[reggie3]

Additionally, I can successfully run npx blitz prisma migrate deploy locally

[reggie3]

link to accompanying Discord thread: https://discord.com/channels/802917734999523368/814627540232699985/868887908998856715

[roshan-sama]

My experience creating docker containers makes me think Prisma needs to be a dependency and not just a devDependency for it to work.

Based on https://discord.com/channels/802917734999523368/814627766694838293/857101460503134208, it looks like thangngoc89, and others may have been able to make this configuration work with containers? I'm going to ping them on Discord and ask. Hopefully they have a solution?

If it is the case that a certain part of our app requires the prisma module when it is not actually needed, removing that requirement will be better because adding prisma to dependencies increases the size of the container image