Let's Encrypt still showing HTTP error

VitalPBX Community Support General Discussion Let's Encrypt still showing HTTP error

Up
0
Down
  • Post
    kbohannon
    Participant

    Upgraded to 2.3.4-2. FQDN always correct. Checked permissions and the log file. Still on this and other servers getting the same error, pic attached. Am I doing something wrong?

    ls -la /usr/share/ombutel/:
    drwxrwsr-x.   3 asterisk apache  4096 Jun 24 17:04 certificates
    drwxr-xr-x. 8 apache apache 4096 Jun 26 21:44 www

    cat log_2019-06-28.log
    [2019-06-28 16:35:32.170933] [info] Account already registered. Continuing.
    [2019-06-28 16:35:32.171309] [info] Starting certificate generation process for domains
    [2019-06-28 16:35:32.172513] [info] Requesting challenge for blah.blahblahblah.net
    [2019-06-28 16:39:05.953844] [info] Sending signed request to /acme/new-authz
    [2019-06-28 16:48:25.747342] [info] Account already registered. Continuing.
    [2019-06-28 16:48:25.747699] [info] Starting certificate generation process for domains
    [2019-06-28 16:48:25.748999] [info] Requesting challenge for blah.blahblahblah.net
    [2019-06-28 16:51:39.341485] [info] Sending signed request to /acme/new-authz

    0
Viewing 1 replies (of 1 total)
  • Replies

    This is a kind of limitation of let’s encrypt. Are you using a DDNS server?

    On another hand, we are currently working to allow to install custom certificates (comodo, Digicert) from the certificates module.

    0
Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.