danb35
Hall of Famer
- Joined
- Aug 16, 2011
- Messages
- 15,504
By hostname, or by IP address? If the latter, there's your problem--you need to use the hostname (same as you set HOST_NAME for the script).I headed to the login page
By hostname, or by IP address? If the latter, there's your problem--you need to use the hostname (same as you set HOST_NAME for the script).I headed to the login page
By hostname, or by IP address? If the latter, there's your problem--you need to use the hostname (same as you set HOST_NAME for the script).
Sure. You can destroy the jail withIs there an easy way to delete the install of nextcloud and start from scratch?
iocage destroy -f nextcloud
, and then clear out your storage directories--by default that would be everything in $POOL_PATH/nextcloud/.JAIL_INTERFACES not set, defaulting to: vnet0:bridge0 Existing Nextcloud config detected... Checking Database compatibility for reinstall ls: /mnt/Storage/nextcloud/db/mariadb: No such file or directory ERROR: You can not reinstall without the previous database Please try again after removing your config files or using the same database used previously
# Check for reinstall if [ "$(ls -A "${CONFIG_PATH}")" ]; then echo "Existing Nextcloud config detected... Checking Database compatibility for reinstall"
Hi mr. danb35, you're right, i will add a second 4TB to create mirror,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.
But consider adding a second 4 TB disk to create a mirror--which you'll unfortunately need to do at the CLI.
From: "Let's Encrypt Staging Expiry Bot" <staging-expiry@letsencrypt.org>
To: admin@mydomain.com
Sent: Monday, July 6, 2020 11:16:04 AM
Subject: Let's Encrypt staging environment certificate expiration notice for domain "cloud.mydomain.com"
Hello,
[ Note: This message is from the Let's Encrypt staging environment. It likely is not relevant to any live web site. ]
You issued a testing cert (not a live one) from Let's Encrypt staging environment. This mail takes the place of what would normally be a renewal reminder, but instead is demonstrating delivery of renewal notices. Have a nice day!
We recommend renewing certificates automatically when they have a third of their
total lifetime left. For Let's Encrypt's current 90-day certificates, that means
renewing 30 days before expiration. See
https://letsencrypt.org/docs/integration-guide/ for details.
Details:
DNS Names: cloud.mydomain.com
Expiration Date: 16 Jul 20 04:28 +0000)
Days to Expiration: 10
For any questions or support, please visit https://community.letsencrypt.org/. Unfortunately, we can't provide support by email.
For details about when we send these emails, please visit https://letsencrypt.org/docs/expiration-emails/. In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message.
If you are receiving this email in error, unsubscribe at http://mandrillapp.com/track/unsub....email=a%2A%2A%2A%2A%40f%2A%2A%2A%2A.%2A%2A%2A
Regards,
The Let's Encrypt Team
If you've run remove-staging.sh and are now using a production certificate (you can easily tell because your browser will give you certificate warnings if not), you can ignore this email. As it says:by the way , 2 days ago i receive an email from let'sencrypt like below :
[ Note: This message is from the Let's Encrypt staging environment. It likely is not relevant to any live web site. ]
Looks like a firewall problem.what am I doing wrong?
Installation without a script is all ok. Previously, after installation, you had to delete the line before the certificate started. Maybe my script doesn’t work.?Looks like a firewall problem.
Maybe space monkeys corrupted your data. Maybe there's a configuration issue. Maybe there's a firewall issue. With what you've posted, there's no way to know, and really not even a good place to start.Maybe my script doesn’t work.?
It could, if:If my DNS hosting where I bought the domain does not support can cause such an error?
service caddy status
). If it isn't, see what errors you find in /var/log/caddy.log.