An Issue with connecting: SSL + WebSocket(socketme.io) + Nginx











up vote
0
down vote

favorite












Tried to connect WebSocket(socketme.io) through HTTPS, didn't succeed gave the error as




WebSocket opening handshake timed out




As my hosting server's ngnix (version: 1.13.8) is configured to work in reverse proxy mode in the front-end. Here is the configuration of the Nginx



http {
map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
upstream websocket {
server xx.xxx.xxx.x:8282; #External IP address
}
server {

location / {
proxy_pass http://xx.xxx.xxx.x:8080; #External IP address
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_read_timeout 120s;
}
}
}


chatroom.php



<script type="text/javascript">
$(document).ready(function(){
var conn = new WebSocket('ws://xx.xxx.xxx.x:8282');
conn.onopen = function(e) {
console.log("Connection established!");
};

conn.onmessage = function(e) {
console.log(e.data);
...
};

conn.onclose = function(e) {
console.log("Connection Closed!");
}
})
</script>


server.php



<?php
use RatchetServerIoServer;
use RatchetHttpHttpServer;
use RatchetWebSocketWsServer;
use MyAppChat;

require dirname(__DIR__) . '/vendor/autoload.php';

$server = IoServer::factory(
new HttpServer(
new WsServer(
new Chat()
)
),
8282
);

$server->run();


Before applying SSL,



enter image description here






Then after applying SSL,

enter image description here



Established the WebSocket connection via port #8282 from the terminal as shown below



root@user:/var/www/vhosts/somedomain.xy/httpdocs/chatroom-php-mysql/bin# php server.php
Server Started.
New connection! (84)
Connection 84 has disconnected


When website URL is opened in browser basically this is what it happens as follows:




  1. Client request comes to front-end Nginx asking for some resource (.html page, .php page, image, javascript, etc). Nginx in our hosting server works on TCP ports: 80 - http, 443 - https.


  2. Nginx checks if it has the resource already in its cache.


  3. If the resource is cached, Nginx returns the cached content.


  4. If the resource is not cached or if the dynamic page (e.g. index.php) is requested, Nginx proxies (forwards) the request to back-end server - Apache. Apache in our hosting server works on TCP ports: 7080 - http, 7081 - https. Then Nginx caches static content - HTML, images, js, css.





Updated:



Symbolic link had been created in
/etc/nginx/plesk.conf.d/vhosts in somedomain.xy.conf



#ATTENTION!
#
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.

