Getting urn:ietf:params:acme:error:unauthorized error while creating new certificate

Help
149

Just some clarity. Do you mean there is no redirect at all? Not even from HTTP to HTTPS?

The rest is very promising ! I think someone already suggested this but you could manually remove everything but the most basic from the port 443 server block for site209. Even extra blank lines. See if that works. If so, slowly add things back in and see what breaks it.

You could start with just this for example

server {
    server_name "hummingbird-flowers.floristtouch.com" "www.hummingbird-flowers.floristtouch.com";

    access_log  /var/www/sites/site209/log/access.log main;
    error_log   /var/www/sites/site209/log/error.log error;

    root  "/var/www/sites/site209/public";

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/hummingbird-flowers.floristtouch.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/hummingbird-flowers.floristtouch.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}

I know you tried recreating site209 from site100 once. But, try it from a different angle by starting from scratch. Hopefully it won't be something so simple as a stray non-printable character somewhere.

I'm not so sure about that. If a reload does not create new pids and nginx -t does not report an error, then nginx -t could use some improvement at least :slight_smile:

That's assuming some syntactical error is causing the reload problem. Looks promising though.

I agree though your nginx behaves normally until the rogue site configs so that makes a lot more sense.

1 Like