geut / discovery-swarm-webrtc

discovery-swarm for WebRTC
MIT License
94 stars 23 forks source link

GET https://localhost:4000/socket.io/?EIO=3&transport=polling&t=NBxR_0e net::ERR_SSL_PROTOCOL_ERROR #18

Open marcoippolito opened 4 years ago

marcoippolito commented 4 years ago

I ran my own signal server:

(base) marco@pc01:~/webMatters/vueMatters/GGC/node_modules/@geut/discovery-swarm-webrtc/bin$ ./index.js
discovery-signal-webrtc running on 4000

and in DiscoverySwarmWebRTC.vue file I put:

<script>
    import swarm from '@geut/discovery-swarm-webrtc';
  const sw = swarm({
    bootstrap: ['localhost:4000']
  })

Executing:

(base) marco@pc01:~/webMatters/vueMatters/GGC$ yarn electron:serve

I get this error:

GET https://localhost:4000/socket.io/?EIO=3&transport=polling&t=NBxR_0e net::ERR_SSL_PROTOCOL_ERROR

image

vue info

Environment Info:

  System:
    OS: Linux 5.3 Ubuntu 18.04.4 LTS (Bionic Beaver)
    CPU: (8) x64 Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
  Binaries:
    Node: 14.3.0 - ~/.nvm/versions/node/v14.3.0/bin/node
    Yarn: 1.22.4 - /usr/bin/yarn
    npm: 6.14.5 - ~/.nvm/versions/node/v14.3.0/bin/npm
  Browsers:
    Chrome: 83.0.4103.116
    Firefox: 77.0.1
  npmGlobalPackages:
    @vue/cli: 4.4.4

I'm developing my app on a local PC where I'm running an NGINX webserver. in the nginx configuration I added:

upstream websocket {
    server ggc.world:4000;
}

server {
    listen 8443 ssl;
    server_name ggc.world;

    ssl_certificate /etc/letsencrypt/live/ggc.world-0002/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/ggc.world-0002/privkey.pem; # managed by Certbot
    ssl_trusted_certificate /etc/letsencrypt/live/ggc.world/chain.pem;
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    location /p2p {
        proxy_pass http://websocket;
        proxy_http_version 1.1;
        proxy_set_header Upgrade "Websocket";
        proxy_set_header Connection "Upgrade";
        proxy_set_header Host ggc.world;
    }
}

How to solve the problem? Looking forward to your kind help. Marco

How to resolve the problem?

noa131 commented 3 years ago

How did u resolve it?

tinchoz49 commented 3 years ago

We are not longer use socket.io, you are using an old version of discovery-swarm-webrtc