TwistedCarnivore

I upgraded to 7.3,0 and did the onboard for boot. After doing this i discovered a problem with the ssd the pool is on. Is there a way to move the onboard boot to another pool? Figured I better ask before I do a major league screw up.

Unraid 7.1.4 CA 2025.07.18 Search box is missing CA-Logging-20250718-1647.zip

Unraid 7.1.4 CA 2025.07.15 Works fine, no display problems. CA-Logging-20250717-1101.zip

7.1.4 Saw the same as snidera but it works. No display issues. Thanks for you work here. Willing to test whatever you need.

DNS servers are static IPv4 DNS server 1: 208.67.222.222 IPv4 DNS server 2: 208.67.220.220 IPv4 DNS server 3: 68.94.157.1 When I said rather quickly, I was referring to access those files via a web browser. https://assets.ca.unraid.net/feed/applicationFeed-lastUpdated.json https://raw.githubusercontent.com/Squidly271/AppFeed/master/applicationFeed.json I have since upgraded Unraid to 7.1.4 with the same result, CA 2025.01.12 works CA 2025.06.04a app feed fails Bypassing the pfsense box would be a last resort, my modem is in passthru so I would have to reconfigure the modem to allow me to bypass the pfsense box. CA-Logging-20250708-1222.zip snafu-diagnostics-20250708-1227.zip

I have come to the conclusion that there is something wrong with CA 2025.06.04a. Reset the router, no change. Upgraded pfsense, no change. Swapped to second ethernet port, swapped ethernet cable, swapped to a different port on the switch. None those made any change. Switch is non managed consumer model, so nothing exotic going on there. All of the above was done with docker turned off and vm manager turned off. I can download the files in a web browser and they come down rather quickly, couple of seconds. After more flash backups and restores that I care to think about, this is what I found. Went back to known working backup and started over. Unraid 6.12.14 CA 2025.01.12 works CA 2025.06.04a app feed fails Unraid 7..0.0 CA 2025.01.12 works CA 2025.06.04a app feed fails . Unraid 7.1.2 CA 2025.01.12 works CA 2025.06.04a app feed fails New install 7.1.12 with trial license CA 2025.06.04a app feed fails Anything else I need to try let me know. I have a working system now with the older CA plugin, pretty happy for now.

Reset the router, no change. Upgraded pfsense, no change. Swapped to second ethernet port, swapped ethernet cable, swapped to a different port on the switch. None those made any change. Switch is non managed consumer model, so nothing exotic going on there. All of the above was done with docker turned off and vm manager turned off. I can download the files in a web browser and they come down rather quickly, couple of seconds like you said. Anything else I should try?

I had a flash drive fail. After creating a new drive from a backup, transferring the license key, and updating the key for the new drive I realized I needed to upgrade Unraid. After upgrading unraid, the apps tab quit working, "downloading of appfeed failed". I have checked DNS settings, time settings, and anything else I could find tin this thread https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/?tab=comments#comment-1101084 , still no app feed. I have removed and reinstalled the community applications plugin as well, still no joy. Plugins can be updated from the plugins tab and docker containers can be updated from the docker tab. AWS, Docker hub and github are all reachable. snafu-diagnostics-20250615-2128.zip CA-Logging-20250615-2131.zip

I had a flash drive fail. After creating a new drive from a backup, transferring the license key, and updating the key for the new drive I realized I needed to upgrade Unraid. After upgrading unraid, the apps tab quit working, "downloading of appfeed failed". I have checked DNS settings, time settings, and anything else I could find in this thread https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/?tab=comments#comment-1101084 , still no app feed. I have removed and reinstalled the community applications plugin as well, still no joy. Plugins can be updated from the plugins tab and docker containers can be updated from the docker tab. AWS, Docker hub and github are all reachable. Any help would be appreciated. CA-Logging-20250615-2131.zip snafu-diagnostics-20250615-2128.zip

