cyberteer

Hey @jjross @mraerosmith in regards to the "Unable to find EVS commandline utilities" error you both encountered... would either of you recall if when you first added the idrive docker if you created a folder/directory under /user/appdata for the idrive docker to use or did you simply let it "auto-create" upon launching the container?

Thank you @jjross for your input. Two reports is certainly more than coincidence. As mentioned, I don't seem to be able to replicate the issue on my Unraid installation and I wasn't able to replicate it on Ubuntu VM running docker that I'd setup to see if I could. I will raise the issue with the container builder as perhaps there is something there.

I appreciate the props, but still doesn't explain why the container failed initially. I suspect that if you make a change to the docker template (change volume path to backup something else or add another volume path) that the container gets rebuilt and you'll be back to having to run the update again. I'm glad to know you are up and running. iDrive really is the least expensive backup option that I have found. Simply put $10/year for 500GB is a fantastic deal. In addition, I am quite pleased with the speed at which backups have executed. Good luck!

@mraerosmith can you try executing: ./idrive -C and force it to update even if it says it is the same version.

I am on Unraid version 6.12.10, If you are older, it might be attributable to an older version of docker. What do you see when you execute: docker version from an Unraid terminal window?

Yes, I am sorry as I am at a loss as to why that is happening. Something is corrupt or corrupting the container, as I again pulled the image on a different computer and it works as expected.

@mraerosmith To give an update, I have removed the container, and the docker image and redeployed from scratch (keeping my config) and I am not getting that "EVS error". Additionally, I deployed the container on a separate Linux VM without any issues. I am left thinking that something happened to the image that you downloaded which is causing that EVS error. It seems the EVS utilities is part of the idrive for Linux install which gets executed inside the container you are creating. I would suggest, removing any existing iDrive containers from the Unraid GUI. Then in a terminal window, use the following command to remove the image: To list the images, execute: docker images Find the snorre0815/idrive-docker image ID, and execute: docker rmi <insert-image-ID-for-snorre0815/idrive-docker> You don't need the < > brackets. Next, to show any "dangling" images, execute: docker images -f dangling=true If any are found, then execute: docker image prune After all that, use the template to recreate the iDrive container, ensuring paths are pointed where you want them. As for the blank template issue, from the filename I am thinking you already had my-idrive.xml as a template -- unless you delete it from the //boot/config/plugins/dockerMan/templates-user directory you shouldn't need to recreate. Let me know how it goes.

What is that option "Community Applications Conversion" = true?? It was not in the template and I do not have it in my own config either. Can you set to "false" or remove it and try again?

I pulled the container again, it works. That EVS error you see appears before you've entered any command. That is the container itself which does not make a lot of sense. In the docker settings can you try changing the Shell to Shell and click apply. That will delete the container and rebuild.

Just to confirm, you are inside the docker container at the # prompt when entering ./idrive -a? Does ./idrive --account-setting give you the same error? The screen capture below is me running ./idrive (no options). When entering the console for the container -- you should immediately be in the path /opt/IDriveForLinux/bin (as shown in the screen capture.

