RichJacot

Ouch! Thank you! I'll skim through the first pages to get an idea but I may just redo everything. It's not a huge setup. Thanks again!

Hello, I'm still running on lscr.io/linuxserver/unifi-controller:7.4.156 on by backup unraid server. I installed 11notes/unifi:10-unraid on my primary unraid server. I'm moving my backup unraid server to another home that I have unifi in and need a controller there. I took a backup and shutdown the unifi 7.4 docker on the backup server, installed the new unifi reborn on the primary server, restored the backup, waited and restarted the docker. I had to change the container port from 8080 to 8081, 8080 was already in use by another docker. I ssh'd to my switches and APs and used the set-inform http://<controller-ip>:8081/inform on each. They 'seemed' to adopt after doing the set-infrom. However after a short while, everything went offline. I couldn't get to anything, even on the same vlan. I couldn't ping anything even when I set my desktop to a static IP (same vlan). I had to factory reset the switch both the primary, backup, and desktop were plugged into. After which I shutdown the unifi reborn docker, started the old 7.4 controller. I then went around and factory reset my other devices. They adopted into the old 7.4 and all is well again and has been for a few hours. I'm assuming it's stable. What did I do wrong or what is the best approach to what I'm trying to do? Or a better suggestion(s)?

The way you suggested, Thank you for posting BTW, looked like the long way around so I kept look for a shorter path. ;-) I found "https://github.com/uglymagoo/plex-claim-server" in my hunt. I used this and it worked for me. I followed the minimal instructions posted and it worked in my case. I'd like to know why a simple password change causes so much work! Hopefully I'll remember this when it comes up again. Thanks ohmaxx

I just did the reset and I'm getting the same as you now. Have you found a solution yet? I don't have the claim variable like you do though. Either way, I'll keep digging and report back if I find something.

No, just binhex-sabnzbd. It's been working right along now. 'shrug'

I've been watching this thread because I started having issue as well (just about the same time). Pretty much match what you're saying above. A couple days ago, I blew it away and reinstalled, and didn't restore anything for back up either. knock on wood.....it's been running fine since, on the latest.

Hello, I'm unsure the order of the steps, maybe even all of the steps involved, to get all my dockers over to spinners before recreating my cache to ZFS. I'd like to use snapshot instead of Backup/Restore Appdata for backups. My Docker settings Default appdata storage location is: /mnt/cache_nvme/appdata/ I have/had plenty of cache_nvme space and wanted the performance of nvme over spinner for some of my dockers. Now if that was where all of my dockers were, it probably wouldn't be an issue and I could follow one of spaceinvader's videos to move everything. The problem is, less important or dockers I didn't feel needed the performance gains being on nvme, I specified in their config to use /mnt/user/appdata/. Does anyone know the best order to get my mess cleaned up? Should I go through all my contains first and change everything that has /mnt/cache_nvme/appdata to /mnt/user/appdata/? Actually, should I just go through EVERY container and everywhere there is /mnt/cache_nvme/*, change it to /mnt/user/* ? Will changing this location in all of the configs automatically move everything from cache to spinners for said container? Then (2nd) shutdown docker, manually mv everything in /mnt/cache_nvme/ to /mnt/user/ ? Then (3rd) change the docker settings Default appdata storage location is: to /mnt/user/appdata/ , then (4th) change all of the shares that use nvme to Array. Start docker back up with my fingers crossed? Once I have everything on spinners and nothing hitting nvme, I can destroy it and recreate with zfs. After which I "think" I should just change the shares to cache_nvme <-- Array. Obviously I'd take a backup with Backup/Restore Appdata before doing any of the above. Not sure I'd know how to get back if I mucked up the above but at least I'd have a backup. cube-diagnostics-20250507.-0857.zip

I figured out what the three are and that I don't need them. I just removed the three pools and was able to start the array. Not a fix, but it got me up and running. Thanks

Hello, I just upgraded to 7.0 stable and I'm getting something similar. Unless the nvme1tb is part of Cache_nvme, I can lose/drop these three problems. The nmve1tb 'might' be and old 1tb nmve I attached at one time in the past. Any ideas? Thanks! cube-diagnostics-20250110-0746.zip

Mine just started working out of the blue, no changes on my end.

