Strange, it's missing the braces. It should look like this:
tls { ca https://acme-v02.api.letsencrypt.org/directory dns cloudflare }
This is addressed here:The "X-Frame-Options" HTTP header is not set to "SAMEORIGIN". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly.
OH!!! SH*T... all ive needed to do is ADD the line? Ive spent like 3 hours LOOKING for the line in other config files :)This is addressed here:
![]()
security/performance issues with default install · Issue #80 · danb35/freenas-iocage-nextcloud
After deploying the nextcloud-instance with this script, there are two warnings reported by the instance itself (under admin/settings/administration/overview): The "X-Frame-Options" HTTP header is ...github.com
I'll need to update the Caddyfile in the repo to really fix it, but you can modify yours by adding the line indicated in that issue.
I'll need to update the Caddyfile in the repo to really fix it, but you can modify yours by adding the line indicated in that issue.
Yes, but it'd be manual work. Briefly, you'd set it up with NO_CERT=1, and then when you want to use SSL instead, change the Caddyfile accordingly (you can use one of the templates with the script as a model). If you're fine using Let's Encrypt, use one of those Caddyfile versions--that's the most-common way to use Caddy. Otherwise, you can use the self-signed cert version along with any cert you've obtained elsewhere.is it possible to set up with no SSL security at installation and then set up a secure connection after install?
The recommended way to run occ is withYou may also want to have occ chmod set to executable
php occ ...
, so there's no reason that occ itself needs to be executable.You shouldn't ever need to SSH into a jail--SSH to your FreeNAS box, thenhave managed to SSH into the jail.
iocage console nextcloud
. And apparently you aren't logging in as root, otherwise you wouldn't be prompted for a password (which the www user doesn't have)--and the latter is the real issue. So, you need to become root in the jail--either log in as root directly, or su
to root once you're logged in (which will require root's password, which you'll need to set--better to do as I said initially, be root on FreeNAS, then enter the jail). You'll then be able to su to another user without needing that user's password.You could do it through the GUI (the command would beCould you also advise on how to plan a cron job to keep the previews up-to-date?
iocage exec nextcloud su -m www . . .
), but I'd lean toward doing it as a cron job in the jail itself. Enter the jail, do export EDITOR=nano
, and then crontab -u www -e
, which will bring up the www user's crontab file. Because it's already the www user, the "su -m www" part isn't needed, so the command would just be php /usr/local/www/nextcloud/occ preview:pre-generate-all -vvv
(unless the command for repeat use is different).Yes, that's what's going on. What version of FreeNAS are you using? And what's in your nextcloud-config file (masking any DNS credentials)?i think somehow the jail kannt connect to the internet or something like taht.