Plugin Error: Can't parse default-ssl.conf

I was trying to setup a Let's Encrypt certificate with certbot but kept running into issues.
Initially I had a No candidate plugin error, but looking around, I found I had to install python3-certbot-apache which I thought did the trick.

Now, I'm facing a different issue, I don't know what honestly.
The log goes:

2021-06-13 19:49:47,687:DEBUG:certbot.main:certbot version: 0.31.0
2021-06-13 19:49:47,688:DEBUG:certbot.main:Arguments: ['--apache', '--no-redirect', '--staple-ocsp', '--agree-tos', '--no-eff-email', '--rsa-key-size', '4096', '-m', '', '-d', '']
2021-06-13 19:49:47,689:DEBUG:certbot.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#apache,PluginEntryPoint#manual,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2021-06-13 19:49:47,797:DEBUG:certbot.log:Root logging level set at 20
2021-06-13 19:49:47,799:INFO:certbot.log:Saving debug log to /var/log/letsencrypt/letsencrypt.log
2021-06-13 19:49:47,817:DEBUG:certbot.plugins.selection:Requested authenticator apache and installer apache
2021-06-13 19:49:48,336:DEBUG:certbot_apache.configurator:Apache version is 2.4.38
2021-06-13 19:49:49,432:DEBUG:certbot.plugins.disco:Other error:(PluginEntryPoint#apache): There has been an error in parsing the file /etc/apache2/sites-enabled/default-ssl.conf on line 144: Syntax error
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/certbot/plugins/", line 132, in prepare
  File "/usr/lib/python3/dist-packages/certbot_apache/", line 255, in prepare
  File "/usr/lib/python3/dist-packages/certbot_apache/", line 77, in check_parsing_errors
    raise errors.PluginError(msg)
certbot.errors.PluginError: There has been an error in parsing the file /etc/apache2/sites-enabled/default-ssl.conf on line 144: Syntax error
2021-06-13 19:49:49,442:DEBUG:certbot.plugins.selection:No candidate plugin
2021-06-13 19:49:49,443:DEBUG:certbot.plugins.selection:Selected authenticator None and installer None

My apache2 default-ssl.conf file is:

<IfModule mod_headers.c>
	<VirtualHost _default_:443>
		ServerAdmin webmaster@localhost

		Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains" 

		DocumentRoot /var/www/html

		# 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/apache2/ssl/CA.crt
		SSLCertificateKeyFile /etc/apache2/ssl/priv_and_pub.key

		#   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/apache2/ssl.crt/server-ca.crt

		#   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/apache2/ssl.crt/ca-bundle.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
		<Directory /usr/lib/cgi-bin>
				SSLOptions +StdEnvVars

		#   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


# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
#<VirtualHost *:443>
#  ServerName
#    <IfModule mod_headers.c>
#      Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains; preload"
#    </IfModule>
# </VirtualHost>

Problem is, line 144 doesn't exist, It's the last line on the file without any text on it.

Those are currently self-signed certs.
Any idea of what's going on or how to fix it?

I'm running certbot version 0.31.0
With the webserver being Apache2 2.4.38 (Raspbian)
I'm rocking dietpi (Debian 10 (Buster)) on a raspberry pi, so I've got full control over the device.

Does that last line contain a space or tab by any chance? Because in that case it might be related to a known bug:

Thanks for the input, your post gave me some new perspective while rechecking the .conf file.
All I had to do was add another /IfModule to the end.

P.S. I think think that issue has been fixed, I've got indentation and it still works :slight_smile:

1 Like

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