WebTorrent doesn't seem to work

[tiotrom]

• OS and version: Manjaro Gnome
• BiglyBT Version Number: biglybt 2.0.0.0-1

I have several torrents created with Webtorrent for our trade-free.org website. Add them to Bigly. Enable Webtorrent plugin and add Webtorrent tracker with the following settings:

I am behind a VPN with port forwarding. I am downloading and uploading torrents for many eyars now. In Webtorrent the same torrent files work without a problems.

So, in BiglyBT I cannot make it work with the Webtorrent technology. The "caveats" (chromium window open) is not even opening - clicking LAUNCH does nothing. I Tested with Chromium and Ungoogle Chromium.

What am I doing wrong?

Thank you!

[TuxPaper]

parg will know more about webtorrent, but in the meantime, check if the Help->Getting Started page shows. If it doesn't, try installing libwebkitgtk-3.0 or similar package on your OS. This should get that page working, and maybe webtorrent.

[tiotrom]

That page works

[Flingafu]

I am also encountering the same issue, no window pops up when I click launch, my help->getting started page works

[parg]

The plugin comes with a bundled chromium browser. Go to

~/.biglybt/plugins/azwebtorrent/browser_71.0.3578.92.2

and try to launch ./chrome

[tiotrom]

Ok I get this error:

[tio@tio-pc browser_71.0.3578.98.2]$ ./chrome
[2998:2998:0729/175717.665327:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.9oo91esource.qjz9zk/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
Trace/breakpoint trap (core dumped)

My kernel is 4.19.60-1-MANJARO

[parg]

how about if you rename chrome to chrome.app (for example) and then create a new file called chrome with the contents

./chrome.app --no-sandbox

and chmod+x the new file?

[tiotrom]

I am not that knowledgeable about this I'm sorry. If you can please give me more detailed instructions so that I don't break anything with bigly. I understand to rename this one: to chrome.app for example.

Then create a new file or a folder? Then what to copy more exactly?

By the way it works with

[tio@tio-pc browser_71.0.3578.98.2]$ ./chrome --no-sandbox

It opens the chrome window. But I am not sure if that affects bigly in any way?

[parg]

No problem, try the following in a terminal window in the same folder as the you tried the ./chrome --no-sandbox

rename chrome to chrome.app:

mv chrome chrome.app

create a new file to launch the renamed chrome.app with the no-sandbox parameter:

echo "./chrome.app --no-sandbox" > chrome

make the new file executable

chmod +x chrome

Hopefully the chromium browser will now launch when you type

./chrome

If this is the case then launch BiglyBT and see if the webtorrent integration is now working

[tiotrom]

Now it worked. Thanks! My follow up questions are:

1. How do I properly check if it works? We this trade-free.org website that streams videos via webtorrent. Generally I am testing by opening it and I'll see my Webtorrent application making upload. But BiglyBT does not. It doesn't seem to connect via BiglyBT.
2. When Bigly works, does it open a new Chrome instance for each webtorrent instance?

[parg]

There should only be a single chromium browser opened by BiglyBT to handle all webtorrent network traffic. When running BiglyBT with a download that has a webtorrent tracker the chromium window should automatically open and you should see any connected webtorrent peers within the browser window.

[tiotrom]

I see this window being opened automatically Now I don't understand which torrent opened it and where can I see the connected peers and/or speed.

[tiotrom]

As an update: I currently have 2 chrome windows opened by biglybt....same as above (is a simple window). Does not show the peers or anything.

[tiotrom]

I woke up to this this morning So many chrome instances opened...

[parg]

Try performing the following command in the same place as before but with the additional $*

echo "./chrome.app --no-sandbox $*" > chrome

[tiotrom]

Done it. Restarted bigly. Same behavior...

[parg]

Does the chrome window that opens at least have the title 'BiglyBT WebTorrent Protocol Proxy' rather than the default start page? If not then please execute the following in

~/.biglybt/plugins/azwebtorrent/browser_71.0.3578.92.2

cat chrome

and tell me what the result is

[tiotrom]

No. It is the default Chrome homepage.

cat chrome outputs:

[tio@tio-pc browser_71.0.3578.98.2]$ cat chrome
./chrome.app --no-sandbox 

[parg]

You didn't make the change correctly / in the right place - the command

echo "./chrome.app --no-sandbox $*" > chrome

should have resulted in the 'chrome' file containing an additional $* after the --no-sandbox

[tiotrom]

I am outputting the same command [tio@tio-pc browser_71.0.3578.98.2]$ echo "./chrome.app --no-sandbox $*" > chrome In the ~/.biglybt/plugins/azwebtorrent/browser_71.0.3578.92.2

Is that what I should do?

[parg]

yup - try doing it again and see if the 'cat' command shows the change. You could try deleting 'chrome' before applying the command to see if that helps

[tiotrom]

Ok, so. I did this again:

[tio@tio-pc browser_71.0.3578.98.2]$ echo "./chrome.app --no-sandbox $*" > chrome
[tio@tio-pc browser_71.0.3578.98.2]$ cat chrome
./chrome.app --no-sandbox 

Then deleted "chrome" file and did it again:

[tio@tio-pc browser_71.0.3578.98.2]$ echo "./chrome.app --no-sandbox $*" > chrome
[tio@tio-pc browser_71.0.3578.98.2]$ cat chrome
./chrome.app --no-sandbox 

Seems like no change.

[parg]

argh, my mistake, you need to escape the $* to prevent expansion. Use the command

echo "./chrome.app --no-sandbox \$*" > chrome

[tiotrom]

Yup :) There we go:

[tio@tio-pc browser_71.0.3578.98.2]$ echo "./chrome.app --no-sandbox \$*" > chrome
[tio@tio-pc browser_71.0.3578.98.2]$ cat chrome
./chrome.app --no-sandbox $*

Now in bigly when I try to "launch"

I get nothing. So you know...

[parg]

ah, redo the 'chmod +x chrome' command as well

[tiotrom]

Ok thanks now it seems to work! :) - I still have to make sure it seeds via webtorrent technology. We are seeding these videos trade-free.org via webtorrent desktop app and as a simple test whenever I visit the website, the webtorrent app starts to upload - meaning it connects to my webtorrent client. In BiglyBT this does not happen it seems. I see no upload despite the chrome windows opening. We want to replace webtorrent desktop app with BiglyBT because Bigly is far superior on all aspects, however so far it seems we cannot do any sort of upload via Bigly for our webtorrent-based videos.

[parg]

Not sure of the implications of using the --no-sandbox flag - hopefully things will work but if not we can try and figure things out.

[parg]

I've created a new version of the plugin, 1.3.4, for BETA users (i.e. you need to join the beta program to get it). It has an updated chromium browser along with a config option to do the '--no-sandbox' stuff. So all you need to do is update to this version and then go to the plugin config (Tools->Options->Plugins->WebTorrent Support) and check the new 'Run the web browser without a sandbox' option

[tiotrom]

How do I join the beta program?

[parg]

Help menu

[tiotrom]

Ok. Done it. Now I get this window all the time If I go to options I see this