Any headway on this matter? I'm started having the issue this morning with a couple dockers. I decided to try to use "Check For Updates" at the bottom of the docker screen. Now ALL of my dockers are saying "not available". 😞 Following...

Well... Somehow the system changed/thinks the IDs are different than they were. I plugged the drive labeled 47CL back in and unplugged the drive labeled 18CT and it thinks it's 18CT in the main array screen. I selected it and selected the new drive from the dropdown to replace the failed drive 6. It's currently rebuilding from parity. A know for a fact I did NOT peel and move stickers. I have no idea how it got confused.

I tried a different connector on the replacement drive and now it thinks the parity drive is one that is no longer in the system. I put stickers on all of the drives when they were installed and booted so I could see the IDs the system assigned, with the last four of their IDs, and 18CT is plugged in. Now even when I unplug the replacement drive it's showing the parity drive as 47CL, which is sitting next to me. I'm at a loss....

I had a drive fail in the array. I had a spare so I'm thinking I'll just shut the array down and swap the drive out. BUT whenever I plug a drive in, the same connections as the failed one, and boot the system up, that parity drive drops off/goes missing. I unplug the one I used as a replacement and boot back up and the parity drive is back like normal. I thought there was an issue maybe with the replacement I was using so I ordered another drive, pre zero'd it and it's doing the same thing. Plug the new drive in, boot up, parity disappears. Does anyone have any ideas or suggestions? TIA

Following to see what the solutions ends up being. I've used this for over a year now and it's worked fine. I give it a look every few months and it HAD been working fine. I've removed and reinstalled, change the /config some have mentioned and tried the BR0... still no go. Very frustrating to say the least.

Thank you. I'll update this evening.

The work around, mentioned in a link above, I don't think helps me. I'm not allowing any external access to need a cert for, from what I can tell...? I've rolled back to 3.7.0-1-01 for the time being.

