mirror of
https://github.com/aspnet/JavaScriptServices.git
synced 2025-12-22 17:47:53 +00:00
Calling into headless chrome timeouts in Production #333
Assignees
fergalmoran
Clear assignees
fergalmoran
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github/JavaScriptServices#333
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @chris-herring on 11/2/2017
Not sure if this is an problem with JavaScriptServices but I'm running out of ideas so looking for any helpful info.
I'm using headless chrome to generate some PDFs from with the app and then is done by using NodeServices.InvokeAsync() to call into node which then uses headless chrome to generate the PDF. This works great locally however once deployed to a Product machine (IIS 7.5, Windows Small Business Server 2011 Standard) it times out trying to launch headless Chrome. If I run the script using node script.js from the command line it works fine, it's just when executing using NodeServices that it fails.
I've turned on debugging and no errors in the logs. I've tried puppeteer & chromeless and both show the same behaviour. Could it be a permissions issue? I've tried running the IIS app pool under an admin account and that did not make a difference. When NodeServices launches node what user account does it run under?