So iDrive Support has confirmed to me that version 3.x of iDrive for Linux is now required in order to connect and backup any content. As was previously noted the version 3.x now uses a binary instead of all the pearl scripts. So any documentation that references ./account-setting.pl or any .pl script should be considered deprecated. As such, I have setup and tested the 'snorre0815/idrive-docker' container that includes the version 3.x binary and can confirm that it does work (connects, computer appears in the dashboard, and able to backup content). Now for anyone that maybe interested here is a revised list of steps to setup this iDrive container on Unraid using the snorre0815/idrive-docker image: (Disclaimer: I acknowledge that credit goes to @taverty @LoneStar@ocyberbum @JoergHH for their work effort as I am simply putting all their hardwork together in a single post) iDrive Docker for Unraid - April 2024 iDrive Account Creation (If you do not have an account already) 1. create an iDrive account https://www.idrive.com/idrive/signup 2. Recommend using the default iDrive encryption key. If you are absolutely set on using your own encryption key remember to store a copy in a very safe place! 3. Setting or not setting the 2FA is your choice, the version 3.x iDrive for Linux is compatible and does work with 2FA Installing the 'snorre0815/idrive-docker' iDrive Docker container: Option #1 -- manual install 1. Search for idrive under APPS tab 2. Click on link labeled: "Click Here To Get More Results From DockerHub" 3. Choose snorre0815/idrive-docker (https://hub.docker.com/r/snorre0815/idrive-docker/) 4. Configure docker container with required paths as below Must enable "ADVANCED VIEW" to expose the Icon field Icon URL: https://static.idriveonlinebackup.com/source/images/favicon.ico Path to Add Perms Container Path Host Path config R/W /opt/IDriveForLinux/idriveIt /mnt/user/appdata/idrive/config backup R/O /home/backup /mnt/user/ ** Unraid includes TZ variable when launching a container set to your selected timezone --End Option #1 -- Jump down below to continue -- Option #2 - Template install In a terminal on your Unraid, navigate to: /boot/config/plugins/dockerMan/templates-user # cd /boot/config/plugins/dockerMan/templates-user Next use nano (or your preferred editor) to create a file called my-idrive.xml # nano my-idrive.xml Copy the following XML into the editor: <?xml version="1.0"?> <Container version="2"> <Name>iDrive</Name> <Repository>snorre0815/idrive-docker</Repository> <Registry>https://hub.docker.com/r/snorre0815/idrive-docker</Registry> <Network>bridge</Network> <MyIP/> <Shell>bash</Shell> <Privileged>false</Privileged> <Support/> <Project/> <Overview/> <Category/> <WebUI>https://www.idrive.com/idrive/home/<WebUI/> <TemplateURL/> <Icon>https://static.idriveonlinebackup.com/source/images/favicon.ico</Icon> <ExtraParams/> <PostArgs/> <CPUset/> <DonateText/> <DonateLink/> <Requires/> <Config Name="Config" Target="/opt/IDriveForLinux/idriveIt" Default="" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/idrive/config</Config> <Config Name="Backup Path 1" Target="/home/backup" Default="" Mode="ro" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/user</Config> </Container> Save / write file to disk Then in Unraid Docker, click ADD CONTAINER From the template drop-down find and select idrive --End Option #2 5. Now click 'Apply' to create the container Next, use either option: In your Unraid terminal execute: docker exec -it idrive /bin/bash OR Login to iDrive Docker Container Console, by clicking the iDrive Docker icon and selecting 'Console' from the menu Once connected and inside the container, execute: # ./idrive -a Follow the remaining prompts to configure your account REMINDER: When prompted for a Backup Location, recommend using HOSTNAME for easy identification If you require further assistance, see https://www.idrive.com/readme#install When finished, use the iDrive Web Dashboard (https://www.idrive.com/idrive/home/) to configure your backup, your shares will be located under "/home/backup". Enjoy!

From what I understand -- if you have unchecked it in the web UI, that disables the scheduler job that gets called regularly to check for file changes -- however, the CDP service will always show as running, but you should find the job disabled (scheduler) when checking from the console.

Have you tried https://hub.docker.com/r/snorre0815/idrive-docker/? JoergHH (see below) seems to have had some success using it. JoergHH any updates?

Taverty -- I noticed that you updated your docker container for iDrive for Linux. Is it upgraded to version 3.20 or still on v2.38?

Thank you for your efforts in finding a root cause. It is certainly appreciated even though it cannot be resolved at this time. Also, my apologies to you. The intention behind the "This would be an immediate no" was not to irritate. What I failed to articulate was that all other variables were identical whether in Incognito mode or not. Thus the filename, which is auto populated, was the same and therefore should not be a factor. Thank you again. Your work is valued and UD truly fills some huge gaps within Unraid.

