Detail guide how to config file config.json

[quanghuy1288]

Detail guide how to config file config.json.
I can not config it

[mrlika]

We will do it but currently working on other P2P functionality.

Everything is very simple. Check the example:
https://github.com/Novage/wt-tracker/blob/master/sample/config.json

Most of the stuff is self-explanatory.

[ckcr4lyf]

Mind if I ask what other features potentially?

[mrlika]

Working on:

• C++ implementation of the tracker that will allow using memory more efficiently comparing to Node.js. On a low-cost VPS that usually goes with 1 vCPU and 1-2GiB of RAM the bottleneck is the RAM.
• Improving and testing this Node.js version of the tracker - looks like memory consumption is better when running on recently released Node.js v12.9.1
• P2P Media Loader issues and improvements

[ckcr4lyf]

C++ implementation sounds great, best of luck

I have a suggestion / request for P2P media loader, functionality for having a stream completely powered by P2P, somewhat like Acestream?

One "server" has a source, which it to "clients" only via P2P, i.e. a WebRTC based connection to the server, for both the manifest as well as fragments.

A partial way to do it is change the HTTP fragment probability to 0, but it still relies on the HTTP for the manifest (.m3u8)

I am trying to understand the library to see if I can do it myself, but seems a bit tricky.

[mrlika]

As far as I know, Ace Stream is not completely powered by P2P. In Ace Stream you have to stream video to their server. Initial video data is loaded from their server. You can see it when streaming stops - they loop the same few seconds of video each time you try to play the stream.

P2P Media Loader has no vendor lock. You can stream through any server\CDN.

I don't know production-ready completely serverless live P2P video streaming solutions. Bittorrent is working on it many years already.

[ckcr4lyf]

Yeah, that is true. Ace stream "contentIDs" need to be validated on their server with their black-box code.

Thanks for the feedback, I shall continue to explore this field. Cheers

[quanghuy1288]

I have clone your project to my centos 7 server (you can check via my httpd http://103.216.120.135:85/p2p/wt-tracker/). Then i install nodejs 12 then run 2 commands:

npm install
npm run build

Then i try to start wt-tracker:
./bin/wt-tracker _config.json (check detail from _config.json; and check pem file which i have used in _config.json in this http://103.216.120.135:85/p2p/keyssl/ )
but it show

listening 0.0.0.0:8000
failed to start the web server: App construction failed

If i run wt-tracker without param:
./bin/wt-tracker
it not show error but my demo p2p-media-loader cannot connect this wt-tracker.
p2p-media-loader-core.min.js:1 WebSocket connection to 'wss://103.216.120.135:8000/' failed: Error in connection establishment: net::ERR_CONNECTION_CLOSED

(you can check my demo p2p-media-loader from this link http://103.216.120.135:85/p2p/custom.html )

[ckcr4lyf]

Try forcing a ws:// connection instead of wss:// (in your HTML page) and see if that works

[quanghuy1288]

Try forcing a ws:// connection instead of wss:// (in your HTML page) and see if that works

Thanks!. It work when i run wt-tracker without config.json

But with config.json wt-tracker still failed to start

[ckcr4lyf]

Try removing the SSL configuration in your _config.json file, specifically this part:

, {
      "server": {
        "port": 8433,
        "host": "0.0.0.0",
        "key_file_name": "/home/vega/p2p/keyssl/server.key.pem",
        "cert_file_name": "/home/vega/p2p/keyssl/server.cert.pem",
        "passphrase": "[redacted]",
        "ssl_prefer_low_memory_usage": true
      },
      "websockets": {
        "path": "/*",
        "maxPayloadLength": 65536,
        "idleTimeout": 240,
        "compression": 1
      }
    }

I'll try and spin up a VPS with wt-tracker and see if I can get it to work with a config.json

[quanghuy1288]

Try removing the SSL configuration in your _config.json file, specifically this part:

, {
      "server": {
        "port": 8433,
        "host": "0.0.0.0",
        "key_file_name": "/home/vega/p2p/keyssl/server.key.pem",
        "cert_file_name": "/home/vega/p2p/keyssl/server.cert.pem",
        "passphrase": "[redacted]",
        "ssl_prefer_low_memory_usage": true
      },
      "websockets": {
        "path": "/*",
        "maxPayloadLength": 65536,
        "idleTimeout": 240,
        "compression": 1
      }
    }

I'll try and spin up a VPS with wt-tracker and see if I can get it to work with a config.json

Ok thanks, it worked when i do as your guide

[mrlika]

I have no good error messages from the underlying uWebSockets.js library about problems with SSL keys and other stuff. That is why just report "failed to start the web server: App construction failed"
I will try to improve the messages.

[quanghuy1288]

I have tried to config ssl. then using it in my demo http://103.216.120.135:85/p2p/custom.html
But error show from console :
WebSocket connection to 'wss://103.216.120.135:8433/' failed: Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID

Could you guide me to fix this problem?