installer not coming up

[14paavang]

When I get onto the web interface, i'm met with this screen and the installer doesn't boot up

also it did boot up once, but the password filed was missing after the email part, which I currently can not replicate.

[14paavang]

i got v1.5 to work, however, the drive isnt showing up, the software sees drive c, and z for some reason but not d or anything else i map to it

[traktuner]

hey,
please try to use the tag ubuntu22 instead of latest.
Also the mount screenshot is cut off - for the drive_g mount "read only" is not checked, right?

[14paavang]

hey, please try to use the tag ubuntu22 instead of latest. Also the mount screenshot is cut off - for the drive_g mount "read only" is not checked, right?

not checked, i'll try ubuntu22

[14paavang]

@traktuner
I tried a fresh container with ubuntu 22 and it is only a black screen when logging into the web interface, despite giving it root access and every permission.

The other container I have running where I initially installed 1.5 and then upgraded to latest is still working, however, i was backing up my laptop the server in a way that created an image file, but it stopped backing it up after only 2gigabytes of the 120 gigabyte file was backed up. Could this be a result of sending the file over to the server using samba and backing it up at the same time?

[traktuner]

Hey,
the folder "dosdevices" should be empty, at least it has content only visible from within the linux container.
The installer files should be in your config/wine/drive_c directory - could you please check the permissions on that folder?
If you have 2 containers, one running one not working, they also must not point to the same "config" directory.
Please check again and always post the docker logs and startup.log file so we can debug further. Without the logs we are "blind".
Thank you!

[14paavang]

Hey, the folder "dosdevices" should be empty, at least it has content only visible from within the linux container. The installer files should be in your config/wine/drive_c directory - could you please check the permissions on that folder? If you have 2 containers, one running one not working, they also must not point to the same "config" directory. Please check again and always post the docker logs and startup.log file so we can debug further. Without the logs we are "blind". Thank you!

I purposely mounted a different directory for the ubuntu 22 image config. The only way I could get the latest image to work was by first installing v1.5 and then pointing the latest one to the same config directory. Due to this observation, I reasoned that the latest image wasn't doing something right when setting up the files in its config directory, so I decided to give the ubuntu 22 container a seperate folder mounted as config to see if I was right, and it does seem to be the case. Keep in mind that I explicitly passed the root Id to both containers during creation and I made sure that the ACL on both directories was the same and gave the container full control over everything, explicitly stating so by adding every user and group to it and setting their permissions to full control.

The startapp.log from the ubuntu 22 image is :
backblaze-wine-startapp.log
these logs are from the path you said
backblaze-wine-startapp.log
These logs are from within the dosdevices folder ( idk why there are 2 copies of it, but I put them both here just in case)

Here are the container logs from the ubuntu22 image:
backblaze_backblaze-ix-chart-75bb79b876-s6rnj_ix-chart.log

Also the issue I was facing earlier where backblaze wasn't backing up the entire file went away, there seems to be a detection interval or something where the software refuses to back up files it has already backed up, unless they have changed by a significant amount, especially when the file is very large.

Also the dosdevices folder is definitely not empty, it has never been so on any of the containers I have installed ( atleast when viewed from the side of the server (i.e after sharing the entire config directory over samba as Truenas doesn't directly let you view the files stored on it))

this is what is inside the folder. ( this is where I saw the second copy of the startapp logs)