Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Is it still working?
See original GitHub issueHello,
First of all, thank you for making this software!
I tried using your compiled binaries. The browser starts properly in AWS lambda, but no inspectable targets are available and AWS lambda (those are required to find websocket URL, at /json/protocol endpoint). The AWS lambda just times out. There are no specific stdout or stderr entries which would indicate a problem.
When I launch headless shell in the lambda-like linux environment - it starts properly, and I can inspect pages.
Just wanted to see if it’s broken only for me, or other people experience similar problem?
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I had the same issue. I was using serverless-chrome/lambda: 1.0.0-43 Changing it to serverless-chrome/lambda: 1.0.0-38 fixed this issue. This thread helped me solve the issue.
Hope it helps
Looking into the logs of the latest dev/stable releases - I don’t see chrome fetches javascript assets. I downloaded https://github.com/adieuadieu/serverless-chrome/releases/tag/v1.0.0-31 and now see that js requests are made. However the screenshot is still blank. Not sure what’s causing it. Going to try pulling older version of the surrounding library (I replaced only binary file)