Strange challenge auth failure

Your mandatory details below. TL;DR I’m seeing strange behavior out of either LE or certbot with an auth failure, where LE seems to be eating one character in the auth URL. The key message I’m seeing is this one:

https://www.mudmaker.org.well-known/acme-challenge/BRSHQaoLeroHx-Zw1K_Ufdj4auAZ6UEp3X-7D2JFNQw: Error getting validation data

Note the missing / before .well-known. I can’t tell if that’s just a diagnostic printing error or what. I don’t see where certbot is handing you the wrong domain, and it seems to be constructing the right domain, but I’m only ever having this problem with the one domain. Others work fine.

My domain is:

mudmaker.org

I ran this command:

/usr/bin/certbot certonly --dry-run -d mudmaker.org

It produced this output (some lines for readability):

Saving debug log to /var/log/letsencrypt/letsencrypt.log

How would you like to authenticate with the ACME CA?

1: Apache Web Server plugin - Beta (apache)
2: Spin up a temporary webserver (standalone)
3: Place files in webroot directory (webroot)


Select the appropriate number [1-3] then [enter] (press ‘c’ to cancel): 3
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for mudmaker.org

Select the webroot for mudmaker.org:


1: Enter a new webroot


Press 1 [enter] to confirm the selection (press ‘c’ to cancel): 1
Input the webroot for mudmaker.org: (Enter ‘c’ to cancel): /srv/www.mudmaker.org
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. mudmaker.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://www.mudmaker.org.well-known/acme-challenge/BRSHQaoLeroHx-Zw1K_Ufdj4auAZ6UEp3X-7D2JFNQw: Error getting validation data

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: mudmaker.org
    Type: connection
    Detail: Fetching
    https://www.mudmaker.org.well-known/acme-challenge/BRSHQaoLeroHx-Zw1K_Ufdj4auAZ6UEp3X-7D2JFNQw:
    Error getting validation data

    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. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.

My web server is (include version):

Apache/2.4.18 (Ubuntu)

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

Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial

My hosting provider, if applicable, is:

n/a

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

n/a

Diagnostics from the log follow:

