Challenge failed for domain

Help
1

I followed this tutorial and everything worked fine until Step 4 : Obtaining an SSL Certificate

PS : When I go to :
http://captiveportal.secureinside.be:81/ and http://www.captiveportal.secureinside.be:81/

Both work.

My ServerName : www.captiveportal.secureinside.be:81
My ServerAlias : captiveportal.secureinside.be:81

My domain is: captiveportal.secureinside.be

I ran this command: sudo certbot --apache

It produced this output:

Enabled Apache rewrite module
Challenge failed for domain www.captiveportal.secureinside.be
http-01 challenge for www.captiveportal.secureinside.be
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: www.captiveportal.secureinside.be
Type: unauthorized
Detail: Invalid response from
https://www.captiveportal.secureinside.be/.well-known/acme-challenge/T79raHDBfLJgw6s-yHvr57FTvayU1sgtS55tjyTlmag
[109.88.89.61]: "\r\n404 Not Found\r\n<body bgcolor="white">\r\n

404 Not Found

\r\n
"

To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address.

My web server is (include version):

The operating system my web server runs on is (include version): ubuntu 20.04

My hosting provider, if applicable, is: OVH

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):

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

1 Like
2

Hi @Courage

port 80 is required. Port 81 is completely unrelevant.

So your setup can't work.

2 Likes
3

This won't work because you have nginx listening on port 80 and Apache listening on port 81.

Port 81 is not a suitable port to perform domain validation over.

What you might be able to do is use nginx to obtain the certificate, and then configure Apache to actually use the certificate:

sudo certbot certonly --nginx -d captiveportal.secureinside.be \
-d www.captiveportal.secureinside.be --deploy-hook "service apache2 reload"

or some other creative way to solve the problem :slight_smile: .

2 Likes
4

@_az

Do you prefer this:

over this:

apachectl -k graceful

Just curious if there's a tangible delta.

1 Like
5

Hi @Courage and welcome to the LE community forum :slight_smile:

What changed on (or leading up to) Sept. 4?
If it worked previously, then how was it working?

Are both port 80 and port 81 reaching the same end system? [are there more than one system needing a cert]

2 Likes
6

This is what I get when I try it without the :81

[Album] After removing :81

And when i put the :81 my index.html page appears :

image
image1180Ă—192 13.2 KB

On my LAN I have 2 web servers and the one of them is using port 80 and the other is using the port 81.

Can I make a certification with this configuration ?

Thank you in advance!

1 Like
7

Please read required basics:

and

You have to use dns validation with your 81 - domain.

1 Like
8
2 Likes
9

Yes, they are reaching the same end system, the 2 web servers have certificates but have different subdomains that are pointing to the same IP.

1 Like
10

When I use the command it gives me this output :

Saving debug log to /var/log/letsencrypt/letsencrypt.log 
Could not choose appropriate plugin: The requested nginx plugin does not appear to be installed
The requested nginx plugin does not appear to be installed
1 Like
11

Then you don't really have much of a problem.
You can:

  • use SNI to serve the names directly from just one IP:port (NGINX)
  • use a reverse proxy in NGINX to access the Apache