This would be an immediate "no". As using the same USB drive (so same partition name) whether incognito or not and saving the script works when no using incognito. That seems to be the only difference... everything else is the same. Same computer, same USB drive, same script just incognito or not. I'll change the logging level and re-test and let you know.

The PHP Settings had nothing, however, I want to note that the "error reporting level" on that page is set at 'Default'. As for the browser debug console, the following errors were noted after attempting to edit and save changes to an existing UD script. Additionally, the following was identified as the "Violating node" (blue section) element.style { display: none; } input[type=checkbox] { vertical-align: middle; margin-right: 6px; } user agent stylesheet input[type="checkbox" i] { background-color: initial; cursor: default; appearance: auto; box-sizing: border-box; margin: 3px 3px 3px 4px; padding: initial; border: initial; } user agent stylesheet input { font-style: ; font-variant-ligatures: ; font-variant-caps: ; font-variant-numeric: ; font-variant-east-asian: ; font-variant-alternates: ; font-variant-position: ; font-weight: ; font-stretch: ; font-size: ; font-family: ; font-optical-sizing: ; font-kerning: ; font-feature-settings: ; font-variation-settings: ; text-rendering: auto; color: fieldtext; letter-spacing: normal; word-spacing: normal; line-height: normal; text-transform: none; text-indent: 0px; text-shadow: none; display: inline-block; text-align: start; appearance: auto; -webkit-rtl-ordering: logical; cursor: text; background-color: field; margin: 0em; padding: 1px 0px; border-width: 2px; border-style: inset; border-color: light-dark(rgb(118, 118, 118), rgb(133, 133, 133)); border-image: initial; padding-block: 1px; padding-inline: 2px; } a { color: #486dba; text-decoration: none; } style attribute { --color-alpha: #f2f2f2; --color-beta: #1c1b1b; --color-gamma: #999999; --color-gamma-opaque: rgba(153, 153, 153, 0.25); --shadow-beta: 0 25px 50px -12px rgba(28, 27, 27, 0.15); --ring-offset-shadow: 0 0 #1c1b1b; --ring-shadow: 0 0 #1c1b1b; } body { font-size: 1.3rem; color: #1c1b1b; background-color: #f2f2f2; padding: 0; margin: 0; -webkit-font-smoothing: antialiased; -moz-osx-font-smoothing: grayscale; } html { font-family: clear-sans; font-size: 62.5%; height: 100%; } ::-webkit-scrollbar { width: 10px; height: 10px; background: transparent; } ::-webkit-scrollbar-corner { background: lightgray; border-radius: 10px; } ::-webkit-scrollbar-thumb { background: lightgray; border-radius: 10px; }

Google Chrome (latest version)

My suggestion appears to have been requested a couple times already using differing terms/references: As suggested by the last requestor, this is a relatively easy modification -- that could be fulfilled by simply allowing the "from" or "sender" name to be included in the existing field "Sending email address" under the SMTP Settings for Notification Settings. The specification is one of the following: Sender Name <[email protected]> "Sender Name" <[email protected]> "Sender Name <[email protected]>" Alternatively, a "new" field could be added under the SMTP Settings for Notifications Settings titled "Sending display name" keeping it consistent with current GUI terminology used in Unraid. Either way I think this feature is long overdue.

I wanted to add to the discussion below as I believe I have some relevant information: I am on the latest version of Unraid (6.12.10) with the latest UD plugin and experience the same issue that I am UNABLE to create new scripts using the prescribed method (click default, edit script, click save) -- as the screen simply refreshes after clicking save and the script is gone. The caveat that I think was perhaps overlooked by user unraid-550529 was that they were accessing the GUI in Incognito mode. As I can successfully perform the same operation (click default, edit script, click save) provided I am not using Incognito mode. As an admin I typically default to using Incognito mode and attempting to create a new script does not appear to work consistently when in Incognito mode.

I have encountered this issue also -- and it is impacting my migration from Synology to Unraid.