I upgraded with unbalanced still installed. No problems after restart.

I was getting ready to upgrade to 6.12.11 and ran the update assistant. Not quite sure of what to make of the output from the script. Disclaimer: This script is NOT definitive. There may be other issues with your server that will affect compatibility. Current unRaid Version: 6.12.10 Upgrade unRaid Version: 6.12.10 NOTE: You are currently running the latest version of unRaid. Checking for plugin updates OK: All plugins up to date Checking for plugin compatibility Issue Found: unbalanced.plg is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues. OK: All plugins are compatible

Forced upgrade fixed the problem. Thanks for your work in fixing this.

All good after forced update. Thanks for the quick response.

Having the same problem with binhex-delugevpn, so whatever changed in common between them is probably causing the problem. Rolled both back to previous versions and the problem went away.

Upgraded a little while ago and having similar problem as Lonewolf147 I created a new pia config file to ensure nothing was screwed up there. sh-5.2# iptables -S -P INPUT DROP -P FORWARD DROP -P OUTPUT DROP -A INPUT -p udp -m udp --sport 53 -j ACCEPT -A INPUT -p tcp -m tcp --sport 53 -j ACCEPT -A OUTPUT -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -p tcp -m tcp --dport 53 -j ACCEPT Command execution.txt supervisord.log.txt

unbalanced installs and runs fine after the upgrade. fix common problems does not show any issues after installing unbalanced. upgrade assistant still shows and error with unbalanced after the upgrade. Must be something in the upgrade assistant causing it to report that problem. Disclaimer: This script is NOT definitive. There may be other issues with your server that will affect compatibility. Current unRaid Version: 6.12.8 Upgrade unRaid Version: 6.12.8 NOTE: You are currently running the latest version of unRaid. Checking for plugin updates OK: All plugins up to date Checking for plugin compatibility Issue Found: unbalanced.plg is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues. OK: All plugins are compatible Checking for extra parameters on emhttp OK: emhttp command in /boot/config/go contains no extra parameters Checking for disabled disks OK: No disks are disabled Checking installed RAM OK: You have 4+ Gig of memory Checking flash drive OK: Flash drive is read/write Checking for valid NETBIOS name OK: NETBIOS server name is compliant. Checking for ancient version of dynamix.plg OK: Dynamix plugin not found Checking for VM MediaDir / DomainDir set to be /mnt OK: VM domain directory and ISO directory not set to be /mnt Checking for mover logging enabled OK: Mover logging not enabled Checking for reserved name being used as a user share OK: No user shares using reserved names were found Checking for extra.cfg OK: /boot/config/extra.cfg does not exist Issues have been found with your server that may hinder the OS upgrade. You should rectify those problems before upgrading

I ran the update assistant twice a little while ago and got the same results. Removed the plugin and update assistant ran clean. Updating unraid now and will try and add unbalanced when it finishes.

Getting ready to upgrade unraid from 6.12.6 to 6.12.8. I ran the update assistant and got this error concerning unbalanced Issue Found: unbalanced.plg is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues. Is this going to cause problems on the upgrade?

Did that again. It shows upgrading in the log when the container starts, but still showing same 10 extra files in integrity check. I did run all the occ commands that he showed in the discord post, and that didn't help either. Guess I just have a persistent poltergeist. Probably just wait for the next version to roll out and see what happens then . using keys found in /config/keys Initializing nextcloud 27.0.0.8 (this can take a while) ... Upgrading nextcloud from 27.0.0.8 ... Setting permissions Nextcloud is already latest version Initializing finished

