![]() Will mount the smb shares to /mnt/downloads and /mnt/hello, and set the download path.Will mount the smb share to /mnt/downloads, and set the download path.This allows accessing either distant smb shares, or local hdd by mounting them first with (sambanas) Samba NAS. You need to check a specific checkbox if you are using smb1. You write on networkdisks your smb paths, then the username and password to get there. I guess other addons also don’t update Hi, that’s exacty that. If not you should check your “Core” log, or reboot the host as this would mean that the Home Assistant is stuck on cache. In your supervisor log, you should have lines that appear like : 21-02-19 12:31:46 INFO (MainThread) Update add-on repositoryĢ1-02-19 12:31:46 INFO (MainThread) Update add-on repositoryĢ1-02-19 12:31:47 INFO (MainThread) Update add-on repositoryĢ1-02-19 12:31:53 INFO (MainThread) Loading add-ons from store: 123 all - 0 new - 0 remove After clicking the addon list will go dark for a couple seconds before coming back. You need to go in the “addon store” tab, click on the 3 dots at top right, and click Reload. Hi, I see the issue : your Home Assistant builds the addon based on its current cache, not on the current version. If I’m the only one with the problem, must be a problem by my side Successfully installed… but version ls113. 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 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. 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 was using the debian shell with SSH on root, I made a new user within the OMV webUI. I don't think I technically had one setup. Ran into some wonky business with standard user. Sorry for the pile of questions, once I get it up and running this will all make more sense to me, there is a lot of potential ambiguity for me though still at this point. 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? ![]() ![]() Display Moreīy 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. Launch the container with docker-compose up -dĬheck that your container is running on Portainer GUI. Make and edit a file named docker-compose.yml: nano docker-compose.ymlĬopy/paste the sample from github editing the values to match your path.Ĭtrl+O, Enter and then Ctrl+X to save and close the editor. Make a folder named qbittorrent: mkdir qbittorrent On the web Gui, add you standard user to the docker group.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |