16 minutes ago, Pete0 said:

Since I had the problem last time I am pretty sure not to have messed with the container or it's configruation too much. Only thing that I see that is different from other working containers is that the appdata directory of firefox has permissions

You can change that by creating a variable like this:

 

But that wouldn't change much, even when it stops working. But I really can't think what causes this on your system because it seems that you are the only one who get that error.

is anyone running into issues with the latest photoprism release? the web UI is inaccessible and the container log doesn't seem to show any errors

 

 

started 220517-bookworm as root (amd64-prod)
init: updating filesystem permissions
PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates
started 220517-bookworm as root (amd64-prod)
init: updating filesystem permissions
PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates

 

Edited May 17, 20224 yr by ooooooooooooo
add code block

4 minutes ago, ooooooooooooo said:

is anyone running into issues with the latest photoprism release? the web UI is inaccessible and the container log doesn't seem to show any errors

 

 

Yes, have the same issues suddenly.  Cannot access webui at all.

 

started 220517-bookworm as root (amd64-prod)
init: updating filesystem permissions
PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates
Problems? Our Troubleshooting Checklists help you quickly diagnose and solve them:
https://docs.photoprism.app/getting-started/troubleshooting/
file umask....: "0002" (u=rwx,g=rwx,o=rx)
home directory: /photoprism
assets path...: /opt/photoprism/assets
storage path..: /photoprism/storage
config path...: default
cache path....: default
backup path...: /photoprism/storage/backups
import path...: /photoprism/import
originals path: /photoprism/originals
switching to uid 99:100
/opt/photoprism/bin/photoprism start
Storage folder "/photoprism/storage" is not writable, see https://docs.photoprism.app/getting-started/troubleshooting/docker/#file-permissions

 

Edited May 17, 20224 yr by lostinspace

14 minutes ago, lostinspace said:

 

Yes, have the same issues suddenly.  Cannot access webui at all.

 

started 220517-bookworm as root (amd64-prod)
init: updating filesystem permissions
PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates
Problems? Our Troubleshooting Checklists help you quickly diagnose and solve them:
https://docs.photoprism.app/getting-started/troubleshooting/
file umask....: "0002" (u=rwx,g=rwx,o=rx)
home directory: /photoprism
assets path...: /opt/photoprism/assets
storage path..: /photoprism/storage
config path...: default
cache path....: default
backup path...: /photoprism/storage/backups
import path...: /photoprism/import
originals path: /photoprism/originals
switching to uid 99:100
/opt/photoprism/bin/photoprism start
Storage folder "/photoprism/storage" is not writable, see https://docs.photoprism.app/getting-started/troubleshooting/docker/#file-permissions

 

unfortunately I'm not sure how to debug any further. the container takes up so much of my server's resources that I had to shut down the container to be able to do anything else! I'm not seeing any reports of similar problems on the project discussion page or their support subreddit though

@ooooooooooooo & @lostinspace I would recommend that you both open a issue on GitHub over here: Click

I cannot figure out how to use the ssh keys. It requires me to ssh login 3 times during every single task. I am using luckybackup, I created ssh keys from bash inside the docker container. I am however using a ubuntu server as my backup location and its location on the network is [email protected]:/BUD. I have tried placing ssh keys inside /BUD/.ssh/authorized_keys/ but that doesn't work. Am I required to use another unraid box? My ubuntu server is running the OS and has a ZFS pool that is mounted at /BUD. /BUD is the only part of that PC that is shared on the network. It is using samba to connect. 

 

I tried searching through this post to find any mentions of my situation, and I totally may have missed it.

 

*EDIT* I was able to fix this by using the ssh-copy-id command onto my remote server. Also noticed I created a directory named 'authorized_keys' and placed a pub key in there instead of copying the contents into the file named 'authorized_keys'. 

Edited May 18, 20224 yr by fz4Ocln7
Solved issue

11 hours ago, ooooooooooooo said:

is anyone running into issues with the latest photoprism release? the web UI is inaccessible and the container log doesn't seem to show any errors

 

 

started 220517-bookworm as root (amd64-prod)
init: updating filesystem permissions
PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates
started 220517-bookworm as root (amd64-prod)
init: updating filesystem permissions
PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates

 

I'm able to run the docker directly and it works. But if I use the app then I get same error on storage being not writable.

13 hours ago, dolomitt said:

I'm able to run the docker directly and it works. But if I use the app then I get same error on storage being not writable.

 

in my case my permissions were already correctly set and photoprism was already allowed to modify permissions. I just had to let it run for hours while it started up

started 220517-bookworm as root (amd64-prod)
init: updating filesystem permissions
PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates
Problems? Our Troubleshooting Checklists help you quickly diagnose and solve them:
https://docs.photoprism.app/getting-started/troubleshooting/
file umask....: "0002" (u=rwx,g=rwx,o=rx)
home directory: /photoprism
assets path...: /opt/photoprism/assets
storage path..: /photoprism/storage
config path...: default
cache path....: default
backup path...: /photoprism/storage/backups
import path...: /photoprism/import
originals path: /photoprism/originals
switching to uid 99:100
/opt/photoprism/bin/photoprism start
Storage folder "/photoprism/storage" is not writable, see https://docs.photoprism.app/getting-started/troubleshooting/docker/#file-permissions

