search

elendirx / web2web

P2P web powered by torrents and blockchain.
2.25k stars 178 forks source link

Broken demo -- 500 and 502 server responses #6

Open meow-sokovykh opened 8 years ago

meow-sokovykh commented 8 years ago

Hello, @elendirx. I'm a journalist from Russia, and our mass media, tproger.ru, has written an article about your project. We really liked an idea of p2p-loading sites and found it quite valuable.

However, during exploration of your project we found out that it doesn't work due to 5xx server responses: web2web_bug_opera The page is sending requests again and again, but responses are always 500 or 502.

After several attempts (performed by several people on different machines) we discovered a way to see your solution is really working --- to load it by Chromium. But even this way the video is not loading and loads of 500 and 502 errors keep occurring in a developers console: web2web_bug_chrome

You can request additional info, if needed. We have written the article anyway (and it seems, like whole our readership liked the idea too), but we still wish you soon will fix the problems :-)

elendirx commented 8 years ago

I'm afraid that this is a webtorrent issue (webtorrent is the javascript library used for torrents). Is it still not working for you? Oh and thanks for the article.

meow-sokovykh commented 8 years ago

Still doesn't work for me (while using Opera browser). Now it's giving me net::ERR_TIMED_OUT errors in addition to 500 and 502 responses.

elendirx commented 8 years ago

Works fine for me. I'm sorry. All I can do here is to ping the author of the webtorrent lib, he might find the log useful. @feross

feross commented 8 years ago

These messages indicate that your browser was unable to open a connection to these tracker servers (tracker.btorrent.xyz and tracker.fastcast.nz). (cc @DiegoRBquero and @jakefb, who run those trackers)

This is probably because these tracker servers are overloaded at the moment. But that's not an issue. There are 4 default tracker servers built into webtorrent, so you're still able to find peers just fine even if you see tracker warnings in the console.

The real reason that you're experiencing this issue is probably that you're on a network with a firewall or NAT that is preventing some of your WebRTC connections from working, and is affecting the performance. Because of your NAT, you won't necessarily be able to connect to all peers.

@elendirx One thing you can do, if you want, is specify a TURN server in your WebTorrent opts object that will be used if P2P connections fail. Though this is not very decentralized, it is a common approach that production WebRTC services do use to make their P2P services more reliable.

elendirx commented 8 years ago

@feross Thank you for the explanation, I'll look into that.

nikitindiz commented 9 months ago

@jhoosy why do you think someone here needs your shitcoins?