SSL Install Error

[mcs3ss2]

Command failed: dehydrated -c. ERROR: Challenge is invalid! (returned: invalid) (result: ["type"]       "http-01"
["url"] "https://acme-v02.api.letsencrypt.org/acme/chall/3503548816/733714411146/Bt0iPQ"
["status"]      "invalid"
["validated"]   "2026-07-05T08:25:44Z"
["error","type"]        "urn:ietf:params:acme:error:unauthorized"
["error","detail"]      "192.18.1.57: Invalid response from http://pbx.mylab.au/.well-known/acme-challenge/qTr256prEeDGHxX4L_F5T86ZA_s_w1yKabCbFDUhiwE: 403"
["error","status"]      403
["error"]       {"type":"urn:ietf:params:acme:error:unauthorized","detail":"192.18.1.57: Invalid response from http://pbx.mylab.au/.well-known/acme-challenge/qTr256prEeDGHxX4L_F5T86ZA_s_w1yKabCbFDUhiwE: 403","status":403}
["token"]       "qTr256prEeDGHxX4L_F5T86ZA_s_w1yKabCbFDUhiwE"
["validationRecord",0,"url"]    "http://pbx.mylab.au/.well-known/acme-challenge/qTr256prEeDGHxX4L_F5T86ZA_s_w1yKabCbFDUhiwE"
["validationRecord",0,"hostname"]       "pbx.mylab.au"
["validationRecord",0,"port"]   "80"
["validationRecord",0,"addressesResolved",0]    "192.18.1.57"
["validationRecord",0,"addressesResolved"]      ["192.18.1.57"]
["validationRecord",0,"addressUsed"]    "192.18.1.57"
["validationRecord",0]  {"url":"http://pbx.mylab.au/.well-known/acme-challenge/qTr256prEeDGHxX4L_F5T86ZA_s_w1yKabCbFDUhiwE","hostname":"pbx.mylab.au","port":"80","addressesResolved":["192.18.1.57"],"addressUsed":"192.18.1.57"}
["validationRecord"]    [{"url":"http://pbx.mylab.au/.well-known/acme-challenge/qTr256prEeDGHxX4L_F5T86ZA_s_w1yKabCbFDUhiwE","hostname":"pbx.mylab.au","port":"80","addressesResolved":["192.18.1.57"],"addressUsed":"192.18.1.57"}])

As per documentation - SSL Installation is not working.
Fresh Debian 13 Install
Latest script to install FSPBX 1.9.3
SSL Install Error. Fresh Install. SIngle Domain. Default Domain is disabled. hostname is resolving to IP.

I can login to NON SSL Page

Can someone help

 

[pbxgeek]

How are you producing this error? Are you running this command?

php artisan app:install-lets-encrypt-certificate

Make sure your nging config has this, and nothing else overrides this block

server {
    listen 80 default_server;
    listen [::]:80 default_server;
    server_name _;

    location ^~ /.well-known/acme-challenge/ {
        default_type "text/plain";
        root /var/www/fspbx/public;
        try_files $uri =404;
    }

    location / {
        return 301 https://$host$request_uri;
    }
}

Ensure that Let's Encrypt servers can reach your server. Recently, someone reported a similar problem, which was caused by their geographical blocking.