http-01 failed

[fffonion]

http-01 failed

[fffonion]

@elvizlai I can't think of a place where 501 is thrown from this library. Maybe check your nginx conf and make sure the route is properly handled by lua-resty-acme not other routes? You can add a different access_log in /.well-known/acme-challenge location block to make sure the request is hitting the correct location block.

[elvizlai]

@elvizlai I can't think of a place where 501 is thrown from this library. Maybe check your nginx conf and make sure the route is properly handled by lua-resty-acme not other routes? You can add a different access_log in /.well-known/acme-challenge location block to make sure the request is hitting the correct location block.

Same config worked a week ago, but now it failed. Maybe Let's encrypt changed?

server {
    listen 80;
    listen 443 ssl http2;

    server_name xxx.yyy.com;

    ssl_certificate     cert/default.crt;
    ssl_certificate_key cert/default.key;

    ssl_stapling off;

    ssl_certificate_by_lua_block {
        require("resty.acme.autossl").ssl_certificate()
    }

    location /.well-known {
        content_by_lua_block {
            require("resty.acme.autossl").serve_http_challenge()
        }
    }

    if ($scheme != "https") {
        return 301 https://$host$request_uri;
    }

    proxy_http_version 1.1;
    proxy_set_header HOST $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

    location / {
        proxy_pass http://172.17.0.1:8090;
    }
}

[elvizlai]

Opps, maybe pagespeed related, I will try to confirm this.

[elvizlai]

Sorry for my mistake, the pagespeed cause that issue.