So any time I want to access my Media folder on my Synology NAS inside qBittorrent, I have to refer to it as "/media", not "/volume1/Media" to be clear. Mine in the install script are: -v /volume1/docker/qbittorrent:/config \ It was a bit confusing on the directions. I'll give RSS a shot later, but I might not have time until the weekend.īefore you reinstall with the root user, maybe make sure your volumes are configured correctly too. Make sure you delete any related images/containers before trying again, and purge the /volume/docker/qbittorrent folder too in case you've changed important defaults. So (values found using the lookup script): -e PUID=1026 I think the main thing though was installing it to run as the root user instead of my regular user, as the directions had said to. or update a single container: docker-compose up -d qbittorrent You can also remove the old dangling images: docker image prune Via Docker Run. Monitoring folders seems to be working fine for me now ? Once the stack is deployed, go to the containers menu option on the left sidebar and click on logs for the qbittorrent container. qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library. I have successfully downloaded a file and it has been seeding all day. That’s all the configs you need to update and then click on Deploy the stack. The Qbittorrent project aims to provide an open-source software alternative to Torrent. 1 Hi, I have installed qbittorrrent in docker with help from Rustys excellent guide. I had this working flawlessly when I was using qBittorrent on my Mac, but now that it is on the NAS, I cannot get it to work. Replace /PATH/TO/qbittorrent in the stack config with the response you got. volume1/Media/OneDrive Torrents/TV Shows and qBittorrent is setup to monitor these folders. When I find a torrent I want to DL, I save the torrent file to one of my torrent folders on Microsoft OneDrive, then, I have OneDrive setup to sync the folders to my NAS using Cloud Sync. I've also set up qBittorrent to monitor specific folders on my NAS to automatically download torrents, from a folder that is synced to a OneDrive account, but qBittorrent isn't doing what I need it to do. I've added a new RSS Subscription (from ShowRSS) under the RSS Tab, but I cannot get the automated RSS Downloader to work. some issue with that one but no worries for me since I could change one.I just installed qBittorrent v4.3.8 on my Synology NAS and access it via the WEB UI.īut, I seem to be having some problems. Clone the repo npm install npm start npm run lint (to format the code) docker-compose up -d (starts a qbittorrent docker, optional) Open the WebUI on localhost with the default username admin and. Alternative methods - May work for older QBit versions. Removed the docker/reinstalled, Tried again with additional step of deleting all appdata for qbittorrent, problem persists. use hotio's qbittorrent docker image, that comes pre-packed with VueTorrent. WebUI shows speeds as 'udnefined', and lots of stuff (eg, torrent name, size, etc) are all blank. I wonder if that works with all apps like Sabnzbd. Updated this docker and experiencing lots of problems now. you do need to reinstall the app and delete all the data from appdata!Īlso you have to add the container port info as well if that wasnt clear enough 6666:6666 That should fix all the issues for everyone. Switched it to advanced, and I can change the default launch URL as well. ![]() Hopefully this helps you or anyone else trying to change their port!Įdit: I figured out that I had the view on basic. I'm still trying to figure out how to change the default webpage since it seems hardcoded to 8080. However, clicking WEBUI on your docker in the UnRaid UI will yield a webpage opening with :8080 which won't load. Value: 6666 (again, whatever your new port is)Īpply this and your UI should now work on the new port. ![]() ![]() To fix this, you need 2 changes from the default config.Ĭreate a new one 6666:6666 (whatever your new port is) Sample Docker Compose configuration for running qBitTorrent as a container routed through another Mullvad container. With the base settings, any time you change the port in the QBT interface, it will reset to 8080 when rebooting the docker. Do you know what I am doing wrong.Īre you changing it in the Qbt WEBUI settings or the container?Įdit: I found I had the same issue as you, but was able to figure it out. ![]() The port seems to change back every time I change the web port from 8080 to 8081.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |