psm321

That depends on what you consider "core"... The unraid kernel driver (which is what I would call "the main array") is in fact open source. But I guess shfs is a major component for people too... I'm pretty concerned that there's been no answer on the privacy issues...

Thanks! Appreciate the heads-up on cache pools too!

My servers are currently on 6.7/6.8 and I'm looking to upgrade to latest. However, some of the changes I've read about concern me, so I want to retain the ability to go back if I cannot adjust to them. I understand I'd have to back up my configurations and such -- just wanted to double-check that the actual unraid driver on-disk format/superblock isn't going to get upgraded to something the older version can't read.

Did you ever figure out where to find raid6_gen_syndrome?

Perfect, thanks!

I just wanted to bump this once before working on a custom container as I'm coming up on renewal. Sorry if I missed a reply somewhere, didn't find one in a quick search.

For anyone else reading this, I did end up ordering an ASM1142 card ( https://www.amazon.com/gp/product/B00XKEBYYE ) and it works fine natively.

I'm on my phone so I didn't check all of them, but at least some of the plugins have an individual option for it. The one I used has it and so does the nsone one. https://certbot-dns-rfc2136.readthedocs.io/en/latest/ https://certbot.eff.org/docs/using.html#dns-plugins err, command-line options, not config file options afaict. That would be too convenient

I would personally suggest trying a longer propogate delay. I was having similar issues with 30 seconds. Unfortunately AFAIK there's not a container variable for this -- I ended up editing something inside the container.

Perhaps it's running and unRAID lost track of it? (not sure if that's possible, I'm new to all this). docker ps | grep "0.0.0.0:443" should tell you what container is using it

netstat -nptl (I believe it's in nerd tools) should show you what's listening on that port

Are there by chance any hooks in the startup of the container to run a custom user script? I need to patch the certbot rfc2136 plugin with some hacks to get it to work with my DNS provider (I don't understand my hacks well enough to actually submit upstream). I figure I'll probably need to build my own container layer on top, but wanted to check before going ahead with that.

I had in fact added STAGING myself after reading the dockerhub docs (it wasn't in the template, including under additional settings). I was reporting that that variable no longer works since --server was added to the certbot commandline inside the container a few days ago to support ACMEv2, as --staging (which STAGING sets) does not work with --server

Not sure if this is on-topic here since STAGING isn't exposed in the unraid template, but the --staging and --server parameters to certbot don't seem to work together (even when I manually edit the server URL to be the staging v2 one). I'm working around this by removing $STGNG from the certbot line in 50-config and setting the --server URL to staging v2 --server value conflicts with --staging

Thank you for this! Could you please consider removing these lines from nginx/site-confs/default? error_page 403 /core/templates/403.php; error_page 404 /core/templates/404.php; These cause user creation with a weak password to fail silently (the button appears to do nothing) instead of showing an error. See: https://github.com/nextcloud/server/issues/3847#issuecomment-287740126 https://github.com/nextcloud/server/pull/2004#issuecomment-291007260 Thanks!