Just wondering why i can't renew my SSL

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: lerg.lt

I ran this command: certbot renew --cert-name lerg.lt

It produced this output:
Renewing an existing certificate for lerg.lt and www.lerg.lt
Failed to renew certificate lerg.lt with error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see Failed Validation Limit - Let's Encrypt


All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/lerg.lt/fullchain.pem (failure)


1 renew failure(s), 0 parse failure(s)

My web server is (include version):Apache/2.4.54 (Debian)

The operating system my web server runs on is (include version): debian-11.0-x86_64

My hosting provider, if applicable, is: iv.lt

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 1.12.0

Just as the message says you have tried and failed too often and must now wait an hour.

While waiting, use this command to use the Let's Encrypt Staging system. It is not as limited and will show the actual reason for your failure. The failures before the one you posted also would have shown the actual error. We need to know what that is

certbot renew --cert-name lerg.lt --dry-run
4 Likes

i run that and got this

rocessing /etc/letsencrypt/renewal/lerg.lt.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator apache, Installer apache
Simulating renewal of an existing certificate for lerg.lt and www.lerg.lt
Performing the following challenges:
http-01 challenge for lerg.lt
http-01 challenge for www.lerg.lt
Waiting for verification...
Challenge failed for domain lerg.lt
Challenge failed for domain www.lerg.lt
http-01 challenge for lerg.lt
http-01 challenge for www.lerg.lt
Cleaning up challenges
Failed to renew certificate lerg.lt with error: Some challenges have failed.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
All simulated renewals failed. The following certificates could not be renewed:
  /etc/letsencrypt/live/lerg.lt/fullchain.pem (failure)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1 renew failure(s), 0 parse failure(s)

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

   Domain: lerg.lt
   Type:   unauthorized
   Detail: 80.209.237.42: Invalid response from
   http://lerg.lt/.well-known/acme-challenge/JhbOp_JhTHE_k1wPTfavkxAzOfTWaqoW9ZUF0pisR64:
   400

   Domain: www.lerg.lt
   Type:   unauthorized
   Detail: 80.209.237.42: Invalid response from
   http://www.lerg.lt/.well-known/acme-challenge/TnhSDcLQmJUc8X-qSkM7iJue1-Ano8W5BtFJRnFJVHE:
   400

   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.

@MikeMcQ maybe u know what i'm missing ?

When I make a similar request I see more info. Does qkqy.c.dedikuoti.lt mean anything to you?

Also, something looks wrong with Apache. It shouldn't require HTTPS on port 80 that is for HTTP

curl -i http://lerg.lt/.well-known/acme-challenge/Test123
HTTP/1.1 400 Bad Request
Date: Fri, 09 Jun 2023 13:56:20 GMT
Server: Apache/2.4.56 (Debian)

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
 Instead use the HTTPS scheme to access this URL, please.<br />
</p>
<hr>
<address>Apache/2.4.56 (Debian) Server at qkqy.c.dedikuoti.lt Port 80</address>
</body></html>

3 Likes

well this is my server HostName

What can it be ?

1 Like

Probably doing HTTP and HTTPS in the same vhost server block.
Review your Apache config.
Starting with the output of:
sudo apachectl -t -D DUMP_VHOSTS

3 Likes

run that and got this

VirtualHost configuration:
*:80                   is a NameVirtualHost
         default server qkqy.c.dedikuoti.lt (/etc/apache2/sites-enabled/000-default.conf:1)
         port 80 namevhost qkqy.c.dedikuoti.lt (/etc/apache2/sites-enabled/000-default.conf:1)
         port 80 namevhost lerg.lt (/etc/apache2/sites-enabled/lerg.lt.conf:19)
                 alias www.lerg.lt
*:443                  is a NameVirtualHost
         default server qkqy.c.dedikuoti.lt (/etc/apache2/sites-enabled/default-ssl.conf:2)
         port 443 namevhost qkqy.c.dedikuoti.lt (/etc/apache2/sites-enabled/default-ssl.conf:2)
         port 443 namevhost lerg.lt (/etc/apache2/sites-enabled/lerg.lt.conf:1)
                 alias www.lerg.lt
         port 443 namevhost vvp.lerg.lt (/etc/apache2/sites-enabled/lergvvp.lt.conf:1)

Let's have a look at this file:

3 Likes

Well this file contains this:

<VirtualHost *:443>
    ServerAdmin admin@example.com
    ServerName lerg.lt
    ServerAlias www.lerg.lt
    DocumentRoot /var/www/lerg.lt
    <Directory /var/www/lerg.lt>
         Options Indexes FollowSymLinks
         AllowOverride All
         Require all granted
    </Directory>

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
     Include /etc/letsencrypt/options-ssl-apache.conf
     SSLCertificateFile /etc/letsencrypt/live/lerg.lt/fullchain.pem
     SSLCertificateKeyFile /etc/letsencrypt/live/lerg.lt/privkey.pem
</VirtualHost>

<VirtualHost *:80>
    ServerName lerg.lt
    ServerAlias www.lerg.lt
    DocumentRoot /var/www/lerg.lt
    
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
    
    RewriteEngine On
    RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L]
</VirtualHost>

Is there any NAT or port forwarding involved?

2 Likes

Tbh not sure haven't done that tho

If the server behind a firewall?

2 Likes

No i think it's it dissable or it dosent even have one

I don't mean a local firewall [that should always be on when directly connected to the Internet].

I mean: Is it behind some other physical device [like a firewall appliance]?

2 Likes

Well i have run that

systemctl --type=service

to check for firewall services and i dont have any

Let's have a look at these files:
/etc/apache2/ports.conf
/etc/apache2/apache2.conf

2 Likes
# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default.conf

Listen 80

<IfModule ssl_module>
	Listen 443
</IfModule>

<IfModule mod_gnutls.c>
	Listen 443
</IfModule>

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

and this is the default apache2.conf

# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#	/etc/apache2/
#	|-- apache2.conf
#	|	`--  ports.conf
#	|-- mods-enabled
#	|	|-- *.load
#	|	`-- *.conf
#	|-- conf-enabled
#	|	`-- *.conf
# 	`-- sites-enabled
#	 	`-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#Mutex file:${APACHE_LOCK_DIR} default

#
# The directory where shm and other runtime files will be stored.
#

DefaultRuntimeDir ${APACHE_RUN_DIR}

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
	Options FollowSymLinks
	AllowOverride None
	Require all denied
</Directory>

<Directory /usr/share>
	AllowOverride None
	Require all granted
</Directory>

<Directory /var/www/>
	Options Indexes FollowSymLinks
	AllowOverride None
	Require all granted
</Directory>

#<Directory /srv/>
#	Options Indexes FollowSymLinks
#	AllowOverride None
#	Require all granted
#</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
	Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

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