WebSocket not connected after adding SSL

[Tahmid Khandokar]

Hello! There,

I've installed AMS enterprise edition (pay as you go package) and then I've added SSL with my Domain which is pointed to a EC2 Instance. And it works great. I can login to AMS with a account and also I've added the license.  
Now the problem is when I just try to test LiveApp/WebRTCEE using this URL, [https://golaiv-server.tech/LiveApp] OR [https://golaiv-server.tech/WebRTCAppEE], it shows the WebSocket not connected error. But when I used AMS using localhost it worked fine. For this error I couldn't use WSS to my application. I've added the browser console image in this post. Please help me. 

 

Error:

Thank you.

[Yash]

Hi @Tahmid Khandokar
I hope you are fine.
Currently your server is unreachable. Could you please cross check once?
Also it seems that SSL certificate is not installed as it is showing unsecure.

Regards,
Yash

[Tahmid Khandokar]

Hello @Yash

Hope you're well.
Actually I've stopped my server for some reason. Now you can check through the given link. Please.
 

Edited November 15, 2022 by Tahmid Khandokar

[Tahmid Khandokar]

And if the SSL is not installed, then I think I couldn't found the cert.pem, privkey.pem, etc. in the directory "/etc/letsencrypt/live/www.golaiv-server.tech". Right?

[Tahmid Khandokar]

Also you can have a look at the security rules in EC2 instance

[Connessione]

4 hours ago, Tahmid Khandokar said:

Also you can have a look at the security rules in EC2 instance

 

Setup your SSL as you normally do and then use SSL Labs to self diagnose problem with your SSL certificate. Its helps in most cases.

Edited November 15, 2022 by Connessione

[Yash]

FYI please,
@Tahmid Khandokarresolves the issue by removing the Nginx server.

Below configuration can be used to run the Ant Media Server behind the Nginx reverse proxy:
 

events {
    worker_connections 1048576;
    multi_accept on;
    use epoll;
}

http{
server { 
            listen 443 ssl;
            ssl_certificate /etc/letsencrypt/live/your-domain-name/fullchain.pem;
            ssl_certificate_key /etc/letsencrypt/live/your-domain-name/privkey.pem;
            server_name your-domain-name;

            location / {
                proxy_pass http://your--ams-server-ip:5080/;
                proxy_http_version 1.1;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header Host $host;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "Upgrade";

            }
        }
}

 

[Leigh Green]

Something to note here is that Websockets are a different Protocol that may not automatically be passed via a Proxy server without adding the Web Socket support.  This goes for Apache and NGINX (which with NGINX is the Upgrade option.)

Something I found to fix an issue like this for our On-Premise server - we use a Sophos XG firewall, and you have to change from a standard Proxy connection to one with Path Specific Routing then enable Websocket Passthrough.

Link for enabling that on such a device is here below.

https://community.sophos.com/sophos-xg-firewall/f/discussions/132910/pass-a-websocket-connection-through-waf