I like DNS validation better, and one of the reasons is that the jail doesn't have to be open to incoming connections on ports 80 and 443 for it to work. But both will work, and most folks would probably prefer to have the Nextcloud installations open to the Internet anyway
I don't know that DNS validation is necessarily safer than HTTP validation, nor do I know what the majority chooses. HTTP validation does require that a couple of ports on the jail be accessible from the Internet, but if that's a configuration you'd be using anyway, there's no additional exposure. IETF believes that both are comparably secure for the purpose of validating domain control.If DNS validation is safer then the port-forwarding variant why does the majority choose / use portforwarding?
Great Job. Worked Great!
I wanted to use ElasticSearch and Tesseract OCR but I am unsure how to safely add the requirements to my install
There's your problem, the same bug in 11.2-U2.1 (and perhaps earlier) that's bitten others. It seems to have been fixed in 11.2-U3, though. You should be able to fix this by stopping the jail, adding the mountpoints, and starting it back up. You'll need to add your DB_PATH (which defaults to POOL_PATH/db) at /var/db/mysql, and FILES_PATH (which defaults to POOL_PATH/files) to /mnt/files.currently I am only seeing the Portsnap mnt point.
There's your problem, the same bug in 11.2-U2.1 (and perhaps earlier) that's bitten others. It seems to have been fixed in 11.2-U3, though. You should be able to fix this by stopping the jail, adding the mountpoints, and starting it back up. You'll need to add your DB_PATH (which defaults to POOL_PATH/db) at /var/db/mysql, and FILES_PATH (which defaults to POOL_PATH/files) to /mnt/files.
Check out the latest update under the "Status" heading and see what you think.Perhaps adding something to the github page with instructions for fixing the mount points would be useful?
Sorry, try"service mysql stop"
service mysql-server stop
.