Bobat

Awesome, got this working now. Great plugin, thanks!

What's the correct identifier to use Backblaze as a S3 provider? I've tried all of the combinations of "provider=Backblaze" I can think of and I keep getting NOTICE: s3: s3 provider "Backblaze" not known - please set correctly

I was still on the community apps version, I somehow missed the post about the manual install. Changed to the manual install and all is good. Thanks!

Yeah, I'm seeing the same thing. I added a new docker and wanted to add it to an existing folder, but I'm getting the blank screen when I click on the folder name. I'm not sure when this started, maybe 7.0.1? It's been a while since I needed to edit my folders, but I'm pretty sure I've done it since 7.0.0.

Sort of. My OPNsense router was also plugged into the same monitor, so I think after 15 minutes of inactivity the monitor was automatically switching over to the other input and the messages would start up again. I unplugged the other cable and it seems to be stable now. I rarely need a monitor plugged into either machine, so maybe I'll try one of those HDMI dummy plugs rather than keeping the monitor on all of the time.

I did have a monitor plugged in via an HDMI KVM. I plugged the monitor directly into the server and it seems to have stopped. Thanks! EDIT: I spoke too soon, it stopped for about 15 minutes and then started doing it again.

I'm getting the "EDID block 0 is all zeroes" error filling up my log on 6.11.0 final. I saw this on 6.11rc4 as well (never tried rc5). Rolling back to rc3 makes it go away. I saw this thread suggesting that blacklisting the GPU driver may fix it, but I use the integrated GPU for Plex transcoding so I don't think that's a viable solution for me. Any other ideas? burns-diagnostics-20220923-1425.zip

The US servers don't look like they support port forwarding. For the servers that do, it looks like you're limited to a single port. I don't use the function personally, so I'm not 100% sure on that.

If you're using PIA, make sure you're using the most up to date ovpn config files from the PIA site. They just recently retired a bunch of legacy servers. My config file was pointing to one of those old servers and I couldn't figure out why it wouldn't connect anymore. Download the default Nextgen config files and make sure you're using the current server names.

From your syslog: Several people (including myself) are having the same issue. See here, here, and here. I've downgraded back to 6.4.1 and everything's good for me now. I'll try again after the next release to see if a new kernel patch solves it.

I was having the same issue post upgrade. Here's what I did to restore connectivity to Crashplan Central: [*]Stop the Crashplan docker [*]Backup your my.service.xml file in your Crashplan docker config folder - mine was in /mnt/cache/appdata/crashplan/conf/ [*]Edit my.service.xml and remove the hash string between the <autoLoginPasswordHash> tags [*]Change the text between the <autoLogin> tag from "true" to "false" [*]Start the Crashplan docker [*]Launch the GUI client (either through Windows or the MATE, whichever you use) and sign in to your Crashplan account when prompted then close the client [*]Stop the Crahsplan docker [*]Edit my.service.xml and change the text between the <autoLogin> tag back to "true" [*]Start the Crashplan docker again Confirm through the GUI client that everything connected and your backups are working again. I don't know if toggling the autoLogin part is strictly necessary, you may only need to remove your old password hash, but this worked for me.

I can confirm that the server is up and running on my beta12 box. Thanks for the quick turnaround!

Does this plugin need to be updated for beta12? I just tried installing the 64 bit server and the config page comes up blank. Not sure if it's my issue or the plugins. I installed from the web GUI and didn't see any errors.