usr/local/share/nextcloud/fix-apps_paths.json”
Correct.I think you are using the Neilpang/acme.sh script.
That's it. If you're going to add another domain to the same cert (as opposed to making a different cert with a different domain), make sure you specify the cert/key paths and reload command--you'll find the original command to issue at or about line 171 of the script.Looks like it is as simple as adding with -d.
I haven't been able to duplicate this when using a self-signed or a Let's Encrypt cert. Can you give it a try again? If you're still having trouble, post the exact steps you took along with what's happening, and I'll see if I can get to the bottom of it.I get a “Too many redirects” error.
So I actually managed to get it working albeit by using a different (self signed cert) encryption method. As far as using the Lets Encrypt method, I followed your directions to the letter. I didn't even get any error messages when running the script.I haven't been able to duplicate this when using a self-signed or a Let's Encrypt cert. Can you give it a try again? If you're still having trouble, post the exact steps you took along with what's happening, and I'll see if I can get to the bottom of it.
iocage console nextcloud acme.sh --issue -w /usr/local/www/apache24/data/ -d ${HOST_NAME} -k 4096 --fullchain-file /usr/local/etc/pki/tls/certs/fullchain.pem --key-file /usr/local/etc/pki/tls/private/privkey.pem --reloadcmd "service apache24 reload"
netstat -na | grep -i LISTEN
I've seen other reports of this when people didn't use vnet. If you had vnet turned off, try re-running the script with it turned on and see if you see the same thing.But when I try to login to the nextcloud web page, it gives me the FreeNAS GUI login, not a Nextcloud login.
OK, trying that now.try re-running the script with it turned on
nextcloud is not running, starting jail mount_nullfs: /mnt/iocage/jails/nextcloud/root/usr/ports: Resource deadlock avoided jail: /sbin/mount -t nullfs -o rw /mnt/WCT-Pool/LeesData/NextCloud/portsnap/ports /mnt/iocage/jails/nextcloud/root/usr/ports: failed
I'm pretty sure this is your actual problem. Unlock your pool, and you should be fine.Also, the pool (Storage->Volumes) shows as status LOCKED.
I'm pretty sure this is your actual problem. Unlock your pool, and you should be fine.
[root@freenas ~]# iocage restart nextcloud nextcloud is not running! * Starting nextcloud + Start FAILED mount: /mnt/iocage: No such file or directory jail: /sbin/mount -t nullfs -o rw /mnt/HomeServer/portsnap/ports /mnt/iocage/jai ls/nextcloud/root/usr/ports: failed
[Sat Oct 27 00:25:41 CEST 2018] Using stage ACME_DIRECTORY: https://acme-staging.api.letsencrypt.org/directory [Sat Oct 27 00:25:42 CEST 2018] Standalone mode. [Sat Oct 27 00:25:42 CEST 2018] Registering account [Sat Oct 27 00:25:43 CEST 2018] Registered [Sat Oct 27 00:25:44 CEST 2018] ACCOUNT_THUMBPRINT='k9fyyB4-vl8BG6MTW3hY7v5Qo9mRjvNXZUaBP1fbcWQ' [Sat Oct 27 00:25:44 CEST 2018] Creating domain key [Sat Oct 27 00:25:44 CEST 2018] The domain key is here: /root/.acme.sh/domain.xyz/domain.xyz.key [Sat Oct 27 00:25:44 CEST 2018] Single domain='domain.xyz' [Sat Oct 27 00:25:44 CEST 2018] Getting domain auth token for each domain [Sat Oct 27 00:25:44 CEST 2018] Getting webroot for domain='domain.xyz' [Sat Oct 27 00:25:44 CEST 2018] Getting new-authz for domain='domain.xyz' [Sat Oct 27 00:25:45 CEST 2018] The new-authz request is ok. [Sat Oct 27 00:25:45 CEST 2018] Verifying:domain.xyz [Sat Oct 27 00:25:45 CEST 2018] Standalone mode server [Sat Oct 27 00:25:49 CEST 2018] Pending [Sat Oct 27 00:25:51 CEST 2018] Pending [Sat Oct 27 00:25:54 CEST 2018] Pending [Sat Oct 27 00:25:56 CEST 2018] Pending [Sat Oct 27 00:25:58 CEST 2018] Pending [Sat Oct 27 00:26:01 CEST 2018] Pending [Sat Oct 27 00:26:03 CEST 2018] Pending [Sat Oct 27 00:26:05 CEST 2018] Pending [Sat Oct 27 00:26:08 CEST 2018] Pending [Sat Oct 27 00:26:10 CEST 2018] Pending [Sat Oct 27 00:26:12 CEST 2018] Pending [Sat Oct 27 00:26:14 CEST 2018] Pending [Sat Oct 27 00:26:17 CEST 2018] Pending [Sat Oct 27 00:26:19 CEST 2018] domain.xyz:Verify error:Invalid response fromhttp://domain.xyz/.well-known/acme-challenge/sl5rvS862-zjMjOZ-bFQORnX_tsNuwX-BFkbPQ16Qws: [Sat Oct 27 00:26:19 CEST 2018] Please add '--debug' or '--log' to check more details. [Sat Oct 27 00:26:19 CEST 2018] See: https://github.com/Neilpang/acme.sh/wiki/How-to-debug-acme.sh
[root@nextcloud ~]# service apache24 start Performing sanity check on apache24 configuration: AH00526: Syntax error on line 27 of /usr/local/etc/apache24/Includes/domain.xyz.conf: SSLCertificateFile: file '/usr/local/etc/pki/tls/certs/fullchain.pem' does not exist or is empty Starting apache24. AH00526: Syntax error on line 27 of /usr/local/etc/apache24/Includes/domain.xyz.conf: SSLCertificateFile: file '/usr/local/etc/pki/tls/certs/fullchain.pem' does not exist or is empty /usr/local/etc/rc.d/apache24: WARNING: failed to start apache24
iocage console nextcloud export CF_Key="sdfsdfsdfljlbjkljlkjsdfoiwje" export CF_Email="xxxx@sss.com" acme.sh --issue --dns dns_cf -d your_fqdn --fullchain-file /usr/local/etc/pki/tls/certs/fullchain.pem --key-file /usr/local/etc/pki/tls/private/privkey.pem --reloadcmd "service apache24 reload"
-bash: acme.sh: command not found
All the "Pending" lines indicate that the connection from Let's Encrypt isn't reaching your server. Do you own domain.xyz? Do its DNS records point to your server? Have you forwarded port 80 on your router to the IP address of your jail? Is your ISP blocking port 80?[Sat Oct 27 00:25:45 CEST 2018] Verifying:domain.xyz
[Sat Oct 27 00:25:45 CEST 2018] Standalone mode server
[Sat Oct 27 00:25:49 CEST 2018] Pending
[Sat Oct 27 00:25:51 CEST 2018] Pending
That's expected--its configuration requires a cert and key that aren't there, so it can't start. Once you obtain the cert, this problem will go away.check service apache24 status it's not running.
iocage console nextcloud cd /usr/local/etc/apache24/Includes/ mv $FQDN.conf $FQDN.conf_old service apache24 start