webtorrent + webrtc + AWS ec2 server seeding issues

[olalonde]

I'm having trouble seeding a file over webrtc from an ec2 machine (webtorrent-hybrid). Are there any specific ports that need to be opened? I've opened opts.torrentPort and opts.dhtPort in my ec2 security group and both dht + regular bittorrent protocol are working. I can't however seem to download anything from my browser over webrtc which is seeded from that server.

[DiegoRBaquero]

I'm having a similar problem on a DO droplet. There's no firewall rules at all. Have you got any solution yet?

[olalonde]

I also tried disabling firewall rules but not luck. I'm running my app in Docker though which might make things more complex. I also noticed that when I enable webrtc support, my server CPU usage skyrockets.

[Chocobozzz]

@olalonde See webtorrent/webtorrent-hybrid#5

But same here, I can't seed from a Docker image.

[olalonde]

Thanks for pointing to this issue, I'm having same issues as you it seems.

[Chocobozzz]

Finally doesn't seem to be a Docker issue, I can view videos with the host from a webtorrent server seeding inside Docker.

[DiegoRBaquero]

@olalonde have you fixed it? I got a semi-working seeder using xfvb (as fake screen, so no need to install a GUI desktop), electron-spawn (headless electron wrapper) (to make it work as a browser). The problem I have is that the process dies after a few hours (haven't really investigated why).

[feross]

It sounds like you guys got this figured out, and the remaining issues are just related to wrtc crashing after a while and taking a lot of CPU :(

[lock]

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.