No joy. root@snafu:~# docker exec -it nextcloud occ integrity:check-core - EXTRA_FILE: - core/js/tests/specs/appsSpec.js: - expected: - current: cf1ff76b5129943a1ffd6ea068ce6e8bc277718b9d0c81dccce47d723e1f290be20f197b6543f17f3b2ac78d8d4986354db4103de2b5e31c76e00e248984605b - core/l10n/et_EE.js: - expected: - current: 55e09a16c917b20c1bba2d5458aab6d4eb4c9a80a0480c7ca309db67a522c83682264d12fcfe6eb54d4120d04b4b90249a03d268b3adf2e7046db8a6229ce586 - core/l10n/et_EE.json: - expected: - current: 675629231727e9b6bc16463489466626476ae9571c5179c78c881e599e3ea991cec4dd9931c3c53bd731f8e0c57312fd31c6503a0b633a579c6bc9a71b5ecb3e - dist/files_trashbin-files_trashbin.js: - expected: - current: 24e537aff151f18ae18af31152bcfd7de9c96f0f6fdcca4c1ad975ece80bb35a2ab7d51c257af6a9762728d7688c9ba37a5359a950eb1e9f401d4b9d875d92b2 - dist/files_trashbin-files_trashbin.js.LICENSE.txt: - expected: - current: 2e40e4786aa1f3a96022164e12a5868e0c6a482e89b3642e1d5eea6502725061e2077786c6cd118905e499b56b2fc58e4efc34d6810ff96a56c54bf990790975 - dist/files_trashbin-files_trashbin.js.map: - expected: - current: 65c2a7ddc654364d8884aaee8af4e506da87e54ae82f011989d6b96a625b0dbfba14be6d6af545fa074a23ccf2cc29043a411dc3ac1f80a24955c8a9faa28754 - lib/private/Files/ObjectStore/NoopScanner.php: - expected: - current: 62d6c5360faf2c7fca90eaafa0e92f85502794a42a5993e2fe032c58b4089947773e588ad80250def78f268499e0e1d9b6b05bc8237cc946469cd6f1fb0b590c - lib/private/Updater/ChangesResult.php: - expected: - current: d2e964099dfd4c6d49ae8fc2c6cbc7d230d4f5c19f80804d5d28df5d5c65786a37ea6f554deacecad679d39dbba0d6bd6e4edadca292238f45f18f080277dad0 - lib/public/WorkflowEngine/IEntityCompat.php: - expected: - current: ea1856748e5fcf8a901597871f1708bdf28db69d6fa8771c70f38212f028b2ff744b04019230721c64b484675982d495a2c96d1175453130b4563c6a61942213 - lib/public/WorkflowEngine/IOperationCompat.php: - expected: - current: 6c09c15e9d855343cc33a682b95a827546fa56c20cc6a249774f7b11f75486159ebfe740ffcba2c9fa9342ab115e7bf99b8c25f71bb490c5d844da251b9751ed Restarted nextcloud and rescanned, still show the extra files.

Ran the command and restarted the container. Still showing the extra files. Would manually deleting the files hurt anything?

docker exec -it nextcloud occ db:add-missing-indices Worked this morning.

