diehardbattery

If you mean the Docker Safe New Perms then I did try that, unfortunately it didn't help.

Can someone please help? Not everyone knows how to resolve these issues independently and unfortunately, I am one of them. I just want this working again...

Any ideas?

No I haven't done anything other than run the command you provided earlier... When I Click show more there is nothing. The arow moves up as if to show more info but there's nothing there:

Okay, I ran the command but now when I try to access I get this error: Configuration was not read or initialized correctly, not overwriting /var/www/html/config/config.php I tried changing permissions for everything in the /config folder to 777 but that does not work either. I restored a backup that was made from the CA appdata backup utility and ran the upgrade command again. After restarting the container, it appears the docker log is still complaining about user id 33. I have not done anything custom that I am aware of that would make the current user id what it is (99)? Initializing nextcloud 28.0.3.2 ... Upgrading nextcloud from 28.0.2.5 ... => Searching for scripts (*.sh) to run, located in the folder: /docker-entrypoint-hooks.d/pre-upgrade Console has to be executed with the user that owns the file config/config.php Current user id: 33 Owner id of config.php: 99 Try adding 'sudo -u #99' to the beginning of the command (without the single quotes)

Should -u 33 be -u 99? When I run it, I get this: Console has to be executed with the user that owns the file config/config.php Current user id: 33 Owner id of config.php: 99

So I ran into this when trying to access my instance today... and I can't make heads or tails on how to proceed. Unfortunately I'm not very good at translating stuff from other nexcloud variants (aio, etc). Trying to update via the unraid docker page shows everything is up to date.

Having an issue with the cronjob container: 1. I installed the cronjob container. Now my Admin overview gives the following error: It was not possible to execute the cron job via CLI. The following technical errors have appeared: - Your data directory is readable by other users. Please change the permissions to 0770 so that the directory cannot be listed by other users. Changing the data directory to 0770 says the directory is invalid when I restart the container and can't go anywhere...

Gotcha... if the key is good enough then I'll probably just leave it at that

Okay, a bit off topic, but how would that work if I wanted to connect via cloudflare tunnel? I have an A record for the domain currently, and it appears I'm unable to add a tunnel with that because it says there's already a record with the name and the documentation they reference to troubleshoot, it seems a bit confusing to me. As for the exe file, are you referring to the exe for the client? That's all I have installed on Windows, the rest is on Unraid.

Yeah, that's why I'm doing the port forwarding.. its just that I'm not sure why swag still seems to want to intercept it and I am reasonably sure that I have the port forwarding setup correctly in OPNSense... UPDATE: I found the public key in the logs and pasted it into the key field on the client with nothing else. Now it works, even from outside access. How safe is this? Should I continue to try and get my subdomain working? Would I still need the public key in that case?

Trying to get Rustdesk-AIO running from my cloudlfare domain (have tried proxied and dns only). I know that part seems to be working. But as I understand it, Rustdesk shouldnt use a reverse proxy. I have swag running, and every time I try to access my rustdesk domain I get the swag welcome page. I have a router running OPNSense and believe I have the port forwarding correct. However it's still not working. What am I missing?

Just recently I noticed that my services using swag stopped working. Upon checking the logs I found what you see in the screenshots. Using WinSCP, I checked the keys folder, and the permissions appear to be correct. I have not changed anything so I dont know what caused this.

I came across this guide, which seems to be the easiest way to get Nextcloud up and running. Wondering if anyone else has done this, and if so, how do you setup the shares? The guide seems to leave this out unless I'm misreading something? Note: The only thing I did differently from the guide is to use Portainer-CI as it seems Portainer-CE isn't available anymore?

Not sure where to look... nice number of percent full though lol... diagnostics-20230824-0926.zip

Okay, I think I get it now. This is my first rodeo with this type of situation so just questioning every little thing lol.

With only one parity drive, how will that work? In other words, what will sync that drive? Do the data drives have bits of parity information to use for the re-sync?

I also posted this on r/unraid: So, I used to have 1 NAS now I have 2. The first NAS was a 8 x 8TB with dual parity, the second one will be identical in terms of bays and parity. One of the parity drives failed on the 8TB array. I replaced all drives with larger ones in the first NAS. Now that I have 2 of them, I moved the larger drives to the new NAS and used the same flash drive from the old one. Everything seems fine. I created a new USB for the first NAS. But now that there's only one parity drive, it is warning me that all data will be overwritten once I start the array. It is also encrypted form the older NAS so i dont know if that has anything to do with it. I made sure to assign the drive that was parity before as parity, and the rest are the data drives. How do I fix this... or am I screwed?

I get that. But I don't think I agree 100% with what you're saying. Yes, you are correct, there are thousands of setups that are just fine, and obviously they outnumber anything else by a wide margin. The excuse that the problem can't be consistently reproduced seems like a copout to me. Most of us are paying for the software. Shouldn't it be part of the developers job to investigate things like this and (hopefully) come up with a workaround or solution? Just based on what I could find, there is a not so small number of users who have the issue as well. Those only represent a finite number of users who have gone through it, not counting an unknown number of others who dont post on forums (here, Reddit, Discord). Granted there are multiple ways to fix it, and most probably work. It doesn't help that for my use case I'm using what's supposed to be a proprietary nas and repurposing to Unraid. It's my understanding that USB is USB no matter what. Without getting into the whole charge vs data part of it, the backward compatibility should be stable. Of course, this does not account for the number of flash drives available, their quality, etc. There are other NAS operating systems who get by just fine with a HDD, SSD, DOM, etc. I suppose you could argue that part of Unraid is proprietary too, hence part of the issue. It just seems that in 2023 there would be a better way. Perhaps I'm wrong.

See, I really wouldn't have minded nearly as much if that's all I had to do.. but a 22TB rebuild takes ~40 hrs and having to start that from scratch multiple times now is starting to test my patience a little lol. Then whenever I want to try a different stick I have to wait for limetech to reset my key because you can only do that once a year, so my one year is now reset. I like the versatility that Unraid offers when mixing and matching drives so I really don't want to look elsewhere... The other issue being that, while you are 100% correct in that it's complex problem, we're paying for the license. I'm not saying just because its paid its not going to be trouble free but it should at least be better than if it was completely free. Just my 2 cents.

Therein lies the difference... you have a 2.0 port to utilize... evidently I either have to cross my fingers that the 3.0 ports do their backward compatibility reliably, or I just have really bad luck with USB flash drives. I have a Cruzer Glide 16GB I'm using now... I mean I know Unraid is somehat known for running well on older hardware but eventually there will come a point where 2.0 ports won't exist period. What then?

Yeah, and I just corrupted again.. time for a new usb stick me thinks... On that note, The current USB is still usable, but I can't determine anything else thats causing this definitively except the USB itself. I'm gonna need to contact limetech to have my key reset when I change it. I've done it before but I cant remember if I was still able to use the NAS normally with the new usb until it's reset... if not is there a way I can get the GUID beforehand or will I be stuck until limetech resets?

If I corrupt again or the rebuild finishes I'll crack open the case to take a look. But researching google and asking on the qnap forums didn't turn up anything on it. Or in the unlikely event that someone else that has the same NAS sees this and volunteers LOL.

I thought that too.. but it wasnt until after I started the second rebuild... it just corrupted again so now is good time as any lol UPDATE: No option to change in the BIOS...

Well, happened to be up late, checked the progress and lo and behold it corrupted again.. no additional writes...