TeamSoftware Solutions

I have moved to the Chromium version as some of the sites we use at the library are not working on the IE based version. Most everything runs well except when we try and access Ancestry Library Edition (hard part to troubleshoot is it is accessible in-library only).

The page loads briefly then flashes to a white screen with errors like:

Sorry we are unable to load: https://d.agkn.com/iframe/9460/?che=921 ... =undefined

Error (-101): ERR_CONNECTION_RESET

I refresh the page:

Sorry we are unable to load: https://s.amazon-adsystem.com/iu3?d=gen ... 0029700400

Error (-101): ERR_CONNECTION_RESET

Any suggestions would be welcomed.

Are you using the URL filter? If so try disabling it to see if you have inadvertently blocked a URL the web site is trying to access.

--Scott

Scott,

I did disable my use of the URL.txt file and the first site I tested was Facebook. Facebook is not blocked by our firewall (nor is Ancestry) and I got a similar screen with a different error:

Sorry we are unable to load: https://googleads.g.doubleclick.net/pag ... N&script=0

Error (-101): ERR_CONNECTION_RESET

Common theme I am seeing is redirects or ads but these sites work fine OUTSIDE of PWB.

Stumped.

I see what could be my issue:

You need at least Windows Vista (PWB IE), Windows 8.0 (PWB CEF) to use PWB v3.

I am running this on Windows 7 as another one of our sites, Familysearch.org has issues in the previous version using IE. Inside PWB I get:

Attention: This site does not support the current version of your web browser. To get the best possible experience using our website we recommend that you upgrade to a newer version or install another browser

Outside of PWB I don't, oddly.

Let me test further.

Scratch that, IE on Windows 7 will produce the message from FamilySearch.org regardless:

Back to the drawing board.

Try running Chrome side by side with PWB CEF using an unedited INI file, do you see the same issues?

--Scott

Scott,

A fresh, unaltered ini gives me the same errors. Plain Chrome does not. This is on my work PC, inside the firewall.

I remoted home and tested with PWB and do not get the error, which normally would lead me to think our firewall is the culprit. Yet I have no issues inside the firewall with Mozilla, Chrome, etc. only PWB.

Erg.

What version of PWB CEF are you using?

PWB uses its own version of the Chrome HTML Rendering Engine via the Chromium Embedded Frame work. It maybe your firewall is blocking PWB and not Chrome.

Does the CEF Sample Application give the errors?
http://opensource.spotify.com/cefbuilds/index.html

--Scott

Scott,

I am using the latest version but I am guessing it is somehow a firewall issue (assuming the IE based version works differently as we never had issue there).

I cannot test via the link you provided as the county blocks that for shareware and freeware.

So, I guess for these 4 PCs I have to look for a different solution (The original PWB works great for our OPAC computers).

Thanks,

Chad