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

Symfony\Component\Process\Exception\ProcessTimedOutException on PDF generation #430

Closed
SilverBull opened this issue Aug 31, 2021 · 4 comments
Labels

Comments

@SilverBull
Copy link

Hello, it look like you closed the issue 169 without a clear solution or at least to me there are workaround that not resolve the issue.
I'm still experiencing this with snappy 1.2.1 and wkhtmltopdf 0.12.6 on Debian 10 server with Apache and php 7.3.
As the previous issue I can correctly generate the pdf in 2 seconds running the command from shell, if I run it with $snappy->generate doesn't matter the timeout it will only generate the pdf after it generate a ProcessTimedOutException. Again as in the issue 169 the problem exist with the cookie option,
$snappy->setOption('cookie', array('PHPSESSID' => $cookie));

I'm missing something? There are other way to render an Url with Snappy?

@stale
Copy link

stale bot commented Nov 9, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Nov 9, 2021
@SilverBull
Copy link
Author

So apparently the repo is a bit stale or I'm the only one still with the problem.

@stale stale bot removed the stale label Nov 10, 2021
@parapente
Copy link

@SilverBull I have also encountered the same problem using laravel sail container and using the same version of snappy and wkhtmltopdf. The container doesn't use apache to serve the pages so I don't think that is relevant to the problem. I can create pdfs just fine using wkhtmltopdf from the command line.

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 16, 2022
@stale stale bot closed this as completed Apr 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants