Hi Davenchy ,
at the first , special thanks for your special live torrent stream serivice worked fine for me .
please tell me how to easy deploy live torrent & backend server to make my own at the easiest way to deploy it on heroku.
I know backend server have 'deploy to heroku button' but what changes needed for live-torrent to using backend server & what steps to run it ?
waiting for your response
finest regards
goodbye

Either pass torrent's infohash or the full URL to that torrent file, none of them works on production server http://live-torrent.herokuapp.com. The example url is https://dl.dmhy.org/2020/03/25/57d9d96bcd814e1de92e64f530056ec73479eaf8.torrent

But working on development server.

I am new to node, no idea how to optimize the whole performance,
I deployed live torrent behind Nginx reverse proxy on Azure VM. it works perfectly for single connection with fast speed. The download speed up to 20 MB/s
But once the second download request was established to get the video from the same torrent, it keep waiting until the first download request done. sometime multiple connections could be concurrently streaming but only up to 4 concurrent connections from my testing.
Isn't node serve requests in Non-blocking way? why incoming requests are being queued?
I am pretty sure the quality of torrent is good.
Azure VM specs

OS: ubuntu 18.04 LTS
Memory: 16GB
vcpus：2
bandwidth: upload 1300 mbps, download 1021 mbps

Hi. Project is dead?

When I clicked play button, I got 400 bad request

Request URL: http://live-torrent.herokuapp.com/api/torrent/serve/043dea44be00f5360a30306255f56cadddfebaea/
Request Method: GET
Status Code: 400 Bad Request
Remote Address: 34.243.165.180:80
Referrer Policy: no-referrer-when-downgrade

Access-Control-Allow-Origin: *
Connection: keep-alive
Content-Length: 18
Content-Type: text/html; charset=utf-8
Date: Thu, 26 Dec 2019 05:49:15 GMT
Etag: W/"12-oN+JvVx3oRJFqBNENVRj+k5XN4w"
Server: Cowboy
Via: 1.1 vegur
X-Powered-By: Express

response body

please select file

This isn't really an issue but is there an HTML file with all the code, I'm kind of new to GitHub so I can't really find it.

Thanks

Subtitles are still loaded as insecure connection under ssl. Must allow insecure objects in browser settings.
Thank you for such a wonderful project

Clicking on the link provided in the repository to get to the website leads to an app not found

Please post a link to install the docker image for live torrent version 4.

Kindly add rclone support for auto uploading to gdrive

I install live-torrent on my VPS,often use it to see movies online.But I don't know how to clear media after the movies end.

Can you add rclone support for uploading to grive ?

Search doesn't work for most torrent providers - Request failed with status code 500. Work only Yts and 1337x.

http://127.0.0.1:3000/ 打不开

When I upload captions it doesn't load into the video, so it would be great if you could fix that

Failed to load resource: net::ERR_CONNECTION_REFUSED
:3000/api/torrent/serve/6162001817e88f82c26121321a78715774a9b4f4/Park.Yurskogo.Perioda.3.2001.BDRip.1080p.mkv:1

C:\Users\User\Projects\live-torrent\node_modules\webtorrent\lib\file-stream.js:59
debug('read %s (length %s) (err %s)', p, buffer.length, err && err.message)
^

TypeError: Cannot read property 'length' of undefined
at _torrent.store.get (C:\Users\User\Projects\live-torrent\node_modules\webtorrent\lib\file-stream.js:59:55)
at C:\Users\User\Projects\live-torrent\node_modules\fs-chunk-store\index.js:198:23
at end (C:\Users\User\Projects\live-torrent\node_modules\run-parallel\index.js:18:15)
at done (C:\Users\User\Projects\live-torrent\node_modules\run-parallel\index.js:22:10)
at each (C:\Users\User\Projects\live-torrent\node_modules\run-parallel\index.js:28:7)
at C:\Users\User\Projects\live-torrent\node_modules\run-parallel\index.js:43:37
at C:\Users\User\Projects\live-torrent\node_modules\fs-chunk-store\index.js:191:27
at apply (C:\Users\User\Projects\live-torrent\node_modules\thunky\index.js:44:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9)