allanp81

Compression? De-duping?

Yes it seems to reinstate it when there is an update for the docker. What would you suggest? Remove the container and reinstall (without removing the config directory?).

Every time this updates itself, it fails to load as I don't have a www subdomain. The only way I can then get it to work is to edit the container and remove the subdomains section. Nothing in my setup changed so I'm assuming something in the way the docker works changed. How can I get around this?

Duplicati works perfectly for me, even backing up to an external hard drive via USB. Yes, it's slow, but usb 2 is 40mbps so I wouldn't expect miracles Sent from my Nexus 5X using Tapatalk

An SSD could potentially write at 500Mb/sec whereas a maxed out Gigabit connection would be just over 100Mb/sec.

I gave up and just let it recreate the appdata directory. I only had about 45Gb uploaded so I just started again after I'd migrated my account across.

Cool thanks, I can see it now. Whitelisting doesn't seem to work though and there's too many things listed to try and blacklist them all.

How though?

Did you ever get this working? I can't get it working either.

I've tried using this docker after migrating my account and for some reason it won't let me login. The username and password work fine via their webpage.

Ah, I see why, because that directory would otherwise be created under /tmp?

Why would that create a share named httpserver if you don't mind me asking?

This is the output from updating the docker: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="duplicati" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 8200:8200/tcp -v "/mnt/cache/":"/tmp":rw -v "/mnt/disks/BUFFALO_External_HDD/Backup/duplicati/":"/backups":rw,slave -v "/mnt/user/P/":"/source":ro,slave -v "/mnt/cache/appdata/duplicati":"/config":rw linuxserver/duplicati a1b4a215c1f22c23e12a7d5675ab3d7f83eb0a9590e97008c63faeb2bbc3840b I'm not sure if this is what you mean by run command. If I bring up the log from the row under docker it shows me: I have about 10 other dockers and don't seem to have this issue with any others.

This docker seems to create a public share named "HttpServer" whenever it starts that the fix common errors plugin then flags up as a problem. Any one know this share is created and what its purpose is?

I emailed them asking for a refund as I'd bought a years subscription less than a month and they've refused, claiming that they're honouring all subscriptions. Why would I want to continue with them after for more money and living in fear that they'll do this again? Bunch of cowboys if you ask me.

I figured it out eventually, I found the section in the source where SMB paths are mounted as cifs. I couldn't figure out the right syntax on my own as I was getting odd filenames appearing when mounting without the correct switches.

I've asked for my money back, I literally signed up about 3 weeks ago. Why would I want to migrate to a more expensive offering when they can close that service as well whenever they feel like it.

That's great, I literally only just signed up to it and they've charged me!

I had a script that ran the rc.unassigned script from the unassigned drivers plugin. The path to is something like /usr/local/plugins. This works fine if I manually kick the script off but fails when the script runs via a schedule, it claims the path doesn't exist.

Hmm, that's what I thought but I seem to get different results depending on how the script is initiated.

When running a user script manually, does it run as a different user versus being run via a schedule?

Can anyone tell me how this plugin uses smbclient to mount an smb share? I'm trying to utilise the rc.unassigned script to mount the listed share via a cs user script but it seems to fail with the path. If I can work out the smbclient syntax instead then it won't matter. I have trawled through the source on github but struggling to see how it works.

Why the bragging post?

For me personally, I see massive latency spikes if I change it to anything suggested in this thread. Leaving it on cache='writeback' gives me greens the whole time.

When I had similar problems it turned out to be 1 of my sticks of ram