Checked for updates, and none showing. Technical information ===================== The following list covers which files have failed the integrity check. Please read the previous linked documentation to learn more about the errors and how to fix them. Results ======= - core - EXTRA_FILE - core/js/tests/specs/appsSpec.js - core/l10n/et_EE.js - core/l10n/et_EE.json - dist/files_trashbin-files_trashbin.js - dist/files_trashbin-files_trashbin.js.LICENSE.txt - dist/files_trashbin-files_trashbin.js.map - lib/private/Files/ObjectStore/NoopScanner.php - lib/private/Updater/ChangesResult.php - lib/public/WorkflowEngine/IEntityCompat.php - lib/public/WorkflowEngine/IOperationCompat.php Raw output ========== Array ( [core] => Array ( [EXTRA_FILE] => Array ( [core/js/tests/specs/appsSpec.js] => Array ( [expected] => [current] => cf1ff76b5129943a1ffd6ea068ce6e8bc277718b9d0c81dccce47d723e1f290be20f197b6543f17f3b2ac78d8d4986354db4103de2b5e31c76e00e248984605b ) [core/l10n/et_EE.js] => Array ( [expected] => [current] => 55e09a16c917b20c1bba2d5458aab6d4eb4c9a80a0480c7ca309db67a522c83682264d12fcfe6eb54d4120d04b4b90249a03d268b3adf2e7046db8a6229ce586 ) [core/l10n/et_EE.json] => Array ( [expected] => [current] => 675629231727e9b6bc16463489466626476ae9571c5179c78c881e599e3ea991cec4dd9931c3c53bd731f8e0c57312fd31c6503a0b633a579c6bc9a71b5ecb3e ) [dist/files_trashbin-files_trashbin.js] => Array ( [expected] => [current] => 24e537aff151f18ae18af31152bcfd7de9c96f0f6fdcca4c1ad975ece80bb35a2ab7d51c257af6a9762728d7688c9ba37a5359a950eb1e9f401d4b9d875d92b2 ) [dist/files_trashbin-files_trashbin.js.LICENSE.txt] => Array ( [expected] => [current] => 2e40e4786aa1f3a96022164e12a5868e0c6a482e89b3642e1d5eea6502725061e2077786c6cd118905e499b56b2fc58e4efc34d6810ff96a56c54bf990790975 ) [dist/files_trashbin-files_trashbin.js.map] => Array ( [expected] => [current] => 65c2a7ddc654364d8884aaee8af4e506da87e54ae82f011989d6b96a625b0dbfba14be6d6af545fa074a23ccf2cc29043a411dc3ac1f80a24955c8a9faa28754 ) [lib/private/Files/ObjectStore/NoopScanner.php] => Array ( [expected] => [current] => 62d6c5360faf2c7fca90eaafa0e92f85502794a42a5993e2fe032c58b4089947773e588ad80250def78f268499e0e1d9b6b05bc8237cc946469cd6f1fb0b590c ) [lib/private/Updater/ChangesResult.php] => Array ( [expected] => [current] => d2e964099dfd4c6d49ae8fc2c6cbc7d230d4f5c19f80804d5d28df5d5c65786a37ea6f554deacecad679d39dbba0d6bd6e4edadca292238f45f18f080277dad0 ) [lib/public/WorkflowEngine/IEntityCompat.php] => Array ( [expected] => [current] => ea1856748e5fcf8a901597871f1708bdf28db69d6fa8771c70f38212f028b2ff744b04019230721c64b484675982d495a2c96d1175453130b4563c6a61942213 ) [lib/public/WorkflowEngine/IOperationCompat.php] => Array ( [expected] => [current] => 6c09c15e9d855343cc33a682b95a827546fa56c20cc6a249774f7b11f75486159ebfe740ffcba2c9fa9342ab115e7bf99b8c25f71bb490c5d844da251b9751ed ) ) ) ) Screen shot of nextcloud admin page https://prnt.sc/-NXFxBW_Bk0u error.log nextcloud.log ngnix error.log snafu.tarfu.xyz-diagnostics-20230705-1339.zip

Installed the upgrade last night, not showing any upgrades available, restarted and still showing the extra files. Not too worried about it, will check again when the next upgrade comes out.

It did upgrade and runs fine. Security check shows code integrity issue. Technical information ===================== The following list covers which files have failed the integrity check. Please read the previous linked documentation to learn more about the errors and how to fix them. Results ======= - core - EXTRA_FILE - core/js/tests/specs/appsSpec.js - core/l10n/et_EE.js - core/l10n/et_EE.json - dist/files_trashbin-files_trashbin.js - dist/files_trashbin-files_trashbin.js.LICENSE.txt - dist/files_trashbin-files_trashbin.js.map - lib/private/Files/ObjectStore/NoopScanner.php - lib/private/Updater/ChangesResult.php - lib/public/WorkflowEngine/IEntityCompat.php - lib/public/WorkflowEngine/IOperationCompat.php Looks like files that don't need to be there any more.