Can't renew certificate with nginx

My domain is: cloud.chaoten-ban.de

I ran this command: certbot renew

It produced this output:

Domain: cloud.chaoten-ban.de
Type:   unauthorized
Detail: Invalid response from
https://cloud.chaoten-ban.de/.well-known/acme-challenge/EMwDkUCZXllwyyrExohwvzIT6BZdpuPp_INI8GEHK 
[173.249.45.139]: "<html>\r\n<head><title>403
Forbidden</title></head>\r\n<body 
bgcolor=\"white\">\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>"

My web server is (include version): nginx/1.14.0 (Ubuntu)

The operating system my web server runs on is (include version): Ubuntu 18.04

My hosting provider, if applicable, is: Contabo

I can login to a root shell on my machine (yes or no, or I don’t know): yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.31.0

Hello,

since some weeks I got this error an I can’t find the reason. I’m guessing that the problem is in the nginx-sites-config, but i have no clue, what causes the problem.
There are other subdomains on the same server, which are working perfectly.

Here is my config:

upstream php-handler {
#server 127.0.0.1:9000;
server unix:/run/php/php7.1-fpm.sock;
}

server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name cloud.chaoten-ban.de;

ssl_certificate /etc/letsencrypt/live/cloud.chaoten-ban.de/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/cloud.chaoten-ban.de/privkey.pem;


ssl_session_timeout 5m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # omit SSLv3 because of POODLE
ssl_ciphers 'ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA';
ssl_prefer_server_ciphers on;

# Add headers to serve security related headers
# Before enabling Strict-Transport-Security headers please read into this
# topic first.
add_header Strict-Transport-Security "max-age=15552000; includeSubDomains; preload;" always;
#
# WARNING: Only add the preload option once you read about
# the consequences in https://hstspreload.org/. This option
# will add the domain to a hardcoded list that is shipped
# in all major browsers and getting removed from this list
# could take several months.
add_header X-Content-Type-Options nosniff;
add_header X-XSS-Protection "1; mode=block";
add_header X-Robots-Tag none;
add_header X-Download-Options noopen;
add_header X-Permitted-Cross-Domain-Policies none;
add_header Referrer-Policy "no-referrer" always;

# Path to the root of your installation
root /var/www/nextcloud;
    
location = /robots.txt {
     allow all;
    log_not_found off;
    access_log off;
}

# The following 2 rules are only needed for the user_webfinger app.
# Uncomment it if you're planning to use this app.
#rewrite ^/.well-known/host-meta /public.php?service=host-meta last;
#rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json
# last;

location = /.well-known {
 allow all;
 auth_basic off;
 alias //cloud.chaoten-ban.de/.well-known/;
}

location = /.well-known/carddav {
  return 301 $scheme://$host/remote.php/dav;
}
location = /.well-known/caldav {
  return 301 $scheme://$host/remote.php/dav;
}

# set max upload size
client_max_body_size 2048M;
fastcgi_buffers 64 4K;

# Enable gzip but do not remove ETag headers
gzip on;
gzip_vary on;
gzip_comp_level 4;
gzip_min_length 256;
gzip_proxied expired no-cache no-store private no_last_modified no_etag auth;
gzip_types application/atom+xml application/javascript application/json application/ld+json application/manifest+json application/rss+xml application/vnd.geo+json application/vnd.ms-fontobject application/x-font-ttf application/x-we$

# Uncomment if your server is built with the ngx_pagespeed module
# This module is currently not supported.
#pagespeed off;

location / {
    rewrite ^ /index.php$uri;
}

location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)/ {
    deny all;
}
location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console) {
    deny all;
}

location ~ ^/(?:index|remote|public|cron|core/ajax/update|status|ocs/v[12]|updater/.+|ocs-provider/.+)\.php(?:$|/) {
    fastcgi_split_path_info ^(.+\.php)(/.*)$;
    include fastcgi_params;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    fastcgi_param PATH_INFO $fastcgi_path_info;
    fastcgi_param HTTPS on;
    #Avoid sending the security headers twice
    fastcgi_param modHeadersAvailable true;
    fastcgi_param front_controller_active true;
    fastcgi_pass php-handler;
    fastcgi_intercept_errors on;
    fastcgi_request_buffering off;
}

location ~ ^/(?:updater|ocs-provider)(?:$|/) {
    try_files $uri/ =404;
    index index.php;
}

