On 9/1/2024 at 5:43 PM, Tolete said:

yup, image stuck on 3.3.3
manual install works, until image maintainer updates or new image become available.

Thank you.  I looked at the manual update and wasn't sure how that would work in UnRAID so I'll take a deeper look at that.

On 4/28/2024 at 12:27 PM, Aractor said:

I was finally able to fix this myself by running the command and confirming the container wasn't getting access to the main storage.

docker exec --user app backblaze_personal_backup ls -la /config/wine/dosdevices/

 

So, I ran this command to manually mount the storage drive.

docker exec --user app backblaze_personal_backup ln -s /backup_volume/ /config/wine/dosdevices/d:

 

Found the solution in the container's git documentation https://github.com/JonathanTreffler/backblaze-personal-wine-container#volumes

I'm trying to Get Backblaze Personal Backup to work, and I'm having the same issue; my shares aren't showing up for backup.

 

So to ask a stupid question (3 actually)....

1) when I use that 2nd command above, is that run in a terminal window on my unraid host, or within the docker itself?  I assume unraid terminal, but the github instructions say it must be "mounted manually within wine", which is confusing me.

2) Do I copy/paste that command exactly, or will I need to edit the "/backup_volume/" portion to point to my local path?  If the latter, what might that look like, exactly?

3) If/When this is all up and running, what happens to the BackBlaze instance that I already have, that's been running for years on my old Windows server?  Am I able to eventually do the 'inherit state' thing, and have it migrate over, or will it have to totally upload all over over again?  I have just over a TB backed up, so I'd hate to start over.  I'd also hate to get banned or whatever if they see 2 machines on the same line, if you get my meaning.

 

TIA for any assistance!

On 4/28/2024 at 12:27 PM, Aractor said:

I was finally able to fix this myself by running the command and confirming the container wasn't getting access to the main storage.

docker exec --user app backblaze_personal_backup ls -la /config/wine/dosdevices/

 

So, I ran this command to manually mount the storage drive.

docker exec --user app backblaze_personal_backup ln -s /backup_volume/ /config/wine/dosdevices/d:

 

Found the solution in the container's git documentation https://github.com/JonathanTreffler/backblaze-personal-wine-container#volumes

I'm trying to Get Backblaze Personal Backup to work, and I'm having the same issue; my shares aren't showing up for backup.

 

So to ask a stupid question (3 actually)....

1) when I use that 2nd command above, is that run in a terminal window on my unraid host, or within the docker itself?  I assume unraid terminal, but the github instructions say it must be "mounted manually within wine", which is confusing me.

2) Do I copy/paste that command exactly, or will I need to edit the "/backup_volume/" portion to point to my local path?  If the latter, what might that look like, exactly?

3) If/When this is all up and running, what happens to the BackBlaze instance that I already have, that's been running for years on my old Windows server?  Am I able to eventually do the 'inherit state' thing, and have it migrate over, or will it have to totally upload all over over again?  I have just over a TB backed up, so I'd hate to start over.  I'd also hate to get banned or whatever if they see 2 machines on the same line, if you get my meaning.

 

TIA for any assistance!

On 4/28/2024 at 12:27 PM, Aractor said:

I was finally able to fix this myself by running the command and confirming the container wasn't getting access to the main storage.

docker exec --user app backblaze_personal_backup ls -la /config/wine/dosdevices/

 

So, I ran this command to manually mount the storage drive.

docker exec --user app backblaze_personal_backup ln -s /backup_volume/ /config/wine/dosdevices/d:

 

Found the solution in the container's git documentation https://github.com/JonathanTreffler/backblaze-personal-wine-container#volumes

I'm trying to Get Backblaze Personal Backup to work, and I'm having the same issue; my shares aren't showing up for backup.

 

So to ask a stupid question (3 actually)....

1) when I use that 2nd command above, is that run in a terminal window on my unraid host, or within the docker itself?  I assume unraid terminal, but the github instructions say it must be "mounted manually within wine", which is confusing me.

2) Do I copy/paste that command exactly, or will I need to edit the "/backup_volume/" portion to point to my local path?  If the latter, what might that look like, exactly?

3) If/When this is all up and running, what happens to the BackBlaze instance that I already have, that's been running for years on my old Windows server?  Am I able to eventually do the 'inherit state' thing, and have it migrate over, or will it have to totally upload all over over again?  I have just over a TB backed up, so I'd hate to start over.  I'd also hate to get banned or whatever if they see 2 machines on the same line, if you get my meaning.

 

TIA for any assistance!

  

On 4/28/2024 at 12:27 PM, Aractor said:

I was finally able to fix this myself by running the command and confirming the container wasn't getting access to the main storage.

docker exec --user app backblaze_personal_backup ls -la /config/wine/dosdevices/

 

So, I ran this command to manually mount the storage drive.

docker exec --user app backblaze_personal_backup ln -s /backup_volume/ /config/wine/dosdevices/d:

 

