I just set up my 3rd TN server. I’ve had no issues using the built in tools on the other 2 in order to set up and use LE SSL certs. On this 3rd server when I click save on the CSR I get a box that pops up for about 1/10th second, then goes away. All my settings look correct. What log would I check to try and track down the issue?
I just tried creating a CSR on my 25.04.1 and didn’t have any problems. There are multiple profiles and options to choose from, I used all the defaults. Perhaps your issue is due to a particular option you’ve chosen?
I created a new API token on Cloudflare with zone read and dns edit properties:
Then I made a new csr with standard options set:
Then I tried to get a cert:
I tried with production a few times, then switched to staging as I didn’t want to blow out my requests depending one what’s going on.
Is there a log I can search that may have a clue as to what’s going on?
You should never paint over your secrets like that. Chars can be guessed by their visible parts and width. I suggest you revoke this token.
Still looking for information that might help me solve the problem. Like log files or similar.
I hadn’t use the built-in truenas mechanism for cert issuing (because it doesn’t have my dns provider). However, the staging directory on this screen
seems kinda strange. Or did you choose it on purpose for preventing limit exhaustion?
I don’t know the exact path, but you can try to find them with something like sudo find /var/ -type d -name 'letsencrypt'.
That would have been nice, but no results.
Didn’t pay enough attention – my bad.
I’m almost out of ideas. Mb you should try to issue it from another browser or with porn incognito/inprivate mode. You can also look for the errors during cert issue inside the browser’s devtools, as a 1/10th second popup doesn’t sound fine.
In terms of places to look for errors, /var/log/messages and /var/log/syslog are always good places to start.
Try also /var/log/middlewared.log
Nothing in any of those logs. I’m guessing that it’s failing before it even has a chance to log anything.
You might want to try submitting a bug report through the GUI and attaching a debug file–maybe the iX crew can figure out where it’s failing.