ropes

That error message was due to user error, had some older legacy certs for some critical containers that I kept around when migrating to the CF origin cert. My lazy behind never went back in to tidy these up once the origin certificate was fully tested and confirmed as working. Removing these older certs in the NPM dashboard, under Certificates menu, has completely removed the errors from my logs. TL;DR - Certbot tried HTTP validation > Cloudflare intercepted > ACME challenge not exposed due to Cloudflare proxy > Validation failed

Not yet, need to get back from work before I can see if anything was written to it, although not holding out much hope after seeing this line in my logs. error Saving debug log to /data/logs/letsencrypt.log

I had restored my data/configuration for nginx proxy manager from a backup after the update yesterday prior to rolling back to v25.09.1, just to get me going again. Unsure if this will make a difference for others that just rolled back and have the db migration issue. Just updated, I also made sure to target the new version - v26.03.2. There are still some errors in my container log. [app ] [3/18/2026] [5:22:18 PM] [SSL ] › ℹ info Renewing LetsEncrypt certificates for Cert #29: test.example.com [app ] [3/18/2026] [5:22:18 PM] [SSL ] › ℹ info Command: certbot renew --force-renewal --config /etc/letsencrypt.ini --work-dir /tmp/letsencrypt-lib --logs-dir /data/logs --cert-name npm-29 --preferred-challenges http --no-random-sleep-on-renew --disable-hook-validation [app ] [3/18/2026] [5:22:21 PM] [SSL ] › ✖ error Saving debug log to /data/logs/letsencrypt.log [app ] Failed to renew certificate npm-29 with error: Some challenges have failed. [app ] All renewals failed. The following certificates could not be renewed: [app ] /etc/letsencrypt/live/npm-29/fullchain.pem (failure) [app ] 1 renew failure(s), 0 parse failure(s) [app ] Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /data/logs/letsencrypt.log or re-run Certbot with -v for more details. [app ] [3/18/2026] [5:22:21 PM] [SSL ] › ℹ info Completed SSL cert renew process Even with these errors, it appears nginx is working okay, have only tested a few containers but all are configured in the same manner with a CF origin cert.

Having the exact same issues as the users above & also using Cloudflare. Was working prior to update and no configuration changes prior or post updating the container. Unable to do any real troubleshooting until I get back from work later today.

I have this exact same issue, Resolved it by running: docker exec -it nextcloud occ upgrade Once this had completed I could continue with the guide.

If you are also running too many in parallel can slow down the plotting process. A 1tb ssd can do about 3 in parallel (4 if you time it right) if you have the RAM to accompany it. This is providing you are using the drive solely for plotting.

Yeah if you restart the container you will lose what you have currently done. Phase 1 & phase 3 take the longest time, the others are quicker. Nothing will be written to the array until the very end. Everything prior is reading/writing to the SSD. Is your cpu doing anything else intensive? As that can really slow down the process. Sent from my GM1913 using Tapatalk

Are you guys are giving it enough time to complete the plotting process? A k32 plot can be done by one expert we know in just under 4 hours, but most experts are creating plots in 5 hours and most folks average around 9-12 hours. https://www.chia.net/2021/02/22/plotting-basics.html Sent from my GM1913 using Tapatalk

You can use the command below to show your mnemonic phrase. docker exec -it chia venv/bin/chia keys show --show-mnemonic-seed

This is normally caused by the container still having an active network connection. Usually caused by not stopping a container before removal. docker network disconnect <network name> <container name> That command should kill any active connections. Sent from my GM1913 using Tapatalk

Can you post the output please? Also from memory, I think that the wallet needs to be fully synced with the chia network before it displays anything. Sent from my GM1913 using Tapatalk

Needs to be the other way round. Plotting is your temporary storage, which should be your ssd & your plots are where the final files are stored, this is for your HDD. This command will show you your wallet. docker exec -it chia venv/bin/chia wallet show Sent from my GM1913 using Tapatalk

This is how I monitor my farm. If you guys install the nerd pack from community applications, then navigate to nerd pack under settings, install tmux. Now launch the unraid terminal & run tmux, then you can have multiple (tabbed) terminal windows in one window. I have 1 tab per plot & can jump around them as needed. Also you can close the terminal window & relaunch your session by running tmux again from the terminal. Also works across different devices or applications, so you can ssh in from your phone or putty etc & just run tmux again & you will be able to see those other terminal windows. Hope this helps.

I managed to get mine working again by hashing out those values from your log & replacing the first one with the tls.skip_verify value below & adding true or false depending on your setup. #trusted_cert: "" #disable_verify_cert: tls.skip_verify: Hope this helps