@raigh29 said in RE error: parentheses not balanced:

error: parentheses not balanced

Related to https://forum.netgate.com/topic/134704/script-error-in-dns-namesilo-method ?

@jimp said in ACME and admins group: not enough permission:

Did you select the "Deny Config Write" privilege for your custom group? Sounds like that's what you did.

Thanks yours point directly answered to my problem. Removing deny permission fixed my problem.
There is plans to add pfSense WebGUI exception for inform about not enough permissions?

@Gertjan thanks, very appriciated...

Hit the Renew button yourself right now. You'll see.
You are allowed to renew yourself, like 5 times a week.

@Gertjan I really did miss that!

@Peek said in Let's Encrypt & ACME:

_acme-challenge.pfsense.domain.com

What about asking for a wildcard cert for root "domain.com" ?
Using
domain.com
and
*.domain.com
(twice) as "Domainname".

You can use pfsense.domain.com, another.domain.com and something-else.domain.com, they will all 'work'.

edit : btw :
_acme-challenge.pfsense.domain.com
is a sub domain do shouldn't exist already. It's just a 'random' place holder, so the acme check server can test for a TXT filed in "_acme-challenge.pfsense.domain.com" - which should contain the "VTTcvhklvFWaDrbJc" phrase. This proves that you control the domain "domain.com", thus the certificate can be handed over to you.

If you update to the latest ACME package posted today, you will see the tabs with other users who have access to that package.

Upgrade to the latest ACME package.

I have the same issue. Any progress on this topic?

Thanks.
It works now with redirect of port 80 and I found "Restart Remote Service".

I spoke to the script author regarding this issue and it has now been resolved. There is also a pull request https://github.com/Neilpang/acme.sh/pull/1807

Issue resolved.

Works great now.

Thanks!

I fixed the text and added some links to the rate limit pages. Thanks!

@jimp, that solved it. Thanks for the quick solution.

Strange that a test cert with Buypass explicitly mentioned not being in the supported 'prime256 ' after creating a 256bit curve setting then 🤔
I have to test again it seems!