• HEADS UP: Let's Encrypt ACMEv1 server EOL starting

    1
    0 Votes
    1 Posts
    593 Views
    No one has replied
  • [Solved] Add additional IPs or Hostnames

    8
    0 Votes
    8 Posts
    1k Views
    GertjanG

    See, for example, this forum, first post.
    Also, check out the https://letsencrypt.org/fr/ site.

  • Pfsense + acme plugin + route53 (dynamic dns) fails

    3
    0 Votes
    3 Posts
    1k Views
    R

    CodenSnap, (I now this is an old thread but in case this might help others)

    I'm working on a similar setup (domain registered with Google and hosting DNS with either CloudFlare or AWS Route53). In domain.google.com there is an option to switch your DNS to "manual". Once switched to manual you have the option to entered to DNS servers for for your domain. I can enter either Route53 or ClouldFlare. In either service I then add my DNS instance and create my Zone. From there I was able to use Dynamic DNS, add A, AAAA, & TXT, records ,etc, with either DNS provider. Have not yet got the ACME client to work. But best-I-can-tell there is no negative with registering a domain with Google and then hosting your DNS with another provider.

    Best Regards,
    RKGraves

  • FYI - ACME on 2.3.x

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • ACME Cert webConfigurator conflicting with OpenVPN CA?

    6
    0 Votes
    6 Posts
    768 Views
    R

    @Derelict
    Yes, working to use DNS Validation w/CloudFlare for ACME client.

    Thanks for the linked Video - Very Helpful (I've worked through it twice) and I believe I am close to getting ACME to work with CloudFlare. In the Video he uses a different DNS host for validation.

    Appreciate the link and your reply.

    RKGraves

  • ACME 0.6.3 Changing domain key size on existing entry (renew)

    1
    0 Votes
    1 Posts
    587 Views
    No one has replied
  • 0 Votes
    1 Posts
    251 Views
    No one has replied
  • ACME with Schlundtech (german provider)

    4
    0 Votes
    4 Posts
    925 Views
    U

    ...meanwhile someone integrated schlundtech into acme.sh and the upstream found it's way into the pfsense acme plug in...

  • loop error while issuing a cert

    2
    0 Votes
    2 Posts
    916 Views
    GertjanG

    @La6er said in loop error while issuing a cert:

    poblacionqxxxxxxtaro.gob.mx

    DNSSEC is not working for your domain : check http://dnsviz.net/d/poblacionqueretaro.gob.mx/dnssec/ or https://dnssec-analyzer.verisignlabs.com/

    Example http://dnsviz.net/d/papy-team.org/dnssec/

    Btw : you are updating against Cloudfare, and using "bind" locally. Why ? Is bind a master name server for your zone ? Slave name server ? I don't understand the relation.

    edit : I looked at your message again.
    You 'bind' is set up as a master for your domain .... but you disallow zone transfers. Wtf ??
    How can a slave sync then ? Do you have just one name server for your domain ? That can't be true, you break everything then, 2 is the minimum.

  • DNS-NSupdate / RFC 2136 Acme 0.6.2

    2
    0 Votes
    2 Posts
    507 Views
    M

    Dear All,

    This is resolved. The cause was a DNS configuration error outside the scope of Acme - sorry. I have had difficulties setting up dnssec. In so doing, I did modify the SOA entry. As a consequence, my slave DNS servers did not track master DNS server changes. Hence, Acme verification had no chance to work.

    Regards,

    Michael Schefczyk

  • Process by which the pfSense ACME plugin is updated

    4
    0 Votes
    4 Posts
    717 Views
    jimpJ

    We have a few changes that I doubt they'd want or accept. It's not a big deal really. Things rarely conflict. I just merge from upstream, copy the files over, and test.

  • LE/Acme Register Account Key Issue.

    7
    0 Votes
    7 Posts
    1k Views
    N

    @Napsterbater So I confirmed via packet caps it was a broken PMTUD issue on the Broken box, seems related to NPt, but that is another story.

    Thanks for the help.

  • Template variables for ACME actions?

    3
    0 Votes
    3 Posts
    750 Views
    J

    @Gertjan said in Template variables for ACME actions?:

    On a firewall ??

    at least not in my case ;-) This pfsense box works as server in my network and not as router/firewall. But fully agree that Cert/Key handling should not take place on a firewall.
    I use acme.sh on my servers for quite a while now. Works like charm, but I like the GUI to manage the LE stuff ;-)

    You could write up a feature request https://redmine.pfsense.org/projects/pfsense/issues?set_filter=1&tracker_id=2

    I opened a feature request: https://redmine.pfsense.org/issues/9725

  • Acme & cPanel/WHM

    3
    0 Votes
    3 Posts
    903 Views
    V

    I've completed my small php script and it seems to work well.
    This is the result in case anyone needs it:

    // -- CONFIG $certname = 'lan.domain.com'; //a registered FQDN in cPanel with acme let's encrypt enabled (wildcard cert) $pfsense_cert_id = 1; // certificate id in pfsense to overwrite. (The correct ID can be found by hovering over an icon in the cert manager or by looking in the config file. $ftp_server = 'ftp.domain.com'; //ftps location to your domain (cpanel). $ftp_user_name = ''; $ftp_user_pass = ''; $server_file = '/.cpanel/nvdata/letsencrypt-cpanel'; //download file used by cPanel holding every certificate (in JSON format). // -- PROGRAM $conn_id = ftp_ssl_connect($ftp_server); $login_result = ftp_login($conn_id, $ftp_user_name, $ftp_user_pass); ftp_pasv($conn_id, true); if (!$login_result) die("can't login"); ob_start(); $dataLoaded = ftp_get($conn_id, "php://output", $server_file, FTP_BINARY); $data = ob_get_contents(); ob_end_clean(); ftp_close($conn_id); if (!$dataLoaded) die("There was a problem downloading the json data from $ftp_server"); $jsonData = json_decode($data, true); $cert = $jsonData['certs'][$certname]; if(empty($cert)) die("Certificate with name $certname not found"); $config['cert'][$pfsense_cert_id ]['prv'] = base64_encode($cert['key']); $config['cert'][$pfsense_cert_id ]['crt'] = base64_encode($cert['cert']); write_config(); exec('/etc/rc.restart_webgui'); //echo 'Certificate:', PHP_EOL, $cert['cert'], PHP_EOL; //echo 'Key:', PHP_EOL, $cert['key'], PHP_EOL; echo 'New certificate for ', $certname, ' is valid untill ', gmdate('r',$cert['cert_expiry']), PHP_EOL; exit;

    I've uploaded the file (named sslupdate) to the /etc/phpshellsessions directory in pfsense and I added the following cron job (through the cron package):

    0 0 1 1/3 * : /usr/local/sbin/pfSsh.php playback sslupdate
  • ACME problem with IDN Domains

    7
    0 Votes
    7 Posts
    2k Views
    jimpJ

    Great! It must have been solved upstream in acme.sh

  • Letsencrypt and acme devepment package version > 0.5.8

    10
    0 Votes
    10 Posts
    572 Views
    R

    I just reverted back from Version "2.5.0.a.20190806.1707 i" to the snapshot using 2.4.4-RELEASE-p3 (amd64) version. I upgraded the acme to version 0.6_1 and tried to issue a certificate with the staging servers of letsencript. Everything works well without no problem at all !!!

    Then i tired a copy of some file to the tmp of PfSense i.e.

    scp test1.txt root@192.168.87.1:/tmp/

    the file got copies and its content to tmp. All good there.

    Now i need to upgrade to 2.5.0.a.20190806.1707 again and see if i will be able to replicate the problem with the file copy.

  • ACME update 0.6.2

    1
    1 Votes
    1 Posts
    500 Views
    No one has replied
  • 0 Votes
    11 Posts
    3k Views
    R

    Im suffering a similar bug but I use the webroot FTP option.

    Manually hit the renew button and I see the certificate is renewed BUT it isnt applied on the HTTPS side of my pfSense.

    2.4.4-RELEASE-p1

    acme security 0.5.8

  • FreeDNS ACME issue

    3
    0 Votes
    3 Posts
    709 Views
    P

    @kiokoman Yeah, you're right =) But anyway, I wasn't able to make some reasonable solution, so I've just created tiny VM guest with alpine linux, lighttpd and nfs-client, and I'm passing my .well-known challenge through "local webroot", but I'm putting there appropiate path for my NFS share + ballast ( </path/to/share>/.well-known/acme-challenge/ ). pfSense comes already preloaded with nfs, all I needed was just enable it through /etc/rc.d.local. HAProxy does rest of the job ( frontend for path match looks like that ---v )

    HAProxy Frontend rules ( I've got it implemented with http->https redirect, except for .well-known =3 I was pretty suprised it came on my mind )

    Spoiler

    HAProxy Frontend rules

    So that's my hotfix solution, but I'm curious for any other ideas ))

  • ACME 0.5.8 Breaks Letencrypt webroot local folder setup

    8
    0 Votes
    8 Posts
    1k Views
    jimpJ

    Let's Encrypt won't publish a list of possible sources as that would let someone game the system to obtain certs for domains they do not own from systems they have compromised in subtle ways (e.g. port forward all LE servers to fakeserver, but let other connections go through to realserver)

    They could reach you from anywhere in the world, there is no way to predict the source. You have to allow connections from anywhere during that timeframe.

    If that bugs you, then switch to a DNS-based method that does not require any inbound access whatsoever.

Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.