bastl

@Nodiaque As workaround for testing Win11 you can use the following on 6.9.2:

I guess most of you who tried to test the final Windows 11 build might allready noticed, the installer checks for the presence of a TPM module and enabled SecureBoot. If one of them is not present, the installer will halt with the following error directly after the edition selection With shift+F10 open a commandline Enter "regedit" into the cmd and press enter. The registry editor should open up. Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\Setup" create a new key called "LabConfig" on the left side bei right clicking on "Setup" and select new > key ad the following 3 DWORD (32-Bit) entries inside LabConfig on the right. BypassTPMCheck BypassSecureBootCheck BypassRAMCheck Double click each entry and change the hex entry from 0 to 1 After that close the registry editor and the commandline and go one step back to the edition selection screen, select the version you wanna install, press next et voila, Windows 11 should install fine. Doing all this straight after the installer has started on the language selection menue also works. No need to go to the edition selection first. For this to work I used the default Win10 template with a 70G vdisk 4G RAM and 8cores. Nothing else on the template or in the xml has changed. Keep in mind this is only a solution if you want to try the new Windows version. No one at this point can guarantee how long this will work and if a future update will break something. We all know MS is randomly "breaking" things with every update. Some reports say updates might not even possible with this reg tweak in the future, therefore my warning for all those can't await the next Unraid version which propably will come with a fix and an emulated TPM module. only use this for testing Windows 11! Happy testing folks

@Falcosc Verify on disk 1 is finished. The file integrity control panel page still shows the the files from disk2 like in the screenshot of my fist post. I have a lot of *.tmp.end files in /var/tmp and a disk2.tmp.end. Some are from august some from today. I renamed the disk2.tmp.end refreshed the page and disk2 export showed "canceled with error". Refreshed the page again. Error is gone. Started a new export of disk2. No errors. I'am kinda confused right now.

@Falcosc Maybe it helps to note that I am from germany and some of the files include the german letters Ää Öö Üü and ß for example */mnt/disk2/company/tmp/Präsentation/industrie-medium.png also I have a folder where backups from my android phone are placed, some with the following naming included with an @ for example */mnt/disk2/nextcloud/user/files_versions/.SeedVaultAndroidBackup/1678426041580/kv/@pm@/Y2ibnQudnVXN1cn9tLZleQ.v1614280421

@Falcosc I have no /tmp/disk2* files in that folder and I can't really share the /var/tmp/disk2* filelist with you. I have a lot of personal and work content on that disk, some named with my real name or the name of the company I work for. I can try to remove the personal stuff if it helps. I guess not. On the main tab I only see reads happen on disk one where the verify process is still active. Looks like export for disk2 is already finished. Timestamp for disk2 is short after the time a started the process for a new export.

Short report for something weird happened to me. Planned verify task for 2 disks started this morning, 1 disk finished and reported a corruption on disk 2. Verify task on disk 1 still running. The coruppted file in my case was the nextcloud.log file getting flooded. I cleared the logfile, verify on disk 1 still running. I selected disk 2 and started a export task and the following happened in the ui The ui shows as it looks like the full list of files beeing scanned on disk 1. Refreshing the page doesn't help. The counter for processed files is still counting up and constant read speeds on disk 1 showing that the process looks like it's still working. Only the page is messed up.

@bonienl 2021.08.24b fixed it. Thanks!

@bonienl 24a gives me the same error

There is another update showing for me right now. current version: 2021.08.23a new version: 2021.08.24 pressing the update button gives me the following error.

I bet you had that feature already in the app why should it ask for permissions like USE_BIOMETRIC and USE_FINGERPRINT 😂

@jbrodriguez I checked a couple other apps for backing up APKs and I found one which backed up all split APKs from that new format and on my main phone V5.0.6 is running now. Thanks for the hint with the new split file format 😘 What's with my feature request? Are you already on it? Just kidding 😂 Would be nice if in the future the app start can be protected by a passcode or via finger print.

So if I understand the new format correctly, as a developer delivering new updates is easier and smaller now. You kinda update only parts of the app. But on the enduser device your app still exists as an APK, right? I grabbed that APK and sideloaded it on my main phone and the install went fine. This doesn't explain, why the app won't launch. Did the app permissions changed compared to version 4? Is there a way to force the app to start in a debug mode so I can get some logs for you? Or do you have a test build for me with debug enabled? i'am kinda relativly sure that feature existed. If not, see it as a feature request 😄

@jbrodriguez I have another problem with the Android version of the app starting with v5. I Tried 5.0.2, 5.0.4 and yesterday v5.0.6. and none are even starting on my phone. Version 4.17 is still working fine, but let me explain a bit more that might help. My phone is a Pixel5 with the custom AOSP based ROM CalyxOS installed with MicroG services to gain some of the google features like push notifications and access to google services. I don't use any Google accounts on that phone and have no access to the play store directly on this phone. The account I baught your app with is still active and I have to use it on a temporary phone to download app updates for paid apps like yours, back them up and install the apk on my Pixel. This procedure worked flawless for me until v5. The temporary phone is an old Galaxy S3 and is only used for this and is off if I don't need an update. Paid Apps can't be updated with the build in F-Droid or Aurora store under CalyxOS and I'am fine with that. I only have 2 paid apps anyways. App version 4.17 installs fine and works without issues. App version 5 was the first one I coudn't use. Clearing cache of the old version, uninstall it, install newest version, so fine so good. As soon as I try to start your app, nothing happens. No error message, nothing. Is there a way I can help to diagnos the issues and make that app work again? I know I'am a special case, but it would be nice to have an up to date version of your app working again on my privacy friendly phone where everything is working except of your really helpful app, and btw. in which version did you removed the password/fingerprint lock option inside the app? This was a feature I requested some time ago and you implemented it back than 😔

First of all, don't use all available cores for your VM and especially not the core 0 and it's HT. Unraid always uses these core for itself to manage stuff in the background. Second thing, you have 2x 6core Xeons in your system, try it first to ONLY use the cores from a single CPU. 1-5 + HT or 6-11 + HT or even less and don't mix the cores from the different CPUs.

Is nen Fehler, der nix mit dem Certbot selbst zu tun hat. Da haben die Jungs und Mädels, die SWAG bereitstellen nen Fehler drin gehabt. Bei mir wurde ne yt-downloader.conf bemängelt, die ich selbst nie erstellt oder den dazugehörigen Docker verwendet hab. Auskommentieren, Umbenennen oder löschen der Datei schafft abhilfe. Neustart oder Update des Containers generiert die Vorlagen eh neu. Wer bei der automatischen Erneuerung der Certs mit certbot Probleme haben sollte, sollte auch mal schauen, ob in der Firewall/Router (bei mir Pfsense) nen Geoblocking aktiv ist. Wenn ja, wie bei mir mit aktivem pfBlockerNG GeoIP Filer, dann diesen kurz abschalten und den Container neustarten.