Folks, I've updated the certs on webby.evergreencatalog.com, so all should be well in that regard now.
On Thu, Sep 18, 2014 at 11:37 AM, Bill Erickson <beric...@gmail.com> wrote: > > > On Tue, Sep 16, 2014 at 2:22 AM, Liam Whalen < > liam.wha...@bc.libraries.coop> wrote: > > <snip> > > >> I am getting the following error when I try to login via Firefox on the >> Windows VM: >> >> webby.evergreencatalog.com:7682 uses an invalid security certificate. >> >> The certificate is not trusted because no issuer chain was provided. >> >> (Error code: sec_error_unknown_issuer) >> >> Firefox can't establish a connection to the server at wss:// >> webby.evergreencatalog.com:7682/osrf-websocket-translator. >> evergreen-staff-client.0.0.1.min.js:9 >> Error: WebSocket Error [object Event] : undefined >> evergreen-staff-client.0.0.1.min.js:9 >> "closing websocket" evergreen-staff-client.0.0.1.min.js:9 >> Synchronous XMLHttpRequest on the main thread is deprecated because of >> its detrimental effects to the end user's experience. For more help >> http://xhr.spec.whatwg.org/ exceptionDialog.js:136 >> www.evergreencatalog.com:443 uses an invalid security certificate. >> >> The certificate is only valid for the following names: >> *.esilibrary.com, esilibrary.com >> > > I can confirm this is a problem in Linux / FF 31 as well. Firefox is > considerably more rigid in its security restrictions than Chrome. If I > recall correctly, in previous versions of FF, adding an exception for https > would allow websockets connections to succeed as well. Apparently not > anymore. We'll need a valid certificate on the server for Firefox to work. > > > -b > -- Mike Rylander | Director of Research and Development | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 1-877-OPEN-ILS (673-6457) | email: mi...@esilibrary.com | web: http://www.esilibrary.com