-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[Self-Host] call to playwright is failing #902
Comments
Can you share the logs of the playwright microservice as well? |
the same problem.
|
I just made a change, I think the way we sent the request to the microservice was wrong. Can you rebuild |
I am getting errors while building the docker container as well - => ERROR [playwright-service 2/6] RUN apt-get update && apt-get install -y --no-install-recommends gcc libstdc++6 0.9s
failed to solve: process "/bin/sh -c apt-get update && apt-get install -y --no-install-recommends gcc libstdc++6" did not complete successfully: exit code: 100 |
I still see the issue, not sure why the logging level is not marked as error - worker-1 | 2024-11-15 16:23:58 info [:]: 🐂 Worker taking job b2c3e207-55ca-4abb-8be1-57a0b1b88cd2 response has empty markdown - { |
another error. after that happens firecrawl start working not correct
|
same issue for me |
same issue |
same issue +1 |
1 similar comment
same issue +1 |
Same issue "info [ScrapeURL:]: An unexpected error happened while scraping with playwright. ", both in original playwright and playwright-ts |
I guess this kind of error should be caused by some job config properties missing, maybe try to add a "timeout" property in json job data or scrapOptions. |
Describe the Issue
Call to playwright fails when trying to scrape with playwright.
To Reproduce
Steps to reproduce the issue:
Expected Behavior
The call to playwright should be successful and dynamic js should be rendered and cleaned up.
Screenshots
If applicable, add screenshots or copies of the command line output to help explain the self-hosting issue.
Environment (please complete the following information):
Logs
worker-1 | 2024-11-15 05:13:48 debug [ScrapeURL:]: Engine docx meets feature priority threshold
worker-1 | 2024-11-15 05:13:48 info [ScrapeURL:]: Scraping via playwright...
worker-1 | 2024-11-15 05:13:48 debug [ScrapeURL:scrapeURLWithPlaywright]: Sending request...
worker-1 | 2024-11-15 05:13:48 debug [ScrapeURL:scrapeURLWithPlaywright]: Request sent failure status
worker-1 | 2024-11-15 05:13:48 info [ScrapeURL:]: An unexpected error happened while scraping with playwright.
worker-1 | 2024-11-15 05:13:48 info [ScrapeURL:]: Scraping via fetch...
here are the logs
Configuration
Provide relevant parts of your configuration files (with sensitive information redacted).
Additional Context
Add any other context about the self-hosting issue here, such as specific infrastructure details, network setup, or any modifications made to the original Firecrawl setup.
The text was updated successfully, but these errors were encountered: