Black screen on vnc and Web gui - unraid

[kosielemmer]

Tried this but after successful install I only get a black screen. Are there some prereqs I might be missing?

Trying it on unraid using the community app

[johntdyer]

Appears it not actually blank, its just sized incorrectly.. After getting the username in and pressing enter I got a further but still cant see the password field or the next button

[revilo951]

I'm getting the same issue on unraid. It was running fine, but after a recent update (a couple of months now I think). It's black, and nothing I do makes any difference.

[Lesani]

I also have a completely black screen, no input in therms of mouse or keyboard lead to anything showing in vnc or webui.

have tried different resolutions, different browsers, and realvnc. on the VERY FIRST install it showed something, but my usb drive was defective. After I set everything up anew with a brand new usb drive, I installed this docker again, and only get black. I am still on unraid trial (very fresh) but unfortunately already created a backblaze account, so that trial is running... any idea how to fix this? I have removed the container multiple times already, and reinstalled...

[Galacticminingoperation]

I'm also having this issue with Unraid. I looked at the logs and nothing stands out: no errors or anything.

[skaza2125]

Experiencing the same issue on unraid, I changed the display res to 1280 x 720 an various other resolutions but am always greeted by a black screen. Any Update on this?

[jensenkd]

I'm having the same issue. Anyone find a workaround? Same black screen using web interface and a VNC client.

[jam3sn]

It seems like going back to v1.2 works.

[johntdyer]

@JonathanTreffler Any thoughts on why we need to pin on 1.2? Thanks

[JonathanTreffler]

Considering the original comment was made when 1.2 was the newest version I think either the 1.3 and 1.4 versions are not the actual issue or the people in this thread have different issues that cause the same blank screen issue.

Generally the only big differences between the versions are the wine versions and the versions of other dependencies.

[JonathanTreffler]

Please posts logs, even if you see no error. Errors often do not occur to the end of the log, but in the middle, since backblaze gets started pretty early in the docker startup.

[whiterussiansp]

I tried pinning to 1.2, didn't work. Saw a note in the logs about the width needing to be divisible by 4. Adjusted the width to be divisible by 4 and VNC returned. Not sure if 1.2 and the width adjustment were needed as I did not backtest without the 1.2.

Edit: ended up with other issues, removed the v1.2 and left the width setting and was able to complete setup.

[gongfunaicha]

I had the same issue on unraid and was able to resolve by following sgu222e's suggestion here. I'm assuming it has to do with me not cleaning up the appdata after previous incorrect installs.

I was experiencing the same issue on Unraid. stopped the container deleted the config directory (/mnt/user/appdata/backblaze_personal_backup/) restarted the container and it worked.

[amphyvi]

Appears it not actually blank, its just sized incorrectly.. After getting the username in and pressing enter I got a further but still cant see the password field or the next button

Getting the same issue. Log says:

xdg-open: no method available for opening 'https://accounts.google.com/o/oauth2/auth?response_type=code&prompt= ... &state=3908&redirect_uri=http://localhost:63631'

Removed most of the URL to protect my privacy, I can provide the rest of it to the dev if needed. I'm using the Backblaze_Personal_Backup app installed via Unraid.

[amphyvi]

Update: I was able to fix it by doing the following: Go to Backblaze and log in, then under Account, choose My Settings. Change the "Sign In to Backblaze Using:" option to My Email.

[johnnyfleet]

I had the same issue and the suggestion by @amphyvi worked for me. I already have an account set up to back up another machine. It turns out that I must have linked to Google signing/Oauth at some point.

Changing the "Sign In to Backblaze Using:" from Backblaze login > My Settings worked.

[henryyeh]

I had the same issue and the suggestion by @amphyvi worked for me. I already have an account set up to back up another machine. It turns out that I must have linked to Google signing/Oauth at some point.

Changing the "Sign In to Backblaze Using:" from Backblaze login > My Settings worked.

I had the same issue. This wine installation doesn't have a browser, so you can't auth through Google. Turning that off makes it work perfectly.