cheww

Oh i fixed it, i don't know how i worked it out but i did this.. Terminal from Unraid type in `docker exec -it authentik /bin/bash` (authentik being the docker app) then i got a new prompt and then type in `ak` (got this from the second line from authentiks website "kubectl exec -it deployment/authentik-worker -c worker -- ak create_admin_group username") all this text popped up on the screen so i thought Hmm.. then type in 'ak create_admin_group username' (the user name i am using on asuthentik) Then all this text came on the screen and right down the bottom i see.. "User 'username' successfully added to the group 'authentik Admins'." Well i do say, i am very proud. lol Thank you for helping.

Thanks for the information. When i run it in unraids terminal it says "unknown flag: --rm" Thanks..

Hi, In Authentik, I accidentally deleted all the user groups. So my user account doesn't have access to any of the Admin stuff. I saw you can fix this issue here .. https://docs.goauthentik.io/docs/troubleshooting/missing_admin_group However i don't know how to run this command 'docker compose run --rm server create_admin_group username' in unraid. I tried it in the Authentik console and the unraid console however they both came up with errors. Does anyone know how i can fix this or am i going to have to reinstall everything again? Thanks.

Just another update - I have sorted out the ATA errors. The cause was not enough power to the back plane. I have a 24 bay hdd case with a back plane that has 24 sata ports and 6 molex power connectors. i had 2 lanes from the Power supply going to all 6 power ports. I disconnected 1 from each 3 ( 3 control 12 hdd and 3 control the other 12 hdd) power ports and added another lane of power so now its getting 3 lanes of power from the power supply. The ata errors have stopped completely i have started a parity check and its been going for 6 hours and not one error. Hope this helps someone ever experiencing this issue.

Switching to ipvlan sold the crashing issue. Which is most important!! Thank you. Replacing the cables did not fix the ATA errors. Need to find out which hard drives this issue is affecting or may be my MB sata ports or LSI card issue. But thanks for helping with the main issue.

Hello!, I'm having an issue with my server its crashing every 3-4 days. Becomes unresponsive and unreachable. II have noticed that i am getting ATA-errors, i'm not sure if that's was causing that issue. The server usually crashes after midnight when its doing nothing. I originally thought it was the backup it was doing of the docker apps which happens after midnight. I have disabled the backups and it still crashed. I have replaced all the Sata cables and the sas to sata cables with name brand but it still happened. A little history i have these 10tb seagate hdd's that a few people here had issues with and the LSI cards. Hard drives would go missing or just error out. I had to put all my 10 tb hdd's onto the motherboard Sata ports and all my 3tb wd hdd are using the LSI card. i have 2 cache drives using an internal PCI sata card and i have 1 nvme sata drive aslo using it as an incoming data drive for download coming into the server. any advice would be most welcome. I think my next step is to try safe mode. Could some one please look at my diags to see if there is any issue? For the Syslog it crashed some time between Jan 24 00:00:37 to Jan 24 15:29:47 which is when i came home from work and powered it off using the power button. Cheers and many thanks. gauntlet-diagnostics-20240124-2032.zip syslog-192.168.4.12.log

Hi All, So i decided to stop the parity check - reading in another forum that even if the drive is not readable running a parity check wont solve an invalid or missing drive. So i stopped the array and ran it it maintenance mode clicked on drive 4 and ran the XFS check.. It found a few errors so i took off the -n and ran it again. Stated to remount the drive and check it if its not there then to go back to maintenance mode and use the -L option. Did that and started the array again as normal and hey presto the drive and all files are back. It moved some files over to a lost and found directory. They were only a few jpg files nothing important. I've decided to run the check on drives 1 and 3 as Trurl noted to check connections. Which i also did before i ran the maintenance mode stuff. I will re run the parity check and make sure that's all in sync too. Thank you Happy i solved something by myself for once

Hi All, Over the last 3 days i have had lockups with my server. They happened during the night while i was sleeping. So unsure why its just started happening. First day it check parity and found 7 errors Second day i last time i checked it found 711 errors i don't think it finished its check third day (today) its checking parity again so far 1 error and its 7.8% through This morning i also noticed a lot of files missing. I check plugin fix common problems and its stated that unable to write to disk4 Drive mounted read-only or completely full. Begin Investigation Here. I went into main tab and clicked browse disk 4 and its come up as invalid path. its used 7.51TB and there is still 2.49tb free. Unsure if i should continue the parity check or restart in safe mode and do the drive check to disk 4. Any advice would be appreciated. Thanks gauntlet-diagnostics-20230219-1149.zip

Bad news .. Started happening again just now for me. one of the new HDD's and one of the old ones at the same time.. Both have the updated firmware. I have connected them back on to the Motherboard.. get it stable again and try that EPC thing in the first post. Back in about 15-20 days let you know how it went

Hi All, I would like to say thanks for this thread solved my issue. I have 4 X ST10000VN0004 10TB HD's Had SC60 Firmware (purchased 3-4 years ago) and 2 X ST10000VN0008 10 TB HD's Has SC61 Firmware. (purchased 6 Months ago) Checked the Seagate website to see if there was any firmware updates and there was an update for the ST10000VN0004 10TB HD's which updates SC60 Firmware so SC61 Firmware. I was getting tons of read errors on the 4 drives and occasionally it would drop one of the drives when connected to my LSI card. When i connected the drives to my motherboard i had no issues for months. I tried replacing cables no luck, i have an LSI card and a HP expander took them off the expander and connected it directly to the LSI card no luck. In the end i though it was my sata back plane since the drives worked no probs directly on the motherboard. Didn't even think that a firmware on the drives could have a compatibility issue with LSI cards. Anyway happy its all sorted. Thanks so much.

This helped me thanks .. What i did was edited the plex.subdomain.conf file and replaced proxy_pass https://$upstream_plex:32400 with proxy_pass http://192.168.178.23:32400 <-- your local ip for plex .. My plex docker stayed at host Then the second part was you had to go into plex > Settings > network. under Custom server access URLs put the plex domain in i.e https://plex.yourdomain.com:443 i when to the domain and it worked. it asked me to sign in again and bingo! hope this helps someone ..