Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting this weird error on Browsershot. Works fine on staginng ,but not live #144

Open
aligajani opened this issue Apr 30, 2024 · 1 comment

Comments

@aligajani
Copy link

Hammerstone\Sidecar\Exceptions\LambdaExecutionException: Lambda Execution Exception for Wnx\SidecarBrowsershot\Functions\BrowsershotFunction: "Command failed: node ./browser.cjs '-f file:///tmp/browsershot.js'
TargetCloseError: Protocol error (Page.navigate): Target closed
    at CallbackRegistry.clear (/opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:146:36)
    at CDPSessionImpl._onClosed (/opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:500:25)

@drjdr
Copy link
Contributor

drjdr commented May 1, 2024

Seems like the underlying lambda layer of browsershot has changed for this package

  • Upgrade your sidecar and sidecar-browsershot packages in composer
  • in your local .env file, make sure you change the APP_ENV to the evironment you want to fix (staging / production / live)
  • Run php artisan sidecar:deploy --activate again, this should deploy a new version of the lambda function that fixes the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants