You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running into a weird issue lately with PuppeteerSharp since updating from 7.1.0 to 9.1.0. I have PuppeteerSharp connect to a NordVPN SSL proxy by passing --proxy-server=https://<nordvpn-server>:89 to the args when launching the Browser object. I'd later call AuthenticateAsync on the Page object I'd get from the browser, as everything I've read says that is what you need to do (or rather, everything I've read says that for the Node.js version of Puppeteer, you need to call the authenticate function, so I assumed the same needed to be done with PuppeteerSharp).
With 7.1.0 this was working just fine. But I am not sure if this works with 9.1.0 anymore. More often than not, I seem to get a page that is still waiting for proxy authentication. Sometimes this happens even before I have a chance to navigate to a page with GoToAsync, sometimes it happens on the first call to GoToAsync, but it has been causing my calls to ScreenshotDataAsync to never return, I assume because Chrome is unable to reply to the Page.captureScreenshot method while waiting for proxy authentication.
I was going to file a bug for ScreenshotDataAsync never returning, but that was before I noticed that it could be because of the proxy authentication being needed. So before I even submit a bug, I'd like to know if what I'm doing to authenticate to a NordVPN SSL proxy is correct or if I should be doing it another way.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm running into a weird issue lately with PuppeteerSharp since updating from 7.1.0 to 9.1.0. I have PuppeteerSharp connect to a NordVPN SSL proxy by passing
--proxy-server=https://<nordvpn-server>:89
to the args when launching theBrowser
object. I'd later callAuthenticateAsync
on thePage
object I'd get from the browser, as everything I've read says that is what you need to do (or rather, everything I've read says that for the Node.js version of Puppeteer, you need to call theauthenticate
function, so I assumed the same needed to be done with PuppeteerSharp).With 7.1.0 this was working just fine. But I am not sure if this works with 9.1.0 anymore. More often than not, I seem to get a page that is still waiting for proxy authentication. Sometimes this happens even before I have a chance to navigate to a page with
GoToAsync
, sometimes it happens on the first call toGoToAsync
, but it has been causing my calls toScreenshotDataAsync
to never return, I assume because Chrome is unable to reply to thePage.captureScreenshot
method while waiting for proxy authentication.I was going to file a bug for
ScreenshotDataAsync
never returning, but that was before I noticed that it could be because of the proxy authentication being needed. So before I even submit a bug, I'd like to know if what I'm doing to authenticate to a NordVPN SSL proxy is correct or if I should be doing it another way.Beta Was this translation helpful? Give feedback.
All reactions