Timing out when we set "RemoteDebuggingAllowed" to 0 for chrome

[jaydeep009]

"RemoteDebuggingAllowed" should be set to 0 in registry under path HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
If this does not exist , then create one.

If this is set and we run puppeteer sharp for html to pdf conversion then it times out.

[kblok]

If you don't allow remote debugging, puppeteer can't automate your browser.

[jaydeep009]

OK, so if this registry key is enabled, then puppeteer sharp will not be able to perform automation and then conversion.
Is there a workaround for these or is it mandatory to keep this key disabled?

For workaround currently i am shipping chrome headless binaries so it doesn't point to installed chrome

[kblok]

OK, so if this registry key is enabled, then puppeteer sharp will not be able to perform automation and then conversion. Is there a workaround for these or is it mandatory to keep this key disabled?

For workaround currently i am shipping chrome headless binaries so it doesn't point to installed chrome

Yes. You won't be able to automate chrome with any automation tool with that flag.