# Adding the cache control header for js and css files
# Make sure it is BELOW the PHP block
location ~ \.(?:css|js|woff|svg|gif)$ {
    try_files $uri /index.php$uri$is_args$args;
    add_header Cache-Control "public, max-age=15778463";
    # Add headers to serve security related headers (It is intended to
    # have those duplicated to the ones above)
    # Before enabling Strict-Transport-Security headers please read into
    # this topic first.
    add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;";
    #
    # WARNING: Only add the preload option once you read about
    # the consequences in https://hstspreload.org/. This option
    # will add the domain to a hardcoded list that is shipped
    # in all major browsers and getting removed from this list
    # could take several months.
    add_header X-Content-Type-Options nosniff;
    add_header X-XSS-Protection "1; mode=block";
    add_header X-Robots-Tag none;
    add_header X-Download-Options noopen;
    add_header X-Permitted-Cross-Domain-Policies none;
    add_header Referrer-Policy "no-referrer" always;
    # Optional: Don't log access to assets
    access_log off;
}

location ~ \.(?:png|html|ttf|ico|jpg|jpeg)$ {
    try_files $uri /index.php$uri$is_args$args;
    # Optional: Don't log access to other assets
    access_log off;
}
}

The error.log says:

2019/05/09 10:04:04 [error] 32428#32428: *29 access forbidden by rule, client: 85.215.2.229, server: cloud.chaoten-ban.de, request: "GET /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de HTTP/1.1", host: "cloud.chaoten-ban.de"

Do you have any idea, how I can solve this problem?

Thanx in advance.

Matthias

Hi @mtisat

there is a check of your domain ( https://check-your-website.server-daten.de/?q=cloud.chaoten-ban.de ):

That looks ok, port 80 is open, there is a redirect http -> https.

Your root:

Create the two subdirectories

/var/www/nextcloud/.well-known/acme-challenge

there a file (file name 1234), then try to load that file via

http://cloud.chaoten-ban.de/.well-known/acme-challenge/1234

If that works, then use it:

certbot run -a webroot -i nginx -w /var/www/nextcloud -d cloud.chaoten-ban.de

PS: Sorry, there is an error visible, should post the complete output:

Domainname Http-Status redirect Sec. G
http://cloud.chaoten-ban.de/
173.249.45.139 301 https://cloud.chaoten-ban.de/ 0.067 A
https://cloud.chaoten-ban.de/
173.249.45.139 302 https://cloud.chaoten-ban.de/login 1.630 N
Certificate error: RemoteCertificateChainErrors
https://cloud.chaoten-ban.de/login 200 0.840 N
Certificate error: RemoteCertificateChainErrors
http://cloud.chaoten-ban.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
173.249.45.139 301 https://cloud.chaoten-ban.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 0.070 A
Visible Content: 301 Moved Permanently nginx
https://cloud.chaoten-ban.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 403 0.256 N
Forbidden
Certificate error: RemoteCertificateChainErrors
Visible Content: 403 Forbidden nginx

There is the same http status 403 - Forbidden, instead of the expected result http status 404 - Not Found.

So create the two subdirectories, then add a 755 (with chmod) permission to that subdirectory.

Hi JuergenAuer,

thank you for your quick answer.

I already created the 2 subdirectories and put that file there. Now I correctet the permissions and the ownership of the directories and the file. But i still get the 403.

The error.log says:

2019/05/09 11:40:27 [error] 8191#8191: *1 access forbidden by rule, client: 193.175.232.77, server: cloud.chaoten-ban.de, request: "GET /.well-known/acme-challenge/1234 HTTP/2.0", host: "cloud.chaoten-ban.de"

The redirect to https:\ is for all subdomains and since the others work I don’t think this is the problem.

I don't understand that rule.

Such permission things -> wrong location definitions with wrong regex (catching too much).

So deactivate some of your rules to check, if there is a different answer.

PS: To check: This GET

https://cloud.chaoten-ban.de/.well-known/acme-challenge/1234

must send a http status 404 - Not Found.

Not a 403 - Forbidden.

After disabling

location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console) {
deny all; 
}

the command

certbot certonly -a webroot -w /var/www/nextcloud -d cloud.chaoten-ban.de

gave me a new certificate.

Thanx a million for your help.

1 Like

Uh, yes - that blocks every request, if the path starts with .well-known.

Happy to read that it works now!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.