I just upgraded to the latest and I'm getting similar errors to some of the above folks. Anyone find a solution? Logs show: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2022-12-18 09:22:08.574938 [info] Host is running unRAID 2022-12-18 09:22:08.594130 [info] System information Linux ef790d81a6ed 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux 2022-12-18 09:22:08.617472 [info] OS_ARCH defined as 'x86-64' 2022-12-18 09:22:08.638459 [info] PUID defined as '99' 2022-12-18 09:22:08.666729 [info] PGID defined as '100' 2022-12-18 09:22:08.695014 [info] UMASK defined as '000' 2022-12-18 09:22:08.714537 [info] Permissions already set for '/config' 2022-12-18 09:22:08.738688 [info] Deleting files in /tmp (non recursive)... 2022-12-18 09:22:08.764028 [info] Starting Supervisor... 2022-12-18 09:22:08,997 INFO Included extra file "/etc/supervisor/conf.d/sabnzbd.conf" during parsing 2022-12-18 09:22:08,997 INFO Set uid to user 0 succeeded 2022-12-18 09:22:09,000 INFO supervisord started with pid 7 2022-12-18 09:22:10,002 INFO spawned: 'start-script' with pid 58 2022-12-18 09:22:10,002 INFO reaped unknown pid 8 (exit status 0) 2022-12-18 09:22:10,705 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,705::INFO::[SABnzbd:1167] -------------------------------- 2022-12-18 09:22:10,705 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-12-18 09:22:10,705 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,705::INFO::[SABnzbd:1168] SABnzbd.py-3.7.1 2022-12-18 09:22:10,705::INFO::[SABnzbd:1178] Commit = "the code here looks like something I should remove" 2022-12-18 09:22:10,705::INFO::[SABnzbd:1180] Full executable path = /usr/lib/sabnzbd/SABnzbd.py 2022-12-18 09:22:10,705 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,705::INFO::[SABnzbd:1181] Arguments = "/usr/lib/sabnzbd/SABnzbd.py" "--config-file" "/config" "--server" "0.0.0.0:8080" "--https" "8090" 2022-12-18 09:22:10,705::INFO::[SABnzbd:1182] Python-version = 3.10.8 (main, Nov 1 2022, 14:18:21) [GCC 12.2.0] 2022-12-18 09:22:10,705 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,705::INFO::[SABnzbd:1183] Dockerized = True 2022-12-18 09:22:10,705 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,705::INFO::[SABnzbd:1184] CPU architecture = x86_64 2022-12-18 09:22:10,707 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,706::INFO::[SABnzbd:1187] Platform = posix - Linux-5.10.28-Unraid-x86_64-with-glibc2.36 2022-12-18 09:22:10,707 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,707::INFO::[SABnzbd:1193] Preferred encoding = UTF-8 2022-12-18 09:22:10,707 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,707::INFO::[SABnzbd:1215] SSL version = OpenSSL 3.0.7 1 Nov 2022 2022-12-18 09:22:10,707 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,707::INFO::[SABnzbd:1224] Certifi version = 2022.12.07 2022-12-18 09:22:10,707 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,707::INFO::[SABnzbd:1225] Loaded additional certificates from /usr/lib/sabnzbd/venv/lib/python3.10/site-packages/certifi/cacert.pem 2022-12-18 09:22:10,707 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,707::INFO::[SABnzbd:1246] Using INI file /config/sabnzbd.ini 2022-12-18 09:22:10,709 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,709::INFO::[postproc:134] Loading postproc queue 2022-12-18 09:22:10,710 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,710::INFO::[scheduler:190] Scheduling RSS interval task every 60 min (delay=15) 2022-12-18 09:22:10,710 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,710::INFO::[scheduler:201] Scheduling VersionCheck on day 2 at 23:58 2022-12-18 09:22:10,710 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,710::INFO::[scheduler:215] Setting schedule for midnight BPS reset 2022-12-18 09:22:10,710::INFO::[scheduler:218] Setting schedule for server expiration check 2022-12-18 09:22:10,710 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,710::INFO::[scheduler:223] Setting schedule for server quota check 2022-12-18 09:22:10,710 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,710::INFO::[__init__:320] All processes started 2022-12-18 09:22:10,710 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,710::INFO::[SABnzbd:336] Template location for Glitter is /usr/lib/sabnzbd/interfaces/Glitter 2022-12-18 09:22:10,711 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,710::INFO::[SABnzbd:336] Template location for Config is /usr/lib/sabnzbd/interfaces/Config 2022-12-18 09:22:10,711 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,711::INFO::[misc:1166] [N/A] Running external command: ['/usr/sbin/unrar'] 2022-12-18 09:22:10,714 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,714::INFO::[misc:1166] [N/A] Running external command: ['/usr/sbin/7za'] 2022-12-18 09:22:10,722 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,722::INFO::[misc:1166] [N/A] Running external command: ['/usr/sbin/par2', '-h'] 2022-12-18 09:22:10,725 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,725::INFO::[SABnzbd:423] SABYenc module (v5.4.4)... found! 2022-12-18 09:22:10,725 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,725::INFO::[SABnzbd:424] SABYenc module is using SIMD set: AVX2 2022-12-18 09:22:10,726 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,725::INFO::[SABnzbd:443] Cryptography module (v38.0.4)... found! 2022-12-18 09:22:10,726 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,726::INFO::[SABnzbd:448] par2 binary... found (/usr/sbin/par2) 2022-12-18 09:22:10,726 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,726::INFO::[SABnzbd:455] UNRAR binary... found (/usr/sbin/unrar) 2022-12-18 09:22:10,726 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,726::INFO::[SABnzbd:463] UNRAR binary version 6.20 2022-12-18 09:22:10,726 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,726::INFO::[SABnzbd:471] 7za binary... found (/usr/sbin/7za) 2022-12-18 09:22:10,726 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,726::INFO::[SABnzbd:473] 7za binary version 17.04 2022-12-18 09:22:10,726 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,726::INFO::[SABnzbd:484] nice binary... found (/usr/sbin/nice) 2022-12-18 09:22:10,726 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,726::INFO::[SABnzbd:488] ionice binary... found (/usr/sbin/ionice) 2022-12-18 09:22:10,728 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,728::INFO::[SABnzbd:1303] HTTPS keys are OK 2022-12-18 09:22:10,729 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,728::INFO::[SABnzbd:1435] Starting web-interface on 0.0.0.0:8090 2022-12-18 09:22:10,729 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,729::INFO::[_cplogging:213] [18/Dec/2022:09:22:10] ENGINE Bus STARTING 2022-12-18 09:22:10,831 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,831::INFO::[_cplogging:213] [18/Dec/2022:09:22:10] ENGINE Serving on http://0.0.0.0:8080 2022-12-18 09:22:10,956 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,956::INFO::[_cplogging:213] [18/Dec/2022:09:22:10] ENGINE Serving on https://0.0.0.0:8090 2022-12-18 09:22:10,956 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,956::INFO::[_cplogging:213] [18/Dec/2022:09:22:10] ENGINE Bus STARTED 2022-12-18 09:22:10,957 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,956::INFO::[SABnzbd:1474] Starting SABnzbd.py-3.7.1 2022-12-18 09:22:10,960 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,959::INFO::[dirscanner:117] Dirscanner starting up 2022-12-18 09:22:10,960 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,960::INFO::[notifier:123] Sending notification: SABnzbd - SABnzbd 3.7.1 started (type=startup, job_cat=None) 2022-12-18 09:22:10,962 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,962::INFO::[notifier:123] Sending notification: Error - [18/Dec/2022:09:22:10] ENGINE Error in HTTPServer.serve Traceback (most recent call last): File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/server.py", line 1807, in serve self._connections.run(self.expiration_interval) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/connections.py", line 198, in run self._run(expiration_interval) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/connections.py", line 241, in _run new_conn = self._from_server_socket(self.server.socket) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/connections.py", line 295, in _from_server_socket s, ssl_env = self.server.ssl_adapter.wrap(s) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/ssl/builtin.py", line 270, in wrap s = self.context.wrap_socket( File "/usr/lib/python3.10/ssl.py", line 513, in wrap_socket return self.sslsocket_class._create( File "/usr/lib/python3.10/ssl.py", line 1071, in _create self.do_handshake() File "/usr/lib/python3.10/ssl.py", line 1342, in do_handshake self._sslobj.do_handshake() ssl.SSLZeroReturnError: TLS/SSL connection has been closed (EOF) (_ssl.c:997) (type=error, job_cat=None) 2022-12-18 09:22:10,962 DEBG 'start-script' stdout output: 2022-12-18 09:22:10,962::ERROR::[_cplogging:213] [18/Dec/2022:09:22:10] ENGINE Error in HTTPServer.serve Traceback (most recent call last): File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/server.py", line 1807, in serve self._connections.run(self.expiration_interval) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/connections.py", line 198, in run self._run(expiration_interval) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/connections.py", line 241, in _run new_conn = self._from_server_socket(self.server.socket) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/connections.py", line 295, in _from_server_socket s, ssl_env = self.server.ssl_adapter.wrap(s) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/ssl/builtin.py", line 270, in wrap s = self.context.wrap_socket( File "/usr/lib/python3.10/ssl.py", line 513, in wrap_socket return self.sslsocket_class._create( File "/usr/lib/python3.10/ssl.py", line 1071, in _create self.do_handshake() File "/usr/lib/python3.10/ssl.py", line 1342, in do_handshake self._sslobj.do_handshake() ssl.SSLZeroReturnError: TLS/SSL connection has been closed (EOF) (_ssl.c:997) 2022-12-18 09:22:11,134 DEBG 'start-script' stdout output: 2022-12-18 09:22:11,134::INFO::[zconfig:61] No bonjour/zeroconf support installed 2022-12-18 09:22:11,135 DEBG 'start-script' stdout output: 2022-12-18 09:22:11,135::INFO::[ssdp:108] Serving SSDP on 172.19.0.24 as SABnzbd And inside the sabnzbd webui it's showing: ERROR an hour ago [18/Dec/2022:08:39:34] ENGINE Error in HTTPServer.serve Traceback (most recent call last): File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/server.py", line 1807, in serve self._connections.run(self.expiration_interval) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/connections.py", line 198, in run self._run(expiration_interval) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/connections.py", line 241, in _run new_conn = self._from_server_socket(self.server.socket) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/connections.py", line 295, in _from_server_socket s, ssl_env = self.server.ssl_adapter.wrap(s) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/ssl/builtin.py", line 270, in wrap s = self.context.wrap_socket( File "/usr/lib/python3.10/ssl.py", line 513, in wrap_socket return self.sslsocket_class._create( File "/usr/lib/python3.10/ssl.py", line 1071, in _create self.do_handshake() File "/usr/lib/python3.10/ssl.py", line 1342, in do_handshake self._sslobj.do_handshake() ssl.SSLZeroReturnError: TLS/SSL connection has been closed (EOF) (_ssl.c:997) I manually added a download through radarr and it 'appears' to function as expected. Of course we'd like to not see errors all the time though.