server {
listen xx.xxx.xxx.x:443 ssl http2;

server_name somedomain.xy;
server_name www.somedomain.xy;
server_name ipv4.somedomain.xy;

ssl_certificate /opt/psa/var/certificates/scfPsMGvJ;
ssl_certificate_key /opt/psa/var/certificates/scfPsMGvJ;
ssl_client_certificate /opt/psa/var/certificates/scfSdpTzN;

client_max_body_size 128m;

root "/var/www/vhosts/somedomain.xy/httpdocs";
access_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_access_ssl_log";
error_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_error_log";

#extension letsencrypt begin
location /.well-known/acme-challenge/ {
root /var/www/vhosts/default/htdocs;

types { }
default_type text/plain;

satisfy any;
auth_basic off;
allow all;

location ~ ^/.well-known/acme-challenge.*/. {
deny all;
}
}
#extension letsencrypt end

location / {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location /internal-nginx-static-location/ {
alias /var/www/vhosts/somedomain.xy/httpdocs/;
internal;
}

location ~ ^/(plesk-stat|awstats-icon|webstat|webstat-ssl|ftpstat|anon_ftpstat) {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ ^/proj_ci/ {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ "^/files/" {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

add_header X-Powered-By PleskLin;

}

server {
listen xx.xxx.xxx.x:80;

server_name somedomain.xy;
server_name www.somedomain.xy;
server_name ipv4.somedomain.xy;

client_max_body_size 128m;

root "/var/www/vhosts/somedomain.xy/httpdocs";
access_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_access_log";
error_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_error_log";

#extension letsencrypt begin
location /.well-known/acme-challenge/ {
root /var/www/vhosts/default/htdocs;

types { }
default_type text/plain;

satisfy any;
auth_basic off;
allow all;

location ~ ^/.well-known/acme-challenge.*/. {
deny all;
}
}
#extension letsencrypt end

location / {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location /internal-nginx-static-location/ {
alias /var/www/vhosts/somedomain.xy/httpdocs/;
internal;
}

location ~ ^/(plesk-stat|awstats-icon|webstat|webstat-ssl|ftpstat|anon_ftpstat) {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ ^/proj_ci/ {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ "^/files/" {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

add_header X-Powered-By PleskLin;

}


I had tried to create in /etc/nginx/conf.d with the filename app_name.conf



map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}

upstream websocket {
server xx.xxx.xxx.x:8282;
}

server {
# listen xx.xxx.xxx.x:80;
# listen 443 default_server ssl;
listen 443 ssl http2;
server_name somedomain.xy;


location / {
proxy_pass http://xx.xxx.xxx.x:8282;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
# proxy_read_timeout 120s;
proxy_read_timeout 86400;
# proxy_redirect default;
# proxy_redirect http://xx.xxx.xxx.x:8282/ /;
# proxy_redirect http://www.somedomain.xy/ /;
}

location /chat/ {
proxy_pass http://xx.xxx.xxx.x:8282;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_read_timeout 120s;
}

location /test {
rewrite ^/test(.*) $1 break;
proxy_pass http://127.0.0.1:8282;
}

location /wss {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Proxy "";
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://xx.xxx.xxx.x:8282;
proxy_read_timeout 120s;
}

location /websocket {
proxy_pass http://xx.xxx.xxx.x:8282; ## WSPHP listening port
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_read_timeout 86400;
}

}


Also, In Nginx we are not able to see such directories they are /etc/nginx/sites-available/* and /etc/nginx/sites-enabled/* ,
we will be seeing under /etc/apache2










share|improve this question
























  • No, I'm using Ratchet PHP @AnimeshSahu
    – Nishanth ॐ
    Nov 21 at 11:29






  • 2




    I'm not sure if I understand your problem correctly. But based on what you show you are embedding a plain websocket connection (ws://) instead of a secure websocket connection (wss://) in your page and the browser is rightly complaining that you embed insecure resources (ws:// instead of wss://) into a secure webpage (https://). Thus, what you do is to change your code to use wss:// instead of ws:// and add the forwarding to the internal websocket server also to the ssl part of your nginx config.
    – Steffen Ullrich
    Nov 21 at 12:09










  • What should be my upstream server and listen port#. Also internal IP starts from 127.0.0.1/30 @SteffenUllrich
    – Nishanth ॐ
    Nov 21 at 12:16








  • 1




    The configuration where you forward to (upstream...) should be exactly the same. There is no change needed on the internal websocket server. You only need to change that you a) use wss:// to access the websocket and b) make nginx forward to the internal websocket server also within the ssl part of your configuration. nginx will terminate the SSL connection (i.e. wss://) and forward the data in plain (ws://) so no change to the internal websocket server is needed.
    – Steffen Ullrich
    Nov 21 at 12:21












  • But still, I couldn't able to figure it out about where should I need to edit. As I'm getting the same error. So kindly help me with the edited post above @SteffenUllrich
    – Nishanth ॐ
    Nov 22 at 7:14

















up vote
0
down vote

favorite












Tried to connect WebSocket(socketme.io) through HTTPS, didn't succeed gave the error as




WebSocket opening handshake timed out




As my hosting server's ngnix (version: 1.13.8) is configured to work in reverse proxy mode in the front-end. Here is the configuration of the Nginx



http {
map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
upstream websocket {
server xx.xxx.xxx.x:8282; #External IP address
}
server {

location / {
proxy_pass http://xx.xxx.xxx.x:8080; #External IP address
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_read_timeout 120s;
}
}
}


chatroom.php



<script type="text/javascript">
$(document).ready(function(){
var conn = new WebSocket('ws://xx.xxx.xxx.x:8282');
conn.onopen = function(e) {
console.log("Connection established!");
};

conn.onmessage = function(e) {
console.log(e.data);
...
};

conn.onclose = function(e) {
console.log("Connection Closed!");
}
})
</script>


server.php



<?php
use RatchetServerIoServer;
use RatchetHttpHttpServer;
use RatchetWebSocketWsServer;
use MyAppChat;

require dirname(__DIR__) . '/vendor/autoload.php';

$server = IoServer::factory(
new HttpServer(
new WsServer(
new Chat()
)
),
8282
);

$server->run();


Before applying SSL,



enter image description here






Then after applying SSL,

enter image description here



Established the WebSocket connection via port #8282 from the terminal as shown below



root@user:/var/www/vhosts/somedomain.xy/httpdocs/chatroom-php-mysql/bin# php server.php
Server Started.
New connection! (84)
Connection 84 has disconnected


When website URL is opened in browser basically this is what it happens as follows:




  1. Client request comes to front-end Nginx asking for some resource (.html page, .php page, image, javascript, etc). Nginx in our hosting server works on TCP ports: 80 - http, 443 - https.


  2. Nginx checks if it has the resource already in its cache.


  3. If the resource is cached, Nginx returns the cached content.


  4. If the resource is not cached or if the dynamic page (e.g. index.php) is requested, Nginx proxies (forwards) the request to back-end server - Apache. Apache in our hosting server works on TCP ports: 7080 - http, 7081 - https. Then Nginx caches static content - HTML, images, js, css.





Updated:



Symbolic link had been created in
/etc/nginx/plesk.conf.d/vhosts in somedomain.xy.conf



#ATTENTION!
#
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.

server {
listen xx.xxx.xxx.x:443 ssl http2;

server_name somedomain.xy;
server_name www.somedomain.xy;
server_name ipv4.somedomain.xy;

ssl_certificate /opt/psa/var/certificates/scfPsMGvJ;
ssl_certificate_key /opt/psa/var/certificates/scfPsMGvJ;
ssl_client_certificate /opt/psa/var/certificates/scfSdpTzN;

client_max_body_size 128m;

root "/var/www/vhosts/somedomain.xy/httpdocs";
access_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_access_ssl_log";
error_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_error_log";

#extension letsencrypt begin
location /.well-known/acme-challenge/ {
root /var/www/vhosts/default/htdocs;

types { }
default_type text/plain;

satisfy any;
auth_basic off;
allow all;

location ~ ^/.well-known/acme-challenge.*/. {
deny all;
}
}
#extension letsencrypt end

location / {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location /internal-nginx-static-location/ {
alias /var/www/vhosts/somedomain.xy/httpdocs/;
internal;
}

location ~ ^/(plesk-stat|awstats-icon|webstat|webstat-ssl|ftpstat|anon_ftpstat) {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ ^/proj_ci/ {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ "^/files/" {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

add_header X-Powered-By PleskLin;

}

server {
listen xx.xxx.xxx.x:80;

server_name somedomain.xy;
server_name www.somedomain.xy;
server_name ipv4.somedomain.xy;

client_max_body_size 128m;

root "/var/www/vhosts/somedomain.xy/httpdocs";
access_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_access_log";
error_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_error_log";

#extension letsencrypt begin
location /.well-known/acme-challenge/ {
root /var/www/vhosts/default/htdocs;

types { }
default_type text/plain;

satisfy any;
auth_basic off;
allow all;

location ~ ^/.well-known/acme-challenge.*/. {
deny all;
}
}
#extension letsencrypt end

location / {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location /internal-nginx-static-location/ {
alias /var/www/vhosts/somedomain.xy/httpdocs/;
internal;
}

location ~ ^/(plesk-stat|awstats-icon|webstat|webstat-ssl|ftpstat|anon_ftpstat) {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ ^/proj_ci/ {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ "^/files/" {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

add_header X-Powered-By PleskLin;

}


I had tried to create in /etc/nginx/conf.d with the filename app_name.conf



map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}

upstream websocket {
server xx.xxx.xxx.x:8282;
}

server {
# listen xx.xxx.xxx.x:80;
# listen 443 default_server ssl;
listen 443 ssl http2;
server_name somedomain.xy;


location / {
proxy_pass http://xx.xxx.xxx.x:8282;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
# proxy_read_timeout 120s;
proxy_read_timeout 86400;
# proxy_redirect default;
# proxy_redirect http://xx.xxx.xxx.x:8282/ /;
# proxy_redirect http://www.somedomain.xy/ /;
}

location /chat/ {
proxy_pass http://xx.xxx.xxx.x:8282;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_read_timeout 120s;
}

location /test {
rewrite ^/test(.*) $1 break;
proxy_pass http://127.0.0.1:8282;
}

location /wss {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Proxy "";
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://xx.xxx.xxx.x:8282;
proxy_read_timeout 120s;
}

location /websocket {
proxy_pass http://xx.xxx.xxx.x:8282; ## WSPHP listening port
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_read_timeout 86400;
}

}


Also, In Nginx we are not able to see such directories they are /etc/nginx/sites-available/* and /etc/nginx/sites-enabled/* ,
we will be seeing under /etc/apache2










share|improve this question
























  • No, I'm using Ratchet PHP @AnimeshSahu
    – Nishanth ॐ
    Nov 21 at 11:29






  • 2




    I'm not sure if I understand your problem correctly. But based on what you show you are embedding a plain websocket connection (ws://) instead of a secure websocket connection (wss://) in your page and the browser is rightly complaining that you embed insecure resources (ws:// instead of wss://) into a secure webpage (https://). Thus, what you do is to change your code to use wss:// instead of ws:// and add the forwarding to the internal websocket server also to the ssl part of your nginx config.
    – Steffen Ullrich
    Nov 21 at 12:09










  • What should be my upstream server and listen port#. Also internal IP starts from 127.0.0.1/30 @SteffenUllrich
    – Nishanth ॐ
    Nov 21 at 12:16








  • 1




    The configuration where you forward to (upstream...) should be exactly the same. There is no change needed on the internal websocket server. You only need to change that you a) use wss:// to access the websocket and b) make nginx forward to the internal websocket server also within the ssl part of your configuration. nginx will terminate the SSL connection (i.e. wss://) and forward the data in plain (ws://) so no change to the internal websocket server is needed.
    – Steffen Ullrich
    Nov 21 at 12:21












  • But still, I couldn't able to figure it out about where should I need to edit. As I'm getting the same error. So kindly help me with the edited post above @SteffenUllrich
    – Nishanth ॐ
    Nov 22 at 7:14















up vote
0
down vote

favorite









up vote
0
down vote

favorite











Tried to connect WebSocket(socketme.io) through HTTPS, didn't succeed gave the error as




WebSocket opening handshake timed out




As my hosting server's ngnix (version: 1.13.8) is configured to work in reverse proxy mode in the front-end. Here is the configuration of the Nginx



http {
map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
upstream websocket {
server xx.xxx.xxx.x:8282; #External IP address
}
server {

location / {
proxy_pass http://xx.xxx.xxx.x:8080; #External IP address
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_read_timeout 120s;
}
}
}


chatroom.php



<script type="text/javascript">
$(document).ready(function(){
var conn = new WebSocket('ws://xx.xxx.xxx.x:8282');
conn.onopen = function(e) {
console.log("Connection established!");
};

conn.onmessage = function(e) {
console.log(e.data);
...
};

conn.onclose = function(e) {
console.log("Connection Closed!");
}
})
</script>


server.php



<?php
use RatchetServerIoServer;
use RatchetHttpHttpServer;
use RatchetWebSocketWsServer;
use MyAppChat;

require dirname(__DIR__) . '/vendor/autoload.php';

$server = IoServer::factory(
new HttpServer(
new WsServer(
new Chat()
)
),
8282
);

$server->run();


Before applying SSL,



enter image description here






Then after applying SSL,

enter image description here



Established the WebSocket connection via port #8282 from the terminal as shown below



root@user:/var/www/vhosts/somedomain.xy/httpdocs/chatroom-php-mysql/bin# php server.php
Server Started.
New connection! (84)
Connection 84 has disconnected


When website URL is opened in browser basically this is what it happens as follows:




  1. Client request comes to front-end Nginx asking for some resource (.html page, .php page, image, javascript, etc). Nginx in our hosting server works on TCP ports: 80 - http, 443 - https.


  2. Nginx checks if it has the resource already in its cache.


  3. If the resource is cached, Nginx returns the cached content.


  4. If the resource is not cached or if the dynamic page (e.g. index.php) is requested, Nginx proxies (forwards) the request to back-end server - Apache. Apache in our hosting server works on TCP ports: 7080 - http, 7081 - https. Then Nginx caches static content - HTML, images, js, css.





Updated:



Symbolic link had been created in
/etc/nginx/plesk.conf.d/vhosts in somedomain.xy.conf



#ATTENTION!
#
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.

server {
listen xx.xxx.xxx.x:443 ssl http2;

server_name somedomain.xy;
server_name www.somedomain.xy;
server_name ipv4.somedomain.xy;

ssl_certificate /opt/psa/var/certificates/scfPsMGvJ;
ssl_certificate_key /opt/psa/var/certificates/scfPsMGvJ;
ssl_client_certificate /opt/psa/var/certificates/scfSdpTzN;

client_max_body_size 128m;

root "/var/www/vhosts/somedomain.xy/httpdocs";
access_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_access_ssl_log";
error_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_error_log";

#extension letsencrypt begin
location /.well-known/acme-challenge/ {
root /var/www/vhosts/default/htdocs;

types { }
default_type text/plain;

satisfy any;
auth_basic off;
allow all;

location ~ ^/.well-known/acme-challenge.*/. {
deny all;
}
}
#extension letsencrypt end

location / {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location /internal-nginx-static-location/ {
alias /var/www/vhosts/somedomain.xy/httpdocs/;
internal;
}

location ~ ^/(plesk-stat|awstats-icon|webstat|webstat-ssl|ftpstat|anon_ftpstat) {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ ^/proj_ci/ {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ "^/files/" {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

add_header X-Powered-By PleskLin;

}

server {
listen xx.xxx.xxx.x:80;

server_name somedomain.xy;
server_name www.somedomain.xy;
server_name ipv4.somedomain.xy;

client_max_body_size 128m;

root "/var/www/vhosts/somedomain.xy/httpdocs";
access_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_access_log";
error_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_error_log";

#extension letsencrypt begin
location /.well-known/acme-challenge/ {
root /var/www/vhosts/default/htdocs;

types { }
default_type text/plain;

satisfy any;
auth_basic off;
allow all;

location ~ ^/.well-known/acme-challenge.*/. {
deny all;
}
}
#extension letsencrypt end

location / {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location /internal-nginx-static-location/ {
alias /var/www/vhosts/somedomain.xy/httpdocs/;
internal;
}

location ~ ^/(plesk-stat|awstats-icon|webstat|webstat-ssl|ftpstat|anon_ftpstat) {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ ^/proj_ci/ {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ "^/files/" {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

add_header X-Powered-By PleskLin;

}


I had tried to create in /etc/nginx/conf.d with the filename app_name.conf



map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}

upstream websocket {
server xx.xxx.xxx.x:8282;
}

server {
# listen xx.xxx.xxx.x:80;
# listen 443 default_server ssl;
listen 443 ssl http2;
server_name somedomain.xy;


location / {
proxy_pass http://xx.xxx.xxx.x:8282;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
# proxy_read_timeout 120s;
proxy_read_timeout 86400;
# proxy_redirect default;
# proxy_redirect http://xx.xxx.xxx.x:8282/ /;
# proxy_redirect http://www.somedomain.xy/ /;
}

location /chat/ {
proxy_pass http://xx.xxx.xxx.x:8282;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_read_timeout 120s;
}

location /test {
rewrite ^/test(.*) $1 break;
proxy_pass http://127.0.0.1:8282;
}

location /wss {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Proxy "";
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://xx.xxx.xxx.x:8282;
proxy_read_timeout 120s;
}

location /websocket {
proxy_pass http://xx.xxx.xxx.x:8282; ## WSPHP listening port
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_read_timeout 86400;
}

}


Also, In Nginx we are not able to see such directories they are /etc/nginx/sites-available/* and /etc/nginx/sites-enabled/* ,
we will be seeing under /etc/apache2










share|improve this question















Tried to connect WebSocket(socketme.io) through HTTPS, didn't succeed gave the error as




WebSocket opening handshake timed out




As my hosting server's ngnix (version: 1.13.8) is configured to work in reverse proxy mode in the front-end. Here is the configuration of the Nginx



http {
map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
upstream websocket {
server xx.xxx.xxx.x:8282; #External IP address
}
server {

location / {
proxy_pass http://xx.xxx.xxx.x:8080; #External IP address
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_read_timeout 120s;
}
}
}


chatroom.php



<script type="text/javascript">
$(document).ready(function(){
var conn = new WebSocket('ws://xx.xxx.xxx.x:8282');
conn.onopen = function(e) {
console.log("Connection established!");
};

conn.onmessage = function(e) {
console.log(e.data);
...
};

conn.onclose = function(e) {
console.log("Connection Closed!");
}
})
</script>


server.php



<?php
use RatchetServerIoServer;
use RatchetHttpHttpServer;
use RatchetWebSocketWsServer;
use MyAppChat;

require dirname(__DIR__) . '/vendor/autoload.php';

$server = IoServer::factory(
new HttpServer(
new WsServer(
new Chat()
)
),
8282
);

$server->run();


Before applying SSL,



enter image description here






Then after applying SSL,

enter image description here



Established the WebSocket connection via port #8282 from the terminal as shown below



root@user:/var/www/vhosts/somedomain.xy/httpdocs/chatroom-php-mysql/bin# php server.php
Server Started.
New connection! (84)
Connection 84 has disconnected


When website URL is opened in browser basically this is what it happens as follows:




  1. Client request comes to front-end Nginx asking for some resource (.html page, .php page, image, javascript, etc). Nginx in our hosting server works on TCP ports: 80 - http, 443 - https.


  2. Nginx checks if it has the resource already in its cache.


  3. If the resource is cached, Nginx returns the cached content.


  4. If the resource is not cached or if the dynamic page (e.g. index.php) is requested, Nginx proxies (forwards) the request to back-end server - Apache. Apache in our hosting server works on TCP ports: 7080 - http, 7081 - https. Then Nginx caches static content - HTML, images, js, css.





Updated:



Symbolic link had been created in
/etc/nginx/plesk.conf.d/vhosts in somedomain.xy.conf



#ATTENTION!
#
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.

server {
listen xx.xxx.xxx.x:443 ssl http2;

server_name somedomain.xy;
server_name www.somedomain.xy;
server_name ipv4.somedomain.xy;

ssl_certificate /opt/psa/var/certificates/scfPsMGvJ;
ssl_certificate_key /opt/psa/var/certificates/scfPsMGvJ;
ssl_client_certificate /opt/psa/var/certificates/scfSdpTzN;

client_max_body_size 128m;

root "/var/www/vhosts/somedomain.xy/httpdocs";
access_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_access_ssl_log";
error_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_error_log";

#extension letsencrypt begin
location /.well-known/acme-challenge/ {
root /var/www/vhosts/default/htdocs;

types { }
default_type text/plain;

satisfy any;
auth_basic off;
allow all;

location ~ ^/.well-known/acme-challenge.*/. {
deny all;
}
}
#extension letsencrypt end

location / {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location /internal-nginx-static-location/ {
alias /var/www/vhosts/somedomain.xy/httpdocs/;
internal;
}

location ~ ^/(plesk-stat|awstats-icon|webstat|webstat-ssl|ftpstat|anon_ftpstat) {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ ^/proj_ci/ {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ "^/files/" {
proxy_pass https://xx.xxx.xxx.x:7081;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

add_header X-Powered-By PleskLin;

}

server {
listen xx.xxx.xxx.x:80;

server_name somedomain.xy;
server_name www.somedomain.xy;
server_name ipv4.somedomain.xy;

client_max_body_size 128m;

root "/var/www/vhosts/somedomain.xy/httpdocs";
access_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_access_log";
error_log "/var/www/vhosts/system/somedomain.xy/logs/proxy_error_log";

#extension letsencrypt begin
location /.well-known/acme-challenge/ {
root /var/www/vhosts/default/htdocs;

types { }
default_type text/plain;

satisfy any;
auth_basic off;
allow all;

location ~ ^/.well-known/acme-challenge.*/. {
deny all;
}
}
#extension letsencrypt end

location / {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location /internal-nginx-static-location/ {
alias /var/www/vhosts/somedomain.xy/httpdocs/;
internal;
}

location ~ ^/(plesk-stat|awstats-icon|webstat|webstat-ssl|ftpstat|anon_ftpstat) {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ ^/proj_ci/ {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

location ~ "^/files/" {
proxy_pass http://xx.xxx.xxx.x:7080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;

}

add_header X-Powered-By PleskLin;

}


I had tried to create in /etc/nginx/conf.d with the filename app_name.conf



map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}

upstream websocket {
server xx.xxx.xxx.x:8282;
}

server {
# listen xx.xxx.xxx.x:80;
# listen 443 default_server ssl;
listen 443 ssl http2;
server_name somedomain.xy;


location / {
proxy_pass http://xx.xxx.xxx.x:8282;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
# proxy_read_timeout 120s;
proxy_read_timeout 86400;
# proxy_redirect default;
# proxy_redirect http://xx.xxx.xxx.x:8282/ /;
# proxy_redirect http://www.somedomain.xy/ /;
}

location /chat/ {
proxy_pass http://xx.xxx.xxx.x:8282;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_read_timeout 120s;
}

location /test {
rewrite ^/test(.*) $1 break;
proxy_pass http://127.0.0.1:8282;
}

location /wss {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Proxy "";
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://xx.xxx.xxx.x:8282;
proxy_read_timeout 120s;
}

location /websocket {
proxy_pass http://xx.xxx.xxx.x:8282; ## WSPHP listening port
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_read_timeout 86400;
}

}


Also, In Nginx we are not able to see such directories they are /etc/nginx/sites-available/* and /etc/nginx/sites-enabled/* ,
we will be seeing under /etc/apache2







php ssl nginx websocket ratchet






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 at 10:44

























asked Nov 21 at 11:24









Nishanth ॐ

4883420




4883420












  • No, I'm using Ratchet PHP @AnimeshSahu
    – Nishanth ॐ
    Nov 21 at 11:29






  • 2




    I'm not sure if I understand your problem correctly. But based on what you show you are embedding a plain websocket connection (ws://) instead of a secure websocket connection (wss://) in your page and the browser is rightly complaining that you embed insecure resources (ws:// instead of wss://) into a secure webpage (https://). Thus, what you do is to change your code to use wss:// instead of ws:// and add the forwarding to the internal websocket server also to the ssl part of your nginx config.
    – Steffen Ullrich
    Nov 21 at 12:09










  • What should be my upstream server and listen port#. Also internal IP starts from 127.0.0.1/30 @SteffenUllrich
    – Nishanth ॐ
    Nov 21 at 12:16








  • 1




    The configuration where you forward to (upstream...) should be exactly the same. There is no change needed on the internal websocket server. You only need to change that you a) use wss:// to access the websocket and b) make nginx forward to the internal websocket server also within the ssl part of your configuration. nginx will terminate the SSL connection (i.e. wss://) and forward the data in plain (ws://) so no change to the internal websocket server is needed.
    – Steffen Ullrich
    Nov 21 at 12:21












  • But still, I couldn't able to figure it out about where should I need to edit. As I'm getting the same error. So kindly help me with the edited post above @SteffenUllrich
    – Nishanth ॐ
    Nov 22 at 7:14




















  • No, I'm using Ratchet PHP @AnimeshSahu
    – Nishanth ॐ
    Nov 21 at 11:29






  • 2




    I'm not sure if I understand your problem correctly. But based on what you show you are embedding a plain websocket connection (ws://) instead of a secure websocket connection (wss://) in your page and the browser is rightly complaining that you embed insecure resources (ws:// instead of wss://) into a secure webpage (https://). Thus, what you do is to change your code to use wss:// instead of ws:// and add the forwarding to the internal websocket server also to the ssl part of your nginx config.
    – Steffen Ullrich
    Nov 21 at 12:09










  • What should be my upstream server and listen port#. Also internal IP starts from 127.0.0.1/30 @SteffenUllrich
    – Nishanth ॐ
    Nov 21 at 12:16








  • 1




    The configuration where you forward to (upstream...) should be exactly the same. There is no change needed on the internal websocket server. You only need to change that you a) use wss:// to access the websocket and b) make nginx forward to the internal websocket server also within the ssl part of your configuration. nginx will terminate the SSL connection (i.e. wss://) and forward the data in plain (ws://) so no change to the internal websocket server is needed.
    – Steffen Ullrich
    Nov 21 at 12:21












  • But still, I couldn't able to figure it out about where should I need to edit. As I'm getting the same error. So kindly help me with the edited post above @SteffenUllrich
    – Nishanth ॐ
    Nov 22 at 7:14


















No, I'm using Ratchet PHP @AnimeshSahu
– Nishanth ॐ
Nov 21 at 11:29




No, I'm using Ratchet PHP @AnimeshSahu
– Nishanth ॐ
Nov 21 at 11:29




2




2




I'm not sure if I understand your problem correctly. But based on what you show you are embedding a plain websocket connection (ws://) instead of a secure websocket connection (wss://) in your page and the browser is rightly complaining that you embed insecure resources (ws:// instead of wss://) into a secure webpage (https://). Thus, what you do is to change your code to use wss:// instead of ws:// and add the forwarding to the internal websocket server also to the ssl part of your nginx config.
– Steffen Ullrich
Nov 21 at 12:09




I'm not sure if I understand your problem correctly. But based on what you show you are embedding a plain websocket connection (ws://) instead of a secure websocket connection (wss://) in your page and the browser is rightly complaining that you embed insecure resources (ws:// instead of wss://) into a secure webpage (https://). Thus, what you do is to change your code to use wss:// instead of ws:// and add the forwarding to the internal websocket server also to the ssl part of your nginx config.
– Steffen Ullrich
Nov 21 at 12:09












What should be my upstream server and listen port#. Also internal IP starts from 127.0.0.1/30 @SteffenUllrich
– Nishanth ॐ
Nov 21 at 12:16






What should be my upstream server and listen port#. Also internal IP starts from 127.0.0.1/30 @SteffenUllrich
– Nishanth ॐ
Nov 21 at 12:16






1




1




The configuration where you forward to (upstream...) should be exactly the same. There is no change needed on the internal websocket server. You only need to change that you a) use wss:// to access the websocket and b) make nginx forward to the internal websocket server also within the ssl part of your configuration. nginx will terminate the SSL connection (i.e. wss://) and forward the data in plain (ws://) so no change to the internal websocket server is needed.
– Steffen Ullrich
Nov 21 at 12:21






The configuration where you forward to (upstream...) should be exactly the same. There is no change needed on the internal websocket server. You only need to change that you a) use wss:// to access the websocket and b) make nginx forward to the internal websocket server also within the ssl part of your configuration. nginx will terminate the SSL connection (i.e. wss://) and forward the data in plain (ws://) so no change to the internal websocket server is needed.
– Steffen Ullrich
Nov 21 at 12:21














But still, I couldn't able to figure it out about where should I need to edit. As I'm getting the same error. So kindly help me with the edited post above @SteffenUllrich
– Nishanth ॐ
Nov 22 at 7:14






But still, I couldn't able to figure it out about where should I need to edit. As I'm getting the same error. So kindly help me with the edited post above @SteffenUllrich
– Nishanth ॐ
Nov 22 at 7:14



















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53411060%2fan-issue-with-connecting-ssl-websocketsocketme-io-nginx%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53411060%2fan-issue-with-connecting-ssl-websocketsocketme-io-nginx%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Berounka

Sphinx de Gizeh

Different font size/position of beamer's navigation symbols template's content depending on regular/plain...