This is interesting:
curl https://theveninskeep.com:80/.well-known/acme-challenge/Test_File-1234
apachectl -t -D DUMP_VHOSTS
VirtualHost configuration:
*:443 TheveninsKeep.com (/etc/apache2/sites-enabled/TheveninsKeep.com-le-ssl.conf:2)
*:80 TheveninsKeep.com (/etc/apache2/sites-enabled/TheveninsKeep.com.conf:1)
And those two:
*:443
<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerAdmin admin@TheveninsKeep.com
ServerName TheveninsKeep.com
ServerAlias TheveninsKeep.com
DocumentRoot /var/www/TheveninsKeep.com/html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
<Directory "/var/www/TheveninsKeep.com/html">
AuthType Basic
AuthName "Restricted Content"
AuthUserFile <passwords :)>
Require valid-user
</Directory>
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/theveninskeep.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/theveninskeep.com/privkey.pem
</VirtualHost>
</IfModule>
*:80
<VirtualHost *:80>
#ServerAdmin admin@TheveninsKeep.com
ServerName TheveninsKeep.com
#DocumentRoot /var/www/TheveninsKeep.com/html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
#<Directory "/var/www/TheveninsKeep.com/html">
# AuthType Basic
# AuthName "Restricted Content"
# AuthUserFile /var/www/TheveninsKeep.com/passwords
# Require valid-user
#</Directory>
RewriteEngine on
RewriteCond %{REQUEST_URI} !^/.well-known/acme-challenge [NC]
RewriteRule (.*) https://%{SERVER_NAME}%{REQUEST_URI}
</VirtualHost>
We should probably start with the main config file.
curl https://theveninskeep.com:80/.well-known/acme-challenge/Test_File-1234
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>401 Unauthorized</title>
</head><body>
<h1>Unauthorized</h1>
<p>This server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.</p>
<hr>
<address>Apache/2.4.41 (Ubuntu) Server at theveninskeep.com Port 80</address>
</body></html>
@Rip, any comment on that response?
[other than my "interesting"]
doesn't set well... and there is an auth file in the mix which is certain to wreak havoc.
I take nothing for granted!
Let's also have a look at these outputs:
ls -l /etc/apache2/sites-enabled/
ls -l /etc/apache2/sites-available/
[please don't mask/hide anything]
sites-enabled:
lrwxrwxrwx 1 root root 41 Apr 21 20:17 TheveninsKeep.com.conf -> ../sites-available/TheveninsKeep.com.conf
lrwxrwxrwx 1 root root 58 Apr 21 20:34 TheveninsKeep.com-le-ssl.conf -> /etc/apache2/sites-available/TheveninsKeep.com-le-ssl.conf
sites-available:
-rw-r--r-- 1 root root 1332 Sep 30 2020 000-default.conf
-rw-r--r-- 1 root root 6338 Sep 30 2020 default-ssl.conf
-rw-r--r-- 1 root root 553 Jul 12 18:11 TheveninsKeep.com.conf
-rw-r--r-- 1 root root 547 Jul 10 14:05 TheveninsKeep.com.conf.orig
-rw-r--r-- 1 root root 673 Apr 21 20:43 TheveninsKeep.com-le-ssl.conf
I kept an "orig" conf before I started fussing with y'alls suggestions
as an FYI, I do have fail2ban configured to be a smidge aggressive.
failregex = ^<HOST> .*"GET (?!\/robots\.txt).*" (401|403|404|503)\s
^<HOST> .*"GET (?!\/).*" (400|401|403|404)\s
If there's three bad requests within a 360 hour period, the inbound IP gets bonked for effectively eternity. I believe if you consistently check for that full well-known URL it shouldn't ban.
I'm suspecting f2b may get in the way if not properly configured. It is not ALWAYS a problem but can cause issues with .well-known...
Just a thought not to interfere with @rg305 analysis.
Let's have a look at that conf file.
Weird how they are 17 seconds apart ...
But one uses "../" and the other uses the fully referenced path.
Highly likely unrelated to anything - but just weird...
Highly likely unrelated to anything - but just weird...
I was also thinking it was a bit weird, but I have practically zero web experience so I wasn't sure it would cause anything
Let's have a look at that conf file.
Assuming you mean the main .conf file, it's the one above:
<VirtualHost *:80>
#ServerAdmin admin@TheveninsKeep.com
ServerName TheveninsKeep.com
#DocumentRoot /var/www/TheveninsKeep.com/html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
#<Directory "/var/www/TheveninsKeep.com/html">
# AuthType Basic
# AuthName "Restricted Content"
# AuthUserFile /var/www/TheveninsKeep.com/passwords
# Require valid-user
#</Directory>
RewriteEngine on
RewriteCond %{REQUEST_URI} !^/.well-known/acme-challenge [NC]
RewriteRule (.*) https://%{SERVER_NAME}%{REQUEST_URI}
</VirtualHost>
I would recommend uncommenting the DocumentRoot. (If that's where the files live.)
I'm looking for a file like:
/etc/apache2/apache2.conf
[or something like that]
I didn't remove the comments, sorry for the XL post
# 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 All
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
True to form, F2B stops IPs that encounter 401s.
But it is returning 401s for things that it shouldn't be - normal GETs.
[false positive banning]
This is the reason for the relative path. @rg305
Nothing strange, nor even questionable, in the main config.
Let's see what is actually running:
ps -ef | grep -i apache | grep -v grep
[might need sudo]
I have updated this to be uncommented, reloaded, and now it doesn't return the relative path. Hooray for learning something about web?
After a clean start:
# ps -ef | grep -i apache | grep -v grep
root 367170 1 0 19:00 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 367172 367170 0 19:00 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 367173 367170 0 19:00 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 367174 367170 0 19:00 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 367175 367170 0 19:00 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 367176 367170 0 19:00 ? 00:00:00 /usr/sbin/apache2 -k start