Found the solution in the container's git documentation https://github.com/JonathanTreffler/backblaze-personal-wine-container#volumes

I'm trying to Get Backblaze Personal Backup to work, and I'm having the same issue; my shares aren't showing up for backup.

 

So to ask a stupid question (3 actually)....

1) when I use that 2nd command above, is that run in a terminal window on my unraid host, or within the docker itself?  I assume unraid terminal, but the github instructions say it must be "mounted manually within wine", which is confusing me.

2) Do I copy/paste that command exactly, or will I need to edit the "/backup_volume/" portion to point to my local path?  If the latter, what might that look like, exactly?

3) If/When this is all up and running, what happens to the BackBlaze instance that I already have, that's been running for years on my old Windows server?  Am I able to eventually do the 'inherit state' thing, and have it migrate over, or will it have to totally upload all over over again?  I have just over a TB backed up, so I'd hate to start over.  I'd also hate to get banned or whatever if they see 2 machines on the same line, if you get my meaning.

 

TIA for any assistance!

55 minutes ago, Elmojo said:

  

I'm trying to Get Backblaze Personal Backup to work, and I'm having the same issue; my shares aren't showing up for backup.

 

So to ask a stupid question (3 actually)....

1) when I use that 2nd command above, is that run in a terminal window on my unraid host, or within the docker itself?  I assume unraid terminal, but the github instructions say it must be "mounted manually within wine", which is confusing me.

2) Do I copy/paste that command exactly, or will I need to edit the "/backup_volume/" portion to point to my local path?  If the latter, what might that look like, exactly?

3) If/When this is all up and running, what happens to the BackBlaze instance that I already have, that's been running for years on my old Windows server?  Am I able to eventually do the 'inherit state' thing, and have it migrate over, or will it have to totally upload all over over again?  I have just over a TB backed up, so I'd hate to start over.  I'd also hate to get banned or whatever if they see 2 machines on the same line, if you get my meaning.

 

TIA for any assistance!

@Elmojo 

1) any docker exec commands you will run from the host terminal. In this case the CLI for unraid.

2) /backup_volume/ is a container path with the default being mounted to drive d within the backblaze docker container. If you edit the docker it's labelled as Storage to backup up. If you wanted to add additional volumes you would create another path variable with a different container path such as /backup_volume2/ and mount it to a different drive letter such as E. Then run the command with the new container path and drive letter for example: docker exec --user app backblaze_personal_backup ln -s /backup_volume2/ /config/wine/dosdevices/e:

3) Tying back to question 2 if you have multiple volumes configured in your existing windows server you will need to ensure when you configure backblaze in unraid that the paths exposed to backblaze match EXACTLY. Otherwise yes you can import the config but backblaze will see the files as all new.

 

For example if you have C:\somefiles in windows it will be a problem since the container's first drive letter available is D:\. Additionally if you have D:\somefolder\somefiles and you expose the path to the backblaze container truncated to d:\somefiles\ then backblaze will see them all as new files. 

Ok...  thanks for the reply. 
I don't think I'm gonna be able to handle this one, it's just too complicated for my brain to untangle. lol
I may be better off migrating to IDrive e2, like I've been thinking about for a while.  I appreciate you taking the time to try to explain, though!

2 hours ago, Elmojo said:

Ok...  thanks for the reply. 
I don't think I'm gonna be able to handle this one, it's just too complicated for my brain to untangle. lol
I may be better off migrating to IDrive e2, like I've been thinking about for a while.  I appreciate you taking the time to try to explain, though!

 

Curious why you would select iDrive e2? I've been looking at migrating to a mass cloud storage too and been looking at Backblaze's storage. Haven't looked at iDrive yet, but curious why you might have settled on them. 

 

Thanks!

11 minutes ago, jmbailey2000 said:

Curious why you would select iDrive e2?

Excellent pricing (2TB for about $75/yr if you sign up for the 2yr plan), and simple setup using Duplicacy docker. 
IDrive themselves even have an excellent tutorial for how to interface with Duplicacy.  It took me maybe 30 mins from docker app search to data being uploaded.  Easy-peasy.
It's also rated at or near the top of the several "best cloud service" searches I did, for whatever that's worth.

29 minutes ago, Elmojo said:

Excellent pricing (2TB for about $75/yr if you sign up for the 2yr plan), and simple setup using Duplicacy docker. 
IDrive themselves even have an excellent tutorial for how to interface with Duplicacy.  It took me maybe 30 mins from docker app search to data being uploaded.  Easy-peasy.
It's also rated at or near the top of the several "best cloud service" searches I did, for whatever that's worth.

 

Hmmmm......going to have to consider that.

 

Thanks!!

Anyone know how to set the time zone variable in the Duplicacy container?  The docs say to use the "TZ Environment variable", but I don't see a way to do that in the template.  It's working fine, but all my backed-up files have incorrect timestamps.

