• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Please explain ACME cert update method

Scheduled Pinned Locked Moved ACME
1 Posts 1 Posters 198 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F
    finite9
    last edited by Feb 7, 2023, 12:51 PM

    Hi,

    I wanted a Let's Encrypt cert for my pfSense router... something that I could eventually re-use (using HAProxy?) for my web server on a PC on the LAN.

    I had trouble generating the cert but I found this guide on YT:

    link text

    And it works great, but it seems like it doesn't use pfSense recommended validation method of DNS. I had to choose a new webgui port instead of 80, turn off the webgui redirect, open a fw rule for port 80 to the pfsense router, and I can only access the webgui now using my external domain name even if im on the LAN (where the LE cert works). Trying to access the webgui using hostname.domainname fails now.

    So, it works, but it seems like if I could get it working using the DNS method instead of HTTP standalone server, then I could go back to using more default settings.

    The problem is that I have no idea what the DNS method is trying to do! I have my own domain name that i've got from nsupdate.info (a free version of the old DynDNS service that started charging for the service).

    Am I supposed to enter my nsupdate.info credentials in the cert "validation method"? Am I correct in assuming it's the DNS-nsupdate method I need to choose? I do not understand the mapping between "server", "key", "key algo" and the "update URL" that I use to update my IP address using the DynDNS service towards nsupdate.info.

    1 Reply Last reply Reply Quote 0
    1 out of 1
    • First post
      1/1
      Last post
    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
      This community forum collects and processes your personal information.
      consent.not_received