Ordered one and it will be here Tuesday the 18th. Array is up and all dockers started without issue. Thank you for your help JorgeB!

Roger. Thank you! While I'm doing that does anyone have a better suggestion for a flash drive? I "HAD" a Samsung USB 3.1 FIT Plus 32GB. Any better/more reliable then 14 months out there?

Makes sense. I've downloaded the backup from my servers and put it on an old USB I had laying around. I have it up and running now, array not started yet. Obviously it's saying: Uptime 7 minutes • Unraid OS GUID Error Purchase Key I'd like to order a new quality USB (which I though I had but it only lasted 14 months). What's my best option to get this back online today and use a new one in a couple days? I see that it appears they let you transfer the lic. once a year. I really don't want to say on the old one I had laying around. It's of unknown age and quality. Suggestions for my next steps?

I don't have a window machine but with Linux I get: $ sudo fsck -n -v /dev/sdb1 fsck from util-linux 2.37.2 fsck.fat 4.2 (2021-01-31) Checking we can access the last sector of the filesystem Boot sector contents: System ID "mkfs.fat" Media byte 0xf8 (hard disk) 512 bytes per logical sector 16384 bytes per cluster 32 reserved sectors First FAT starts at byte 16384 (sector 32) 2 FATs, 32 bit entries 7830016 bytes per FAT (= 15293 sectors) Root directory start at cluster 2 (arbitrary size) Data area starts at byte 15676416 (sector 30618) 1956999 data clusters (32063471616 bytes) 63 sectors/track, 255 heads 0 hidden sectors 62654593 sectors total Checking for unused clusters. Checking free cluster summary. /dev/sdb1: 4615 files, 41935/1956999 clusters I'm not seeing an issue with the above but when I tried to make a copy of the USB before running anything against it I got: $ ls /dev/disk/by-id/ ata-SanDisk_SD8TB8U256G1001_164821802268 ata-SanDisk_SD8TB8U256G1001_164821802268-part4 wwn-0x5001b448b4841df0-part1 ata-SanDisk_SD8TB8U256G1001_164821802268-part1 usb-Samsung_Flash_Drive_FIT_0378621030003521-0:0 wwn-0x5001b448b4841df0-part2 ata-SanDisk_SD8TB8U256G1001_164821802268-part2 usb-Samsung_Flash_Drive_FIT_0378621030003521-0:0-part1 wwn-0x5001b448b4841df0-part3 ata-SanDisk_SD8TB8U256G1001_164821802268-part3 wwn-0x5001b448b4841df0 wwn-0x5001b448b4841df0-part4 $ $ sudo dd if=/dev/disk/by-id/usb-Samsung_Flash_Drive_FIT_0378621030003521-0:0 status=progress | gzip -c > /home/rjacot/UNRAID_FLASH.img.gz666901504 bytes (667 MB, 636 MiB) copied, 80 s, 8.3 MB/s dd: error reading '/dev/disk/by-id/usb-Samsung_Flash_Drive_FIT_0378621030003521-0:0': Input/output error 1302752+0 records in 1302752+0 records out 667009024 bytes (667 MB, 636 MiB) copied, 80.1167 s, 8.3 MB/s $ ls /dev/disk/by-id/usb* ls: cannot access '/dev/disk/by-id/usb*': No such file or directory As you can see the /dev/disk/by-id/usb* is there before I run the command. It knocks it out when I ran the dd. :-/

I awoke this morning with my log file full. It's been quite some time since that has happened. I've made no HW changes nor added any new docker/VMs in a long time either. In syslog I'm seeing a lot of kernel: SQUASHFS error: errors. I've never seen these before. I've googled some but most of what I'm finding is related to a bad USB flash boot device and they can't boot, which isn't my case. I haven't tried starting the array yet, I don't want to cause more issues. Can someone help me or point me where to dig deeper please? cube-diagnostics-20221006-0643.zip

Hello mmedic, Did you find a solution for this? I had the same issue this past weekend. Thanks!

I get redirected to login, it just never pulls/shows them. I've done every icon one at time. It's something with chrome, Firefox and safari work as expected after the redirect and login.