jay gardner

evidently, my renewal has not been working (domain my.domain.com is a sanitized placeholder). it started trying to renew 4 weeks ago - here's what is recorded via my logging -...

here's result with --debug & --dnssleep added: [log](https://pastebin.com/aUiL9dBT) full command line: `/root/.acme.sh/acme.sh --cron --debug --home /root/.acme.sh --dnssleep >> /root/.acme.sh/acme.logger 2>&1` domain sanitized to `subdomain.my.domain.com` csr text sanitized to my `my-csr-text`...

ok, this is apparently not a dns api issue - i changed the --server option to letsencrypt and issued a new cert - and it works fine... something must be...

I see, apologies for my misunderstanding of the purpose of this thread, and thanks for your reply/suggestions.

you might try a different CA - i was having similar issues today (and evidently for the last 4 weeks my renewal continually failed). My error was similar, but timeouts...

I had the same problem - but discovered that it was due to spaces vs tabs. make sure your edl file is using tabs between the entries on each line

@fdrfaure - you need to format the QEMU disk you created as MyDisk.qcow2. From that menu choose option 4, and when disk utility opens, select Erase, and select the QEMU...

If you are running find3 server locally via native install (ie, not docker), yes. I just set this up. When you launch the main server component, you can simply specify...

@schollz - in preior version of find there was an option (-mosquitto) to pass the PID # to find when starting find. when i run ./main --help i don't see...

i never really understood the use of the PID previously as it seemed like it was intended for use with a separate mosquitto instance associated with FIND. but the only...