Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remote pairing #3228

Open
Thermalgeek2 opened this issue Apr 23, 2024 · 11 comments
Open

remote pairing #3228

Thermalgeek2 opened this issue Apr 23, 2024 · 11 comments

Comments

@Thermalgeek2
Copy link

Thermalgeek2 commented Apr 23, 2024

hello been using biglybt for some time now, had migrated from vuze
since i live in a house where we share internet we get it free but open port on houses router, only the one i own myself, and while using vuze even if it was only in my room, it was nice to see progress on my phone, but since i migrated to biglybt, i havdt been able to do that no more it just.. hangs, D:
What can i do to fix this?

  • win 10 22h2
  • BiglyBT 3.5.0.0
  • For *nix: Desktop Environment
@parg
Copy link
Contributor

parg commented Apr 23, 2024

Tools->Options->Connections->Pairing shows information about your current pairing deatils. There's a link you can click on there to see current registration details. That opens a webpage - at the bottom there is a "services" section, the "biglyby web remote" plugin shows there as "xmwebui". There should be a test link on the right for IPv4. Try that.

@Thermalgeek2
Copy link
Author

the first link "sid: protocol=https port=9091 [client IPv4] "failed
the tunnel says it succeded,
but when i tried in the biglybt's web remote plugin it says (in bigly bt app downleft of main screen there is a plugin section and its there) it says Attempting direct secured connection: https://xxx.xxx.x.xx:9091/
Failed: Tunnel unavailable for a further 16s due to failure, HTTP GET for https://xxx.xxx.x.xx:9091//pairing/tunnel/create?ac=xxxxxxxx&sid=xmwebui failed, Connection refused: connect
Attempting proxy secured connection: https://pair.biglybt.com/
Failed: Tunnel unavailable for a further 15s due to failure, Authentication failed: Bad authorisation response: {op=4, status=failed}

@Thermalgeek2
Copy link
Author

and thank you for answering so fast :)

@parg
Copy link
Contributor

parg commented Apr 23, 2024

Hard to diagnose these issues. Ignore the tunnel stuff, that isn't supported by biglybt web remote. Perhaps try connecting via HTTP rather than HTTPS and see if that works?

Also, if you are testing from within the same network (e.g. you're at home via wifi on your phone) check what the "Client detected local IPv4" says - that should be the lan address of your computer.

@Thermalgeek2
Copy link
Author

checked without the https and just did http, nothing D :cant even seem to acces it on computer normally either when i go in test , and checked the detected local ipv4 and it is indeed my computers ip adresse

@Thermalgeek2
Copy link
Author

also got a yellow popup saying it failed to listen on web remote

@Thermalgeek2
Copy link
Author

also when i try connect it via access code it seems to be hanging hope all that could help a little

@parg
Copy link
Contributor

parg commented Apr 24, 2024

Check VIew->Log Views->Bigly Web Remote for any logs.

If it is failing to listen then something is borked with your local network setup/antivirus/firewall.

@Thermalgeek2
Copy link
Author

strange.. no errors.. but phone cant find it, and when i try use web, it says Please make sure BiglyBT is running and accessible.but ports are open..

@parg
Copy link
Contributor

parg commented Apr 25, 2024

Any bind ips set in "Options->Connection->Advanced Network Settings [Socket Options]: Bind to local IP address or interface" ?

@Thermalgeek2
Copy link
Author

nothing in the place is written

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants