Dht Qbittorrent
Destiny Olatunji
So far I've read through the OMV 6 documentation, watched 5 different videos on installing qbittorrent on OMV, looked trough the guides in the guide section, googled it multiple times, and looked through this forum itself to see if I could find isntructions, so far I haven't found anything useable. All the videos except one are for previous versions of OMV that look and function differently, the remaining one stops after he gets portainer installed.
So far I have OMV 6 installed, Docker installed, Portainer installed, and on Portainer I'm logged in with linuxserver/qbittorrent on there as both an image and a container using default settings. I have no idea where to go from here, as far as I can tell it's just sitting there doing nothing, appears to have no relation to OMV at all, can't access the qbittorrent web ui through myip:8080, not even sure if there is anything even running technically speaking.
I read through it, didn't understand any of it, no idea what docker compose is or why I would need it, etc, haven't had to use the OMV shell yet and honestly didn't know it exists, I've been doing anything command line from debian. I'll try I guess.
I legitimately can't tell if that's a literal thing you want me to paste or if I'm suppose to substitute it for something like "rmdir /myname/appdata/config". This is basically all brand new to me so most of things that seem self explanatory to a linux expert are arcane to me. I don't know how I would find those folders by command line.
This is all. I typed linuxserver/qbittorrent into the image pull box, pulled it. Added a container the same way, typed it into the docker box in the section for making a new container on portainer. I have done literally nothing else directly involving qbittorrent, and I have never used docker/portainer before or fully setup OMV before so I'm stuck at a brick wall here.
I pointed you to the docker cli section of the docs, not the docker compose section. The cited section is 13 continued lines of code and at most you would have to make changes to five of them.
Reading it now, I have a different setup than the writer of that guide, no SSD, I have 4TB HDD and an SD Card only, I suppose it still makes more sense to store the container on the HDD. Not sure where I should make the directories in this case, or if they were already made automatically.
It says that I'm supposed to navigate to a certain folder, then copy all the stack info into a text file, should I just try to navigate to the docker folder using command line then try to make the text file and paste it in on command line as well?
I do have basic linux and networking familiarity, it's the specific stuff related to navigating around linux to do file operations on CLI, as well as container applications that I have no familiarity with. Is the normal way of accessing shell for OMV just to SSH into the NAS debian command line, or is there some way to do that over the web UI?
You can ssh into OMV if it is headless or if you have a keyboard and monitor connected you can use the console. I suggest ssh even if you have console capability because you can copy and paste from and to OMV via ssh that way if your ssh client app has that capability.
By standard user you mean the non-admin debian linux user? I made a different user inside of OMV, it gets kind of confusing which is which. Making the folder using that command places it in the root directory, correct? That cd command would work globally because it's just basically root/qbittorrent but root is omitted automatically? For the copy and paste, you are suggesting the one from the docker-compose section of the linxserver/qbittorrent page not the one from the docker CLI section? Do you need a separate application or plugin to use docker-compose or is that functionality built into the standard version of docker? Also would I need to launch the container every time I boot up the NAS or would it be booted automatically?
Ran into some wonky business with standard user. I don't think I technically had one setup. I was using the debian shell with SSH on root, I made a new user within the OMV webUI. I can login to either no problems through the NAS directly, and I can login to root from SSH, but I can't login to my standard user from SSH, it just gives me access denied. I tried deleting my OMV standard user, making a new one from scratch from the Debian command line, again I can login to it just fine on Debian, but if I try to login from SSH I get access denied. Looking at the SSHD_config file, pubkeyauthentication is set to yes, passwordauthentication is set to yes, challengeresponseauthentication is set to no, permitrootlogin is set to yes. I can't figure out what's wrong but I can't really continue until I get this figured out.
As for why Malwarebytes blocked QBitTorrent , this is because QBitTorrent , and all Bittorrent software, are what are known as Peer-to-Peer (P2P) applications meaning it connects to many different servers/IP addresses (this is how files are downloaded through QBitTorrent ) and because of this, sometimes QBitTorrent will connect to a server that is also known for hosting malicious content. This is because servers/IP addresses are often shared by multiple sites, so while what you are downloading through QBitTorrent may be perfectly safe, some of the sites hosted on some of the IP addresses that QBitTorrent connects to may be malicious. Such connections are not a threat however, and you may exclude QBitTorrent from the Web Protection component in Malwarebytes to stop the blocks from happening without compromising your protection (your web browser and other critical web facing programs will still be fully protected from malicious websites and other malicious content). To do so, add QBitTorrent to your exclusions using the method described under the Exclude an Application that Connects to the Internet section of this support article.
File sharing involves using technology that allows internet users to share files that are housed on their individual computers. Peer-to-peer (P2P) applications, such as those used to share music files, are some of the most common forms of file-sharing technology. However, P2P applications introduce security risks that may put your information or your computer in jeopardy. Risks of File-Sharing Technology
I am a bit confused about having more than one site on the same I.P. address, so good and bad together. Why would someone put good stuff on a domain that has bad stuff on it thus creating this situation that the site will be blocked.
sorry for bumping this topic but i have similar problem i just installed qbittorrent from official site and run the app and nothing is downloading and this threats was detected (all outbound connections) hmmm