Where the script tells you--in your FreeNAS system, at /root/nextcloud_db_password.txt.I lost the admin password where i can find?
I can't see your screen shots, but if you're getting a certificate error, there are a few possibilities:other say certificate not valid.
Hi Mr.danb35,Check the certificate of your current installation (you can see it in your browser). If it's issued by "Let's Encrypt Authority X3", you're good. If not, you're probably getting certificate errors anyway.
Since you only have one disk right now, you apparently don't care about redundancy. In that case, you should be able to replace the old disk through the GUI. Plug in the new one, go to Storage -> Pools, click on the gear, click Status, select the three vertical dots to the right of your current disk, select Replace, pick the new disk. Wait for the server to do its thing, then you can remove the old disk.i want to expand my nextcloud storage from 500GB to 4TB, the question is "how to do" ?
Unless you used DNS validation to get your cert, yes, it will.will caddy have trouble renewing my Let's Encrypt certificate with the NAT rule on port 443 disabled?
Ok I think I finally have DNS validation working. No errors in my caddy log after turning off 80 and 443 forwarding in my router and restarting. Is there a way to test the certificate renewal. Something like Certbot dry run option? Can you edit the Caddyfile to change to DNS Validation?Unless you used DNS validation to get your cert, yes, it will.
root@batman[~/freenas-iocage-nextcloud]# ./nextcloud-jail.sh JAIL_INTERFACES not set, defaulting to: vnet0:bridge0 nextcloud successfully created! Testing Host DNS response to pkg.freebsd.org Testing nextcloud's SRV response to pkg.freebsd.org pkg.freebsd.org's SRV record could not be verified. Testing nextcloud's DNSSEC response to pkg.freebsd.org pkg.freebsd.org could not be reached via DNSSEC. Testing nextcloud's DNS response to pkg.freebsd.org pkg.freebsd.org could not be reached via DNS, check nextcloud's network configur ation Failed to creat jail root@batman[~/freenas-iocage-nextcloud]#
GNU nano 4.4 nextcloud-config JAIL_IP="192.168.1.199/18" DEFAULT_GW_IP="192.168.50.1" POOL_PATH="/mnt/backup" TIME_ZONE="America/New_York" HOST_NAME="my website here" DNS_CERT=1 DNS_PLUGIN="cloudflare" CERT_EMAIL=xxxxxxx@gmail.com DNS_ENV="CLOUDFLARE_EMAIL=xxxxxxx@gmail.com CLOUDFLARE_API_KEY=global API here
Your jail IP and Gateway are on different subnets.
It's a DNS problem, in at least two ways:
- From insideyour network, whatever you set as HOST_NAME needs to resolve to the IP address of your jail. If you have a router that doesn't suck, you can configure this on your router--I only have experience with pfSense in this regard, and it's entirely capable of doing this. If you aren't able to configure your router to do this, you have a few other options:
- Upgrade your router's firmware to something like dd-wrt, if it's available for your router
- Use something else for your LAN's DNS server, like maybe Pi-Hole
- As a last resort, edit your hosts/hosts.txt file
- From outside your network, whatever you set as HOST_NAME needs to resolve to your public IP address, if you want to be able to access your Nextcloud installation from outside. You'll also, in that case, need to forward ports 80 and 443 to your jail--again, this will be done on your router.
iocage exec nextcloud /root/remove-staging.sh
to get rid of the SSL errors.