SocketCluster / socketcluster-client

JavaScript client for SocketCluster
MIT License
291 stars 92 forks source link

Instance_1 was not allowed to run insecure contenet from instance_2 #99

Closed sravia closed 6 years ago

sravia commented 6 years ago

I have the follow architecture:

EC2_1_INSTANCE instance is connecting to EC2_2_INSTANCE instance using the following settings: options = { path: '/', port: 80, hostname: 'EC2_2_INSTANCE', autoConnect: true, secure: false, };

I am getting this error in browser console: [blocked] The page at https://EC2_1_INSTANCE was not allowed to run insecure content from ws://EC2_2_INSTANCE:80/

How something like this gets fixed? Do I have to also get a second certificate for EC2_2_INSTANCE? Another domain/subdomain?

DarkMukke commented 6 years ago

I would opt for a subdomain for your workers/sc-server, you can't run a secure http connection over port 80. Or at least not the current version of http (1.2). Basically your webapp is secured over SSL on port 443 but then the client creates a connection to port 80 which is not secure, so the browser will refuse to connect to insecure sources within the webapp as it cannot guarantee the sources security.