Let's Encrypt from the GUI still not working for me

› VitalPBX Community Support › General Discussion › Let's Encrypt from the GUI still not working for me

Up
0
Down
  • Post
    • May 16, 2019 at 2:38 pm
    Up
    0
    Down
    kbohannon
    Participant

    755 on /usr/share/ombutel/www and apache owns /certificate/ and /www/. I have even whitelisted the IPs for outbound1 and oubtound2.letsencrypt.org. /var/log/log* shows little.

    Eventually the GUI presents an error:

    Exception: HTTP Challenge for milieu.xxxxxx.net is not available. Whole response:

    {“type”:urn:acme:error:unauthorized”,”Detail”:”No registration exists matching provided key”,”status”:403} at file /usr/share/ombutel/www/modules/certificates/certificates.php on line 0

     

    The only other thing different is that I do a fresh install of the latest version, and then clone the existing drive from that VPS to others, then continue the configuration. Should this make a difference?

    0
Viewing 6 replies - 1 through 6 (of 6 total)
  • Replies
    • May 16, 2019 at 5:40 pm
    Up
    0
    Down
    Jose Miguel Rivera
    Keymaster
    NI

    Try the following:

    • chown apache:apache -R /usr/share/ombutel/certificates
    • chown apache:apache /usr/share/ombutel/www

    Both folders must have 755 as permission

     

    0
    • May 21, 2019 at 1:01 pm
    Up
    0
    Down
    kbohannon
    Participant

    Still nothing, on several installs. It worked fairly well a few weeks ago, so I am wondering if I am hitting up against some limit with LE, though I can’t imagine how. Sometimes I get the error, but with new installs it just sits there and nothing happens, and the log file doesn’t reveal much.

    is it possible to add in our own Comodo certs instead? I had hoped to avoid getting another wildcard by using VPBX but I’ve now got several instances giving clients browser alerts.

    0
    • May 21, 2019 at 9:13 pm
    Up
    0
    Down
    Jose Miguel Rivera
    Keymaster
    NI

    We will add the possibility to add custom certificates for next version

    0
    • May 23, 2019 at 1:34 pm
    Up
    0
    Down
    toxicfusion
    Participant

    I had success by manually using LetsEncrypt (as I use non standard port 80).  Just have to sym link the letsencrypt cert to proper cert directory specified in the httpd.conf,

     

    0
    • May 23, 2019 at 1:46 pm
    Up
    0
    Down
    kbohannon
    Participant

    Could you elaborate? My CLI skills are still at a beginner stage.

    0
    • June 12, 2019 at 11:18 pm
    Up
    0
    Down
    Jose Miguel Rivera
    Keymaster
    NI

    We have added some fixes on certificates, please check the latest version of VitalPBX

    0
Viewing 6 replies - 1 through 6 (of 6 total)

Tagged: 

  • You must be logged in to reply to this topic.