In either case, you can obtain certs via HTTP port 80 (NGINX) [even if you don't use SNI nor a reverse proxy]. By simply using certbot with --webroot.

2 Likes
12

For clarity to anyone following along:

curl -Iki captiveportal.secureinside.be:80
HTTP/1.1 301 Moved Permanently
Server: nginx/1.14.0 (Ubuntu)

Summary

Date: Fri, 26 Feb 2021 11:46:16 GMT
Content-Type: text/html
Content-Length: 194
Connection: keep-alive
Location: https://captiveportal.secureinside.be/

curl -Iki captiveportal.secureinside.be:81
HTTP/1.1 200 OK
Date: Fri, 26 Feb 2021 11:46:18 GMT
Server: Apache/2.4.41 (Ubuntu)

Summary

Last-Modified: Fri, 26 Feb 2021 10:54:23 GMT
ETag: "d5-5bc3b1747a664"
Accept-Ranges: bytes
Content-Length: 213
Vary: Accept-Encoding
Content-Type: text/html

2 Likes
13

I just tried it by using this command :

sudo certbot certonly --webroot --agree-tos --email zlatko@secureinside.be -d captiveportal.secureinside.be -w /var/www/captiveportal.secureinside.be/

It shows this output :

Challenge failed for domain captiveportal.secureinside.be
http-01 challenge for captiveportal.secureinside.be
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

I apologize in advance for any ignorance of my part I just started working on this a couple of days and it's been really difficult to wrap my head around it.

2 Likes
14

Try it this way:

sudo certbot certonly --webroot -w /var/www/captiveportal.secureinside.be/ -d captiveportal.secureinside.be --agree-tos --email zlatko@secureinside.be

It can be confusing...
Sometimes people think they have to get the cert where they will use the cert.
But the two are completely separate things.

2 Likes
15

It gives me the same error :confused:

Challenge failed for domain captiveportal.secureinside.be
http-01 challenge for captiveportal.secureinside.be
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: captiveportal.secureinside.be
   Type:   unauthorized
   Detail: Invalid response from
   https://captiveportal.secureinside.be/.well-known/acme-challenge/ezMrzE1-7gfwbFhZv-5Z2bKqTQwon1z03pwEHlGa0Mw
   [109.88.89.61]: "<html>\r\n<head><title>404 Not
   Found</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>404
   Not Found</h1></center>\r\n<hr><center>"

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A/AAAA record(s) for that domain
   contain(s) the right IP address.
1 Like
16

OK we have to:
adjust your nginx config to allow access to that path via that name
OR
adjust that webroot path to match the default path used when nginx can't match the name

[the second choice is much simpler and faster]

Let me know which one you would like help with [if any is needed].

2 Likes
17

The second one, thanks ! :slight_smile:

2 Likes
18

We will need to see the nginx HTTPS server blocks.
Likely files found in one of these folders
/etc/nginx/conf.d/
/etc/nginx/sites-enabled/

OR

Just show the entire nginx config [if not too long] with:
nginx -T
OR
sudo nginx -T

In all cases, be sure to format the posted configs with three preceding backticks ``` and three afterwards.
Like:

```
post
your
config
```

note: the backtick is generally found [on US styled keyboards] on the left side above the TAB key.

2 Likes
19

Output for sudo nginx -T :


# configuration file /etc/nginx/nginx.conf:
user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;

events {
        worker_connections 768;
        # multi_accept on;
}

http {

        ##
        # Basic Settings
        ##

        sendfile on;
        tcp_nopush on;
        tcp_nodelay on;
        keepalive_timeout 65;
        types_hash_max_size 2048;
        # server_tokens off;

        # server_names_hash_bucket_size 64;
        # server_name_in_redirect off;

        include /etc/nginx/mime.types;
        default_type application/octet-stream;

        ##
        # SSL Settings
        ##

        ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; # Dropping SSLv3, ref: POODLE
        ssl_prefer_server_ciphers on;

        ##
        # Logging Settings
        ##

        access_log /var/log/nginx/access.log;
        error_log /var/log/nginx/error.log;

        ##
        # Gzip Settings
        ##

        gzip on;

        # gzip_vary on;
        # gzip_proxied any;
        # gzip_comp_level 6;
        # gzip_buffers 16 8k;
        # gzip_http_version 1.1;
        # gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

        ##
        # Virtual Host Configs
        ##

        include /etc/nginx/conf.d/*.conf;
        include /etc/nginx/sites-enabled/*;
}


#mail {
#       # See sample authentication script at:
#       # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
#       # auth_http localhost/auth.php;
#       # pop3_capabilities "TOP" "USER";
#       # imap_capabilities "IMAP4rev1" "UIDPLUS";
#
#       server {
#               listen     localhost:110;
#               protocol   pop3;
#               proxy      on;
#       }
#
#       server {
#               listen     localhost:143;
#               protocol   imap;
#               proxy      on;
#       }
#}

# configuration file /etc/nginx/modules-enabled/50-mod-http-image-filter.conf:
load_module modules/ngx_http_image_filter_module.so;

# configuration file /etc/nginx/modules-enabled/50-mod-http-xslt-filter.conf:
load_module modules/ngx_http_xslt_filter_module.so;

# configuration file /etc/nginx/modules-enabled/50-mod-mail.conf:
load_module modules/ngx_mail_module.so;

# configuration file /etc/nginx/modules-enabled/50-mod-stream.conf:
load_module modules/ngx_stream_module.so;

# configuration file /etc/nginx/mime.types:

types {
    text/html                             html htm shtml;
    text/css                              css;
    text/xml                              xml;
    image/gif                             gif;
    image/jpeg                            jpeg jpg;
    application/javascript                js;
    application/atom+xml                  atom;
    application/rss+xml                   rss;

    text/mathml                           mml;
    text/plain                            txt;
    text/vnd.sun.j2me.app-descriptor      jad;
    text/vnd.wap.wml                      wml;
    text/x-component                      htc;

    image/png                             png;
    image/tiff                            tif tiff;
    image/vnd.wap.wbmp                    wbmp;
    image/x-icon                          ico;
    image/x-jng                           jng;
    image/x-ms-bmp                        bmp;
    image/svg+xml                         svg svgz;
    image/webp                            webp;

    application/font-woff                 woff;
    application/java-archive              jar war ear;
    application/json                      json;
    application/mac-binhex40              hqx;
    application/msword                    doc;
    application/pdf                       pdf;
    application/postscript                ps eps ai;
    application/rtf                       rtf;
    application/vnd.apple.mpegurl         m3u8;
    application/vnd.ms-excel              xls;
    application/vnd.ms-fontobject         eot;
    application/vnd.ms-powerpoint         ppt;
    application/vnd.wap.wmlc              wmlc;
    application/vnd.google-earth.kml+xml  kml;
    application/vnd.google-earth.kmz      kmz;
    application/x-7z-compressed           7z;
    application/x-cocoa                   cco;
    application/x-java-archive-diff       jardiff;
    application/x-java-jnlp-file          jnlp;
    application/x-makeself                run;
    application/x-perl                    pl pm;
    application/x-pilot                   prc pdb;
    application/x-rar-compressed          rar;
    application/x-redhat-package-manager  rpm;
    application/x-sea                     sea;
    application/x-shockwave-flash         swf;
    application/x-stuffit                 sit;
    application/x-tcl                     tcl tk;
    application/x-x509-ca-cert            der pem crt;
    application/x-xpinstall               xpi;
    application/xhtml+xml                 xhtml;
    application/xspf+xml                  xspf;
    application/zip                       zip;

    application/octet-stream              bin exe dll;
    application/octet-stream              deb;
    application/octet-stream              dmg;
    application/octet-stream              iso img;
    application/octet-stream              msi msp msm;

    application/vnd.openxmlformats-officedocument.wordprocessingml.document    docx;
    application/vnd.openxmlformats-officedocument.spreadsheetml.sheet          xlsx;
    application/vnd.openxmlformats-officedocument.presentationml.presentation  pptx;

    audio/midi                            mid midi kar;
    audio/mpeg                            mp3;
    audio/ogg                             ogg;
    audio/x-m4a                           m4a;
    audio/x-realaudio                     ra;

    video/3gpp                            3gpp 3gp;
    video/mp2t                            ts;
    video/mp4                             mp4;
    video/mpeg                            mpeg mpg;
    video/quicktime                       mov;
    video/webm                            webm;
    video/x-flv                           flv;
    video/x-m4v                           m4v;
    video/x-mng                           mng;
    video/x-ms-asf                        asx asf;
    video/x-ms-wmv                        wmv;
    video/x-msvideo                       avi;
}

# configuration file /etc/nginx/sites-enabled/default:
##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# https://www.nginx.com/resources/wiki/start/
# https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/
# https://wiki.debian.org/Nginx/DirectoryStructure
#
# In most cases, administrators will remove this file from sites-enabled/ and
# leave it as reference inside of sites-available where it will continue to be
# updated by the nginx packaging team.
#
# This file will automatically load configuration files provided by other
# applications, such as Drupal or Wordpress. These applications will be made
# available underneath a path with that package name, such as /drupal8.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

# Default server configuration
#
server {
        listen 80 default_server;
        listen [::]:80 default_server;

        # SSL configuration
        #
        # listen 443 ssl default_server;
        # listen [::]:443 ssl default_server;
        #
        # Note: You should disable gzip for SSL traffic.
        # See: https://bugs.debian.org/773332
        #
        # Read up on ssl_ciphers to ensure a secure configuration.
        # See: https://bugs.debian.org/765782
        #
        # Self signed certs generated by the ssl-cert package
        # Don't use them in a production server!
        #
        # include snippets/snakeoil.conf;

        root /var/www/html;

        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html;

        server_name _;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files $uri $uri/ =404;
        }

        # pass PHP scripts to FastCGI server
        #
        #location ~ \.php$ {
        #       include snippets/fastcgi-php.conf;
        #
        #       # With php-fpm (or other unix sockets):
        #       fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;
        #       # With php-cgi (or other tcp sockets):
        #       fastcgi_pass 127.0.0.1:9000;
        #}

        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        #location ~ /\.ht {
        #       deny all;
        #}
}


# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
#server {
#       listen 80;
#       listen [::]:80;
#
#       server_name example.com;
#
#       root /var/www/example.com;
#       index index.html;
#
#       location / {
#               try_files $uri $uri/ =404;
#       }
#}
2 Likes
20

That doesn't look right - there is no https section and no http to https redirection shown.
Yet LE sees this from it:

Please show:
nginx -v
curl -4 ifconfig.co

1 Like