TargetClosedException when using Proxy

Description

A TargetClosedException occurs immediately after the browser window is opened when using proxies with PuppeteerSharp 1.15.0 and 1.16.0; rolling back to 1.14.1 it is working fine. This is occurring both headless and non-headless, in Chrome and Chromium, on Windows and Linux. I am also not using request interception.

Expected behavior:

Successful proxy usage.

Actual behavior:

Protocol error(Page.navigate): Target closed. (NetworkManager failed to process Fetch.requestPaused. Value cannot be null.
Parameter name: key.    at System.Collections.Concurrent.ConcurrentDictionary`2.ThrowKeyNullException()
   at System.Collections.Concurrent.ConcurrentDictionary`2.set_Item(TKey key, TValue value)
   at PuppeteerSharp.NetworkManager.OnRequestPausedAsync(FetchRequestPausedResponse e)
   at PuppeteerSharp.NetworkManager.Client_MessageReceived(Object sender, MessageEventArgs e)) Protocol error(Page.navigate): Target closed. (NetworkManager failed to process Fetch.requestPaused. Value cannot be null.
Parameter name: key.    at System.Collections.Concurrent.ConcurrentDictionary`2.ThrowKeyNullException()
   at System.Collections.Concurrent.ConcurrentDictionary`2.set_Item(TKey key, TValue value)
   at PuppeteerSharp.NetworkManager.OnRequestPausedAsync(FetchRequestPausedResponse e)
   at PuppeteerSharp.NetworkManager.Client_MessageReceived(Object sender, MessageEventArgs e))

Versions

.NET Core 2.0

[null511]

Awesome. I just wanted to confirm that I’ve updated to 1.17.1 and it appears everything is working fine.

Also, thank you @kerohero that is correct. I did not try the ProxyManager service myself, but did discover that part of the issue above was authentication not being applied somehow.

[Kiro369]

I can confirm that it’s solved too, updated to 1.17.1 and everything runs as expected.