{
“type”: “http-01”,
“status”: “invalid”,
“error”: {
“type”: “urn:acme:error:connection”,
“detail”: “Fetching https://www.mudmaker.org.well-known/acme-challenge/BRSHQa
oLeroHx-Zw1K_Ufdj4auAZ6UEp3X-7D2JFNQw: Error getting validation data”,
“status”: 400
},
“uri”: “https://acme-staging.api.letsencrypt.org/acme/challenge/QAPD-6kdF2srvaK
KpiaxrTZPTFOA_6hSOfyfWAmzFwI/83020404”,
“token”: “BRSHQaoLeroHx-Zw1K_Ufdj4auAZ6UEp3X-7D2JFNQw”,
“keyAuthorization”: “BRSHQaoLeroHx-Zw1K_Ufdj4auAZ6UEp3X-7D2JFNQw.qNEFcnWQhX4NY5
ZZUXRCIURJ2mLjBIthblxPVxyzvLw”,
“validationRecord”: [
{
“url”: “https://www.mudmaker.org.well-known/acme-challenge/BRSHQaoLeroHx-Zw
1K_Ufdj4auAZ6UEp3X-7D2JFNQw”,
“hostname”: “www.mudmaker.org.well-known”,
“port”: “443”,
“addressesResolved”: [],
“addressUsed”: “”,
“addressesTried”: []
},

Hi @elear,

Can you share your apache configuration for this domain? Usually this is caused by an incorrect redirect directive.

Thanks for the answer. Pls see below.

<VirtualHost *:80>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request’s Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.

ServerAdmin webmaster@mudmaker.org
DocumentRoot /srv/www.mudmaker.org
ServerName www.mudmaker.org
ServerAlias mudmaker.org
Redirect / https://www.mudmaker.org
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
LogLevel info ssl:warn

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined

# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf

<Directory “/srv/www.mudmaker.org/”>
Options None
AllowOverride None
Order allow,deny
Allow from all

ServerAdmin webmaster@upstairs.ofcourseimright.com DocumentRoot /srv/www.mudmaker.org/ ServerName www.mudmaker.org
	# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
	# error, crit, alert, emerg.
	# It is also possible to configure the loglevel for particular
	# modules, e.g.
	#LogLevel info ssl:warn

	ErrorLog ${APACHE_LOG_DIR}/error.log
	CustomLog ${APACHE_LOG_DIR}/access.log combined

	# For most configuration files from conf-available/, which are
	# enabled or disabled at a global level, it is possible to
	# include a line for only one particular virtual host. For example the
	# following line enables the CGI configuration for this host only
	# after it has been globally disabled with "a2disconf".
	#Include conf-available/serve-cgi-bin.conf

	#   SSL Engine Switch:
	#   Enable/Disable SSL for this virtual host.
	SSLEngine on

	#   A self-signed (snakeoil) certificate can be created by installing
	#   the ssl-cert package. See
	#   /usr/share/doc/apache2/README.Debian.gz for more info.
	#   If both key and certificate are stored in the same file, only the
	#   SSLCertificateFile directive is needed.
SSLCertificateFile  /etc/letsencrypt/live/mudmaker.org/cert.pem
SSLCertificateKeyFile  /etc/letsencrypt/live/mudmaker.org/privkey.pem

	#   Server Certificate Chain:
	#   Point SSLCertificateChainFile at a file containing the
	#   concatenation of PEM encoded CA certificates which form the
	#   certificate chain for the server certificate. Alternatively

root@upstairs:/etc/apache2/sites-enabled#
root@upstairs:/etc/apache2/sites-enabled# cat mudmaker.conf
<VirtualHost *:80>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request’s Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.

ServerAdmin webmaster@mudmaker.org
DocumentRoot /srv/www.mudmaker.org
ServerName www.mudmaker.org
ServerAlias mudmaker.org
Redirect / https://www.mudmaker.org
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
LogLevel info ssl:warn

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined

# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf

<Directory “/srv/www.mudmaker.org/”>
Options None
AllowOverride None
Order allow,deny
Allow from all

ServerAdmin webmaster@upstairs.ofcourseimright.com DocumentRoot /srv/www.mudmaker.org/ ServerName www.mudmaker.org
	# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
	# error, crit, alert, emerg.
	# It is also possible to configure the loglevel for particular
	# modules, e.g.
	#LogLevel info ssl:warn

	ErrorLog ${APACHE_LOG_DIR}/error.log
	CustomLog ${APACHE_LOG_DIR}/access.log combined

	# For most configuration files from conf-available/, which are
	# enabled or disabled at a global level, it is possible to
	# include a line for only one particular virtual host. For example the
	# following line enables the CGI configuration for this host only
	# after it has been globally disabled with "a2disconf".
	#Include conf-available/serve-cgi-bin.conf

	#   SSL Engine Switch:
	#   Enable/Disable SSL for this virtual host.
	SSLEngine on

	#   A self-signed (snakeoil) certificate can be created by installing
	#   the ssl-cert package. See
	#   /usr/share/doc/apache2/README.Debian.gz for more info.
	#   If both key and certificate are stored in the same file, only the
	#   SSLCertificateFile directive is needed.
SSLCertificateFile  /etc/letsencrypt/live/mudmaker.org/cert.pem
SSLCertificateKeyFile  /etc/letsencrypt/live/mudmaker.org/privkey.pem

	#   Server Certificate Chain:
	#   Point SSLCertificateChainFile at a file containing the
	#   concatenation of PEM encoded CA certificates which form the
	#   certificate chain for the server certificate. Alternatively
	#   the referenced file can be the same as SSLCertificateFile
	#   when the CA certificates are directly appended to the server
	#   certificate for convinience.
SSLCertificateChainFile /etc/letsencrypt/live/mudmaker.org/chain.pem

	#   Certificate Authority (CA):
	#   Set the CA certificate verification path where to find CA
	#   certificates for client authentication or alternatively one
	#   huge file containing all of them (file must be PEM encoded)
	#   Note: Inside SSLCACertificatePath you need hash symlinks
	#		 to point to the certificate files. Use the provided
	#		 Makefile to update the hash symlinks after changes.
	SSLCACertificatePath /etc/ssl/certs/
	SSLCACertificateFile /etc/ssl/certs/ca-certificates.crt

	#   Certificate Revocation Lists (CRL):
	#   Set the CA revocation path where to find CA CRLs for client
	#   authentication or alternatively one huge file containing all
	#   of them (file must be PEM encoded)
	#   Note: Inside SSLCARevocationPath you need hash symlinks
	#		 to point to the certificate files. Use the provided
	#		 Makefile to update the hash symlinks after changes.
	#SSLCARevocationPath /etc/apache2/ssl.crl/
	#SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl

	#   Client Authentication (Type):
	#   Client certificate verification type and depth.  Types are
	#   none, optional, require and optional_no_ca.  Depth is a
	#   number which specifies how deeply to verify the certificate
	#   issuer chain before deciding the certificate is not valid.
	#SSLVerifyClient require
	#SSLVerifyDepth  10

	#   SSL Engine Options:
	#   Set various options for the SSL engine.
	#   o FakeBasicAuth:
	#	 Translate the client X.509 into a Basic Authorisation.  This means that
	#	 the standard Auth/DBMAuth methods can be used for access control.  The
	#	 user name is the `one line' version of the client's X.509 certificate.
	#	 Note that no password is obtained from the user. Every entry in the user
	#	 file needs this password: `xxj31ZMTZzkVA'.
	#   o ExportCertData:
	#	 This exports two additional environment variables: SSL_CLIENT_CERT and
	#	 SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
	#	 server (always existing) and the client (only existing when client
	#	 authentication is used). This can be used to import the certificates
	#	 into CGI scripts.
	#   o StdEnvVars:
	#	 This exports the standard SSL/TLS related `SSL_*' environment variables.
	#	 Per default this exportation is switched off for performance reasons,
	#	 because the extraction step is an expensive operation and is usually
	#	 useless for serving static content. So one usually enables the
	#	 exportation for CGI and SSI requests only.
	#   o OptRenegotiate:
	#	 This enables optimized SSL connection renegotiation handling when SSL
	#	 directives are used in per-directory context.
	#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
	<FilesMatch "\.(cgi|shtml|phtml|php)$">
			SSLOptions +StdEnvVars
	</FilesMatch>
	<Directory /usr/lib/cgi-bin>
			SSLOptions +StdEnvVars
	</Directory>

<Directory “/srv/www.mudmaker.org/”>
Options None
AllowOverride None
Order allow,deny
Allow from all

# SSL Protocol Adjustments:
# The safe and default but still SSL/TLS standard compliant shutdown
# approach is that mod_ssl sends the close notify alert but doesn’t wait for
# the close notify alert from client. When you need a different shutdown
# approach you can use one of the following variables:
# o ssl-unclean-shutdown:
# This forces an unclean shutdown when the connection is closed, i.e. no
# SSL close notify alert is send or allowed to received. This violates
# the SSL/TLS standard but is needed for some brain-dead browsers. Use
# this when you receive I/O errors because of the standard approach where
# mod_ssl sends the close notify alert.
# o ssl-accurate-shutdown:
# This forces an accurate shutdown when the connection is closed, i.e. a
# SSL close notify alert is send and mod_ssl waits for the close notify
# alert of the client. This is 100% SSL/TLS standard compliant, but in
# practice often causes hanging connections with brain-dead browsers. Use
# this only for browsers where you know that their SSL implementation
# works correctly.
# Notice: Most problems of broken clients are also related to the HTTP
# keep-alive facility, so you usually additionally want to disable
# keep-alive for those clients, too. Use variable “nokeepalive” for this.
# Similarly, one has to force some clients to use HTTP/1.0 to workaround
# their broken HTTP/1.1 implementation. Use variables “downgrade-1.0” and
# “force-response-1.0” for this.
BrowserMatch “MSIE [2-6]”
nokeepalive ssl-unclean-shutdown
downgrade-1.0 force-response-1.0
# MSIE 7 and newer should be able to use keepalive
BrowserMatch “MSIE [17-9]” ssl-unclean-shutdown

</VirtualHost>

vim: syntax=apache ts=4 sw=4 sts=4 sr noet

By George that’s it. Thanks for the clue about the redirect.

1 Like

Woohoo! Glad to hear you were able to solve the problem :lock::chart_with_upwards_trend::tada:

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