Error: Failed to launch the browser process! /tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

vercel / virtual-event-starter-kit

Open source demo that Next.js developers can clone, deploy, and fully customize for events.

https://demo.vercel.events

MIT License

2.14k stars 431 forks source link

Error: Failed to launch the browser process! /tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory #89

Open thorwebdev opened 2 years ago

thorwebdev commented 2 years ago

I'm running into and issue with the image rendering: "ERROR Error: Failed to launch the browser process! /tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md"

This answer on SO suggest to use node v 14, but not sure if that's the correct resolution. Any ideas?

Originally posted by @thorwebdev in https://github.com/vercel/virtual-event-starter-kit/issues/88#issuecomment-1181342816

thorwebdev commented 2 years ago

Fixing the node version to 14 as outlined here worked for me: https://stackoverflow.com/a/72626919/17622044

Mcastres commented 1 year ago

Having node 14 both on Vercel and package.json wasn't the fix for me. Bumping chrome-aws-lambda and puppeteer-core was the actual solution: kudos to https://stackoverflow.com/a/69493610

Victorvalenzue commented 1 year ago

Having node 14 both on Vercel and package.json wasn't the fix for me. Bumping chrome-aws-lambda and puppeteer-core was the actual solution: kudos to https://stackoverflow.com/a/69493610

Look my dependencies version and still facing the problem 😭


  "dependencies": {
    "aws-sdk": "2.1446.0",
    "aws-xray-sdk": "3.5.1",
    "chrome-aws-lambda": "10.1.0",
    "date-fns": "2.30.0",
    "puppeteer-core": "21.1.1",
    "webpack": "5.88.2",
    "winston": "3.10.0"
  },