@Fabian_Calais, does your company’s proxy replace SSL certs with their own internal certs? I unfortunately cannot use sites that utilize websockets at my work, including Coda, because of this. Go to any site that is using ssl (almost all do now). Take a look at the certificate path. In Chrome this can all be done by clicking on the lock icon to the left of the address bar. After clicking on the icon, select “certificate” and go to certificate path tab. If the proxy is replacing a public cert with private ones, than this is why websockets don’t work. Your company may be unwilling to bypass this mechanism as they will no longer be able to snoop in on your network traffic. It also allows the outside to request info from your browser, which could be a no no. Many modern sites use websockets to enable chat features, which would require constant client side refreshes to make sure users are getting notified on time.