flutter-webrtc / flutter-webrtc-server

A simple WebRTC signaling server for flutter-webrtc.
MIT License
756 stars 304 forks source link

This site can’t be reached #24

Closed theantiqa closed 3 years ago

theantiqa commented 4 years ago

I have created server in aws. and i have setup that project and than start npm,

also got compile success (see below log): but when i am going to start to connect with webrtc using http://52.66.250.53:4443/ws but can't get connection. can you help me what i have to do? even it can't be open in html page in using http://52.66.250.53:8086

--------------------------------------- Server Log ---------------------------------------- ubuntu@ip-172-31-13-9:~/flutter-webrtc-server$ npm start

flutter-webrtc-web@1.0.0 start /home/ubuntu/flutter-webrtc-server npm-run-all --parallel run-server run-webpack-dev-server

flutter-webrtc-web@1.0.0 run-server /home/ubuntu/flutter-webrtc-server node server/index.js

flutter-webrtc-web@1.0.0 run-webpack-dev-server /home/ubuntu/flutter-webrtc-server webpack-dev-server --mode development --https --cert ./certs/cert.pem --key ./certs/key.pem --hot --inline --progress --colors --watch --compress --content-base ./dist --port 8086 --host 0.0.0.0 --open

Start WS Server: bind => ws://0.0.0.0:4442 Start WSS Server: bind => wss://0.0.0.0:4443 10% building 1/1 modules 0 activeℹ 「wds」: Project is running at https://0.0.0.0:8086/ ℹ 「wds」: webpack output is served from / ℹ 「wds」: Content not from webpack is served from /home/ubuntu/flutter-webrtc-server/dist ℹ 「wdm」: Hash: d3d1792c4c5825caa6a1 Version: webpack 4.41.5 Time: 5799ms Built at: 01/08/2020 1:26:07 PM Asset Size Chunks Chunk Names ./index.html 234 bytes [emitted] main.d3d1792c.bundle.js 2.19 MiB main [emitted] [immutable] main main.d3d1792c.bundle.js.map 2.4 MiB main [emitted] [dev] main Entrypoint main = main.d3d1792c.bundle.js main.d3d1792c.bundle.js.map [0] multi (webpack)-dev-server/client?https://0.0.0.0:8086 (webpack)/hot/dev-server.js ./src/index.js 52 bytes {main} [built] [./node_modules/react-dom/index.js] 1.33 KiB {main} [built] [./node_modules/react/index.js] 190 bytes {main} [built] [./node_modules/strip-ansi/index.js] 161 bytes {main} [built] [./node_modules/webpack-dev-server/client/index.js?https://0.0.0.0:8086] (webpack)-dev-server/client?https://0.0.0.0:8086 4.29 KiB {main} [built] [./node_modules/webpack-dev-server/client/overlay.js] (webpack)-dev-server/client/overlay.js 3.51 KiB {main} [built] [./node_modules/webpack-dev-server/client/socket.js] (webpack)-dev-server/client/socket.js 1.53 KiB {main} [built] [./node_modules/webpack-dev-server/client/utils/createSocketUrl.js] (webpack)-dev-server/client/utils/createSocketUrl.js 2.91 KiB {main} [built] [./node_modules/webpack-dev-server/client/utils/log.js] (webpack)-dev-server/client/utils/log.js 964 bytes {main} [built] [./node_modules/webpack-dev-server/client/utils/reloadApp.js] (webpack)-dev-server/client/utils/reloadApp.js 1.59 KiB {main} [built] [./node_modules/webpack-dev-server/client/utils/sendMessage.js] (webpack)-dev-server/client/utils/sendMessage.js 402 bytes {main} [built] [./node_modules/webpack/hot sync ^.\/log$] (webpack)/hot sync nonrecursive ^.\/log$ 170 bytes {main} [built] [./node_modules/webpack/hot/dev-server.js] (webpack)/hot/dev-server.js 1.59 KiB {main} [built] [./node_modules/webpack/hot/emitter.js] (webpack)/hot/emitter.js 75 bytes {main} [built] [./src/index.js] 166 bytes {main} [built]

cloudwebrtc commented 4 years ago

You need to confirm using WS to connect to port 4442 and WSS to connect to 4443。

theantiqa commented 4 years ago

i have started server once again and its showing me as below.

Start WS Server: bind => ws://0.0.0.0:4442 Start WSS Server: bind => wss://0.0.0.0:4443 10% building 1/1 modules 0 activeℹ 「wds」: Project is running at https://0.0.0.0:8086/

now can you guide me how to open html page in or which url is use to connect with webrtc instead of demo.webrtc.com

or can you give me you skype. so it will be good for me to get guide from you by screen share.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.