I just try to get Let's Encrypt running (with no success at the moment) and then I realize I don't get any log file to do debugging. What's wrong? I recreated the file in the path /var/log/acme.sh.log
Is there any permission issue?
I don%u2019t know why, but now it seems to work again. Sorry.
How do I change the status to solved?
I just ran into this issue recently. Did you end up just recreating the log file with root and chmod it 600?
Some reason acme won't generate any log file when running. It's so strange.
is issue/renewal required for any certificate?
if its not - look for " issue/renewal not required" in system log
Hi,
first post here after using OPNSense for 6 months. :) Many thanks to you for having created OPNSense!!
I have the same issue as described previously: the web GUI gives File /var/log/acme.sh.log doesn't exist.
This machine is a real machine create by using backup/restore from a virtual machine.
/var/log/acme.sh.log was present into the virtual machine.
Creating/renewing certs works (if all things are correct!) but doesn't generate the log file => in case of issues it is difficult to solve.....
=> what can I do? Create an empty file? Which permissions? Uninstall the plugin and reinstall it? Is it possible to delete completely the conf of the plugin?
Thanks.
Arnaud
maybe an explanation of the maintainer would be helpful
https://github.com/opnsense/plugins/issues/1948
Hi Fright,
and many thanks for the quick answer.
The link helped me:
- after remaking the setup step by step and selecting "staging environment" I get the logs by renewing the cert
- after selecting "production environment" and renewing the cert, there is no new log (with "normal" and "extended" log level) while the the cert has been renewed
- System: Log Files: General and search for "AcmeClient" shows the missing logs
=> the logs are not added any more to /var/log/acme.sh.log by switching from "staging environment" to "production environment".
I use http-01 as challenge-typ
As a newbie with OPNSense, I would quietly say that this seems to be a (small) bug.... :-[
Bye
Arnaud
QuoteI get the logs by renewing the cert
so now there is records in Services: Let's Encrypt: Log File?
Quotethe logs are not added any more to /var/log/acme.sh.log
fresh records appear only if the acme.sh is launched. that is, if actions are performed with a certificate or account using this script. if the certificate is checked and does not require action, then there will be no fresh entries in this log
Quote from: Fright on February 03, 2021, 08:21:36 AM
QuoteI get the logs by renewing the cert
so now there is records in Services: Let's Encrypt: Log File?
yes file exists now and contains the log messages
Quote from: Fright on February 03, 2021, 08:21:36 AM
Quotethe logs are not added any more to /var/log/acme.sh.log
fresh records appear only if the acme.sh is launched. that is, if actions are performed with a certificate or account using this script. if the certificate is checked and does not require action, then there will be no fresh entries in this log
yes, I understand this (I hope!). But forcing the renewing of the cert uses acme.sh, doesn't it?
Looking at the date and time of "issue/renewal date" and "Last acme run" I see that the cert is really renewed.
Under the staging environment this produces logs into /var/log/acme.sh.log, under the production environment logs aren't produced any more => is this normal?
Quoteunder the production environment logs aren't produced any more => is this normal?
dont think so.
you can try to del acme.sh.log, change log level to debug at "Services: Let's Encrypt: Settings", force cert renew, go to "System: Log Files: General" and search for "running acme.sh command". there should be record like "AcmeClient: running acme.sh command: /usr/local/sbin/acme.sh --issue --debug". If it is and acme.sh.log does not contain new entries, then something is definitely wrong.
Hi,
I made the test: "System: Log Files: General" shows AcmeClient: running acme.sh command: /usr/local/sbin/acme.sh --issue --debug --webroot /var/etc/acme-client/challenges etc.....
and no logs into "Services: Let's Encrypt: Log File": File /var/log/acme.sh.log yielded no results.
=>there is a problem.
... and now? How get it fixed?
Do you have the right place to report this?
Hi
i think that https://github.com/opnsense/plugins/issues is ther right place for this ticket
https://github.com/opnsense/plugins/issues/2227
maintainer has already fixed this bug (opnsense-patch -c plugins 3a029db4)