Norman Fomferra
Norman Fomferra
@VPriemer and @papesci Could you please ask your network admin whether there is any (new) proxy server / firewall configuration in your intranet regarding use of *WebSockets* with localhost (127.0.0.1).
@kbernat Thanks, sounds promising! @VPriemer Could you please try setting an environment variable in a shell: $ export no_proxy="127.0.0.1, localhost" Then start Cate Desktop from the same shell.
@VPriemer that should be ok, as there was no update since you've observed the problem.
Hopefully today. Note that the background map you see is Cate's static world image. It will be shown when Cate cannot reach http://dev.virtualearth.net which provides Cate's default Bing Maps imagery....
I just released 2.0.0.dev11
@papesci Vivien's browser passed the web socket test. When she runs the `cate-webapi-start -p 9090` first, Cate Desktop works fine, which is strange enough.
Issue could be partly solved by letting Cate Desktop recognizing environment variables `HTTP_PROXY`, `HTTPS_PROXY`, `SOCKS_PROXY`, `NO_PROXY`, and their lower-case counterparts to 1. configure Electron's [proxy command-line switches](https://github.com/electron/electron/blob/master/docs/api/chrome-command-line-switches.md#--proxy-serveraddressport) 2. configure Electron's...
It does not always happen. Any idea what causes it?
I'll debug into it.
Could you please try again with dev11.