![]() This entry was posted in security, self hosting, torrents and tagged HTTPS, self hosting, SSL, TLS, torrents on Augby pizzapower. If you want HTTPS with an official certificate, try out Let’s Encrypt. Again, this isn’t the best way to do this, but it’ll work. Now you have HTTPS with your qBitorrent WebUI. So click there and then click on confirm security exception. It’ll query the site for the cert and then the checkbox to permanently store this exception will become clickable. Use your URL in the location box on the add security exception screen. add an exception in FirefoxĮnter the URL of your qBittorrent WebUI. Click on the servers tab, and then click add exception. The certificate manager, as seen below, should pop up. Then scroll down to find certificates where you will see the option to view certificates, so click on that. After all, they’ve probably already cracked your WebUI password, and can run arbitrary python code, as I talked about here.Īnyway, in Firefox, go to settings > privacy & security. ![]() If the bad guy has gotten this far, your qBittorrent app is probably the least of your worries. You probably shouldn’t do this, but oh well. You can optionally add an exception in your browser that will bypass this warning message. The browser is just warning you that this isn’t an official cert from a trusted authority – everything is still encrypted. Warning you’ll get in ChromeĬlick advanced and then proceed to ip-address (unsafe) and you’ll be able to log in to your web interface. Now, when you visit the URL of the qBittorrent web interface, you’ll have HTTPS, but you’ll get a warning. Then, enter the paths to the certificate and the key that you just created. In qBittorrent, go into tools > options > Web UI. Click through these, or enter whatever you want – it doesn’t matter You can just click through all of the fields below – it won’t affect the operation of your certificate. openssl req -x509 -newkey rsa:4096 -nodes -out cert.crt -keyout key.key -days 365 In a Linux terminal, run the following command to create cert.crt and key.key – a key and certificate pair. Anyway, if you want easy HTTPS with qBittorrent, read on. Some will say you don’t need HTTPS then, but that is a discussion for another day. Use Wireguard to tunnel into your home network, and access it that way. It feels like the dockerized torrent client needs a heavy load from outside to be able to use the full bandwidth, and when the network is idling it limits the network speed for some reason.Wanna use HTTPS with your qBittorrent WebUI, but don’t know how? First off, you probably shouldn’t expose the qBittorrent WebUI to the internet. Nothing helped, the only way to get the expected download speed in the container if I start a download that is not within the dockerized torrent client. Several proxy settings (with and without VPN)Įverything is the same without VPN and/or proxyĬompletely destroyed the container and deleted the images and networks and rebuiltįactory reset and tried that way (deleted config folder and rebuilt the container) Several VPN servers and providers (NordVPN, Mullvad) ![]() Tested different containers (deluge and qbittorrent)ĭeluge ltConfig plugin with Best Performance Seed settings I am after 24hrs of debugging session, I've tried everything I could find on the internet: So this is not a networking or a disk IO problem, since I can download a file and write the disk fast even directly from the container outside of the torrent client. Weirder if I open a terminal to the container, and I go into the download folder and start a huge file download with wget it's lightning-fast, and the torrent download inside the docker speeds up as well. If I stop downloading on the host OS, the download speed decreases back to around 500 Kb/s in the dockerized torrent client. If I try to download the SAME torrent with qBittorrent from the host OS (outside of docker), the download speed is good AND increases the download speed within the docker container. If I try to download the SAME torrent with qBittorrent from the host OS (outside of docker), the download speed is good AND increases the download speed within the docker container. What is really weird is, that if I start any download on the host OS, the torrent download goes fast. When I start a download it starts fast, then it slows down after ~1 minutes (around 500 Kb/s). I tested with deluge and qbittorrent within a docker container. Something weird is happening with my containerized torrent download speed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |