Azure Appservice

[avialonn]

Hi All,
Is it possible to run this on azure AppService (Windows)?
I'm getting the following error with no success:

An error occurred trying to start process 'C:\home\site\wwwroot\Chrome\Win64-121.0.6167.85\chrome-win64\chrome.exe' with working directory 'C:\home\site\wwwroot'. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. line: 208

Thanks!
AA

[kblok]

Docker images proved to be the best way to run puppeteer in the cloud.

[avialonn]

Got it! I will give it a try.
Thanks

[sashiyama]

I've created a docker image to run a proxy server that provide WebSocket endpoint to use Chromium headless browser from your application. You can run it on your local environment or server such as render.com, Azure VMs, and so on even though your application is running on Azure App Service that does not allow apps to run headless browsers.

https://github.com/sashiyama/browserless

var options = new ConnectOptions
{
    BrowserWSEndpoint = "ws://localhost/chromium?token=xxx"
};

return await Puppeteer.ConnectAsync(options);

[John-PS]

we had a web app service running this, but as soon as we upgraded to .net core 8 (and updated the old puppeteer Sharp) it is essentially broken as just calling the Page.GotoAsync makes it throw the error regarding the detached Frame. I've found a lot of notes about that and it sounds like it just doesnt work anymore:

PuppeteerException: Navigating frame was detached
PuppeteerSharp.Helpers.TaskHelper.WithTimeout(Task task, Func timeoutAction, TimeSpan timeout, CancellationToken cancellationToken) in TaskHelper.cs, line 101

NavigationException: Navigating frame was detached
PuppeteerSharp.Cdp.CdpFrame.GoToAsync(string url, NavigationOptions options) in CdpFrame.cs, line 108

[sashiyama]

@John-PS Thank you for letting me know. It seems like my node library and Puppeteer Sharp don't have compatibility anymore since you upgraded the library. I think that since my library is just wrapping Puppeteer with WebSocket server, if my library and Puppeteer sharp use same version of Puppeteer, it should work. Have you rebuild my library docker image since you upgraded Puppeteer Sharp? If you haven't, could you do that to update puppeteer in my library running on your server.

[John-PS]

I should clarify - I meant that we were using Puppeteer Sharp and it stopped working when we moved to .net core 8; we aren't using a docker image as the project we inherited is using a slightly different setup.