-
Notifications
You must be signed in to change notification settings - Fork 170
Remote Pairing
To enable pairing of your BiglyBT client, go to your BiglyBT client and click on Tools-> Remote Pairing. Click the "Turn On" option on the popup in order to install the necessary plugin.
You should then see a screen that lets you know if your client can be controlled remotely, as well as an access code. To pair your web interface with this client go to remote.BiglyBT.com and enter the access code given.
BiglyBT runs a check to see if you can connect to your client outside of your current network. You received this message because the BiglyBT service to check connectivity is down. You may still be able to connect outside of your current network
This error message occurs because your current internet connection doesn't allow you to connect to it from outside of the network. This can happen for two reasons:
- Your network is firewalled
- Your router doesn't support UPnP or NAT-PMP
To fix this you will need to open the remote port, by default this is TCP port 9091. First ensure that the computer running BiglyBT has its firewall/antivirus software configured to allow BiglyBT to act as a 'server' (i.e. accept incoming connections) for the port. Second check your router to see if you can enable UPnP on it - if not you will need to manually configure a port mapping to route incoming connections on TCP port 9091 to your computer. See general discussions on Port Forwarding and Nat Problems as this is an instance of the same issue you can get with incoming peer-to-peer connections when downloading.
If you have an old or damaged certificate store you can get error messages indicating that a 'certification path' could be found, or perhaps that you have an 'invalid keystore'.
From BiglyBT version 5101, build 48 onwards there is a button under Tools->Options->Security to 'reset certificate store'. Try hitting this and letting BiglyBT restart, hopefully that will solve the problem.
The BiglyBT remote should work on any fully functioning browser that accepts cookies. However, we have tested the remote to work on the following browsers.
- Safari (Windows / Mac / iOS)
- Chrome (Windows / Mac / iOS / Android)
- Firefox (Windows / Mac / Android)
- Opera (Windows / Mac / iOS / Android)
- Internet Explorer (Windows / Windows Phone)
There are multiple ways to unpair your web remotes:
- Unpairing all web-remotes from your client
- Unpairing individual web-remotes
To unpair an individual web-remote click the logout button on the top-right portion of your screen, or clear your browser cookies.
Are you behind a firewall?
Make sure that your firewall is not blocking BiglyBT Remote. Try temporarily disabling the firewall to see if this is the cause of problem. In case you are using a 3rd party firewall (like Kerio) try disabling it too. If disabling the firewall helps you will need to configure an exception rule for BiglyBT. It needs to be allowed to listen on port 9091.
The BiglyBT remote uses a browser cookie to store your pairing code. Make sure your browser accepts cookies for this feature to work.
Your BiglyBT client must be up and running in order for you to control it remotely.
If you have a router, BiglyBT uses UPnP or NAT-PMP to try and automatically configure the router so that your web-browser can connect to the BiglyBT client. If your BiglyBT client is running behind a router that doesn't support these protocols, and you haven't manually mapped a port, you will only be able to connect while within your current network. Most routers built in the last two years support these protocols, but they may be disabled. Check with your router manufacturer to see how to enable these protocols.
You can usually manually map a port by logging into your router's adminstrative interface. By default BiglyBT uses TCP port 9091 for this so forward this port to the computer running BiglyBT.
bigly help