Comment 3 for bug 1751498

I think it may have something to do with how Chromium is accessing local storage.

Here's a screen shot from when it is able to communicate with the server.