Looks like its related to this issue:

https://github.com/photoprism/photoprism/issues/2334

Edited May 20, 20224 yr by lostinspace

How we can change date format in Krusader ?

example: from 12h to 24h and from mm/dd/yy to dd/mm/yy ?

16 hours ago, Masterwishx said:

How we can change date format in Krusader ?

example: from 12h to 24h and from mm/dd/yy to dd/mm/yy ?

Open up the container console and type in this:

su $USER
mkdir -p ${DATA_DIR}/.kde/share/config/kdeglobals
echo "[Locale]
Charset=iso8859-1
Country=GB
DateFormatShort=%d/%m/%Y
Language=en_GB
MonetaryThousandsSeparator=$0.$0
ThousandsSeparator=$0.$0" > ${DATA_DIR}/.kde/share/config/kdeglobals

 

Then close the console window and restart the container.

 

Hope that helps.

21 minutes ago, ich777 said:

Hope that helps.

 

Thanks , i will try i hope it will be saved after container update ,becose i have sometime some setting is lost , i think after container update maybe .... ( like editor and profil name , etc ...)

should i specify DATA_DIR  ?

 

changed to /krusader/.config for file will appear in /mnt/user/appdata/krusader/.config but nothing changed ...

7 hours ago, Masterwishx said:

changed to /krusader/.config for file will appear in /mnt/user/appdata/krusader/.config but nothing changed ...

Sorry it was already late yesterday, forgot to include this line

mkdir -p ${DATA_DIR}/.kde/share/config/kdeglobals

 

Changed the complete command above too.

47 minutes ago, ich777 said:

Changed the complete command above too

 

Sorry that i dont realised to make directory , kdeglobals should be file right ?

but after that somehow not working ...

 

2 minutes ago, Masterwishx said:

Sorry that i dont realised to make directory , kdeglobals should be file right ?

I have to look into this further, I never need to change the date nor the time...

--Ensuring UID: 99 matches user---
---Ensuring GID: 100 matches user---
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Checking configuration for noVNC---
Nothing to do, noVNC resizing set to default
Nothing to do, noVNC qaulity set to default
Nothing to do, noVNC compression set to default
---Taking ownership of data...---
---Starting...---
---Checking for 'runtime' folder---
---'runtime' folder not found, creating...---
---Checking if Runtime is installed---
---Downloading and installing Runtime---
---Something went wrong, can't download Runtime, putting server in sleep mode---

 

Anyone stuck here?

1 hour ago, Kanashii said:

Anyone stuck here?

About what container are we talking here?

Please also notice that GitHub had some issues about 2 or 3 hours ago.

I keep getting 

Error: Invalid or corrupt jarfile /jDownloader2/JDownloader.jar

If I remove the file and force a re-install of the docker, it takes ages and runs through lots of updates, but eventually just gets back to this stage again.

This is from the ich777/jdownloader2 repository

6 hours ago, DaveH said:

I keep getting 

No issue over here, installed it from scratch and pulled a fresh copy from the CA App (attached the logs).

 

6 hours ago, DaveH said:

If I remove the file and force a re-install of the docker, it takes ages and runs through lots of updates, but eventually just gets back to this stage again.

First startup took not a full minute because the container restarts itself two times to install the updates.

 

These are the steps that the container executes:

1. Pull the runtime and extract it
2. Pull the jdownloader.jar
3. Run the jdownloader.jar
4. Cycle through the initial updates

 

6 hours ago, DaveH said:

This is from the ich777/jdownloader2 repository

Are you using Unraid?

log.txt

2 hours ago, ich777 said:

No issue over here, installed it from scratch and pulled a fresh copy from the CA App (attached the logs).

 

First startup took not a full minute because the container restarts itself two times to install the updates.

 

These are the steps that the container executes:

1. Pull the runtime and extract it
2. Pull the jdownloader.jar
3. Run the jdownloader.jar
4. Cycle through the initial updates

 

Are you using Unraid?

log.txt 4.81 MB · 0 downloads

 

Sorry, I hadn't realised you supported other platforms, yes, I am running Unraid.

In the end, I removed the jdownloader2 folder in appdata, just in case there was something in there causing it to act strange, removed the container entirely and started from scratch, and it's working!

I've backed up the folder before I removed it, but there's so many configs in there, I wouldn't know where to begin looking through to see what caused it!

Appreciate the reply though, thank you

5 minutes ago, DaveH said:

I've backed up the folder before I removed it, but there's so many configs in there, I wouldn't know where to begin looking through to see what caused it!

If anything breaks again take a look at this: Click

 

Or what I would recommend:

1. Stop the container
2. Delete the files "Core.jar" & "JDownloader.jar" and the folders "tmp" & "update" from your jdownloader2 directory
3. Start the container again

Jdownloader gibes me the following Error after unraid-update. Any Suggestions?

 

Edit: saw the posting above, will try this.

Edited May 30, 20224 yr by Cicatrix