I am trying to get invoiceninja working with my reverse proxy NPM.  i created a cname in cloudflare and a proxy host in NPM but it wont work has anyone got this working?

On 9/19/2024 at 8:54 AM, Elmojo said:

Anyone know how to set the time zone variable in the Duplicacy container?

No one?  Please? 
I have files backing up with incorrect timestamps.

On 9/19/2024 at 6:54 AM, Elmojo said:

Anyone know how to set the time zone variable in the Duplicacy container?  The docs say to use the "TZ Environment variable", but I don't see a way to do that in the template.  It's working fine, but all my backed-up files have incorrect timestamps.

Unraid automatically passed the host timezone into a Docker container as the TZ variable, so you shouldn't need to specify it manually.

 

If you do, simply add a Variable to the template with TZ as the key and your time zone as the value.

53 minutes ago, grtgbln said:

Unraid automatically passed the host timezone into a Docker container as the TZ variable

Mine is not.  The files being backed up all have incorrect timestamps.
I will add the variable and see if that helps, thanks.

 

EDIT:  Well....crap.  Anyone have some ketchup to go with this crow I'm about to eat? lol
It turns out that the Timezone was set wrong on the whole dang server.  I must have forgotten that I needed to set that when I configured this new machine.  Doh.
All is well, obviously.

Edited October 4, 20241 yr by Elmojo
I'm an idiot

For Duplicacy, what license do I need if any to use this docker?

 

Thanks,

What type of speed should I expect uploading to Backblaze using Backblaze Personal Backup?  I'm getting about .7 Mbits/sec.  Is this reasonable or is something wrong?

 

Thanks

On 8/29/2024 at 7:17 PM, Bmalone said:

Same issue.  I gave up.

I was able to get past this error by creating a file (owned by nobody:users) of graylog2-committed-read-offset in the appdata folder (note it's greylog in this container but the container itself is called graylog-I updated them to be the same, even though it doesn't matter).

 

But now I'm stuck again-I get loads of errors like this before the container stops itself:
 

Caused by: java.io.IOException (same stack trace as error #16)
34 errors
	at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
	at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
	at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
	at com.google.inject.Guice.createInjector(Guice.java:87)
	at org.graylog2.shared.bindings.GuiceInjectorHolder.createInjector(GuiceInjectorHolder.java:34)
	at org.graylog2.bootstrap.CmdLineTool.setupInjector(CmdLineTool.java:379)
	at org.graylog2.bootstrap.CmdLineTool.run(CmdLineTool.java:194)
	at org.graylog2.bootstrap.Main.main(Main.java:50)

 

I've suddenly started to get this error whenever I try to download anything.  I've tried restarting the container and trying different videos but it keeps failing.  Any ideas?

 

Error while retrieving info on video with URL https://www.youtube.com/watch?v=HPH0HgotIE4 with the following message: Error: Command failed with exit code 1: node_modules/youtube-dl/bin/youtube-dl -o audio/%(title)s.%(ext)s --write-info-json --audio-quality 0 -x --audio-format mp3 --write-thumbnail --no-clean-info-json -j --no-simulate --dump-json http://www.youtube.com/watch?v=HPH0HgotIE4

Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "node_modules/youtube-dl/bin/youtube-dl/__main__.py", line 14, in <module>
  File "<frozen zipimport>", line 259, in load_module
  File "node_modules/youtube-dl/bin/youtube-dl/yt_dlp/__init__.py", line 4, in <module>
ImportError: You are using an unsupported version of Python. Only Python versions 3.9 and above are supported by yt-dlp

 

On 11/20/2022 at 2:34 PM, Bitbass said:

Well, I found some examples of the run-time flags that are the defaults and just loaded them all into the Post Arguments, adding the tsdb time flag. Looks like it's working. I guess "time" will tell. In the meantime, I found some comments from Jeff Geerling concerning this and there's an open issue for it with Prometheus. Maybe they'll change it for the better in a future release.

@Bitbass Did you find a solution for changing the default retention setting? If so, could you please share it? I have been trying with no luck so far.

Hi, could be possible upgrade the technitium container to the last version (13.2.2)?

 

Thanks 

Hi
I can see that there is a update for Duplicacy. Where can i see the version and what changes in this?

 

Thanks!

your Dozzle template is broken. I removed a bunch of stuff that was in your template and it runs.

 

It only needs

 

# Run with docker compose up -d
services:
  dozzle:
    image: amir20/dozzle:latest
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    ports:
      - 8080:8080

 

to run

In shinobi, when I click the drop down, it's just white. Not sure how to fix.

 

Thanks 

29 minutes ago, PartyingChair said:

In shinobi, when I click the drop down, it's just white. Not sure how to fix.

 

Thanks 

I just tested in another browser, I guess it's an issue in safari because it works fine in Chrome/Firefox. Would love for it to work in Safari if anyone knew what the issue was and how to fix it, but at the end of the day, not a deal breaker