500 Internal Error after running certbot, perhaps pointed to wrong virtual host conf file?

natew · January 1, 2025, 11:33am

My domain is: natewest.jp

I ran this command: sudo certbot --apache

It produced this output: During the certbot configuration, it asked me which virtual host to choose. I chose wordpress-https.conf, but now I'm realizing maybe I was supposed to choose 000-default.conf. Here is the log of certbot working:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Please enter the domain name(s) you would like on your certificate (comma and/or
space separated) (Enter 'c' to cancel): natewest.jp www.natewest.jp
Requesting a certificate for natewest.jp and www.natewest.jp

Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/natewest.jp/fullchain.pem
Key is saved at:         /etc/letsencrypt/live/natewest.jp/privkey.pem
This certificate expires on 2025-04-01.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.

Deploying certificate

We were unable to find a vhost with a ServerName or Address of natewest.jp.
Which virtual host would you like to choose?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: wordpress-https.conf           |                       | HTTPS | Enabled
2: 000-default.conf               |                       |       | Enabled
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1
Successfully deployed certificate for natewest.jp to /etc/apache2/sites-enabled/wordpress-https.conf

We were unable to find a vhost with a ServerName or Address of www.natewest.jp.
Which virtual host would you like to choose?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: wordpress-https.conf           | natewest.jp           | HTTPS | Enabled
2: 000-default.conf               |                       |       | Enabled
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1
Successfully deployed certificate for www.natewest.jp to /etc/apache2/sites-enabled/wordpress-https.conf
Congratulations! You have successfully enabled HTTPS on https://natewest.jp and https://www.natewest.jp

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
If you like Certbot, please consider supporting our work by:
 * Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
 * Donating to EFF:                    https://eff.org/donate-le
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

My web server is: Apache/2.4.62 (Debian)

The operating system my web server runs on is: Debian GNU/Linux 11 (bullseye)

My hosting provider, if applicable, is: Google Cloud Compute Engine VM

I can login to a root shell on my machine: yes

I'm using a control panel to manage my site: no

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

natew · January 1, 2025, 2:56pm

Just wanted to add a follow-up to say happy new year and thank you for any help. Apologies, I got so caught up in the post template and problem that I forgot. Also thought it might help if I add the contents of these:

wordpress-https.conf

<VirtualHost *:443>
  ServerAdmin admin@example.com
  DocumentRoot /var/www/html
  SSLEngine on

  <Directory /var/www/html>
    Options -Indexes
    AllowOverride FileInfo
  </Directory>

  <Files xmlrpc.php>
    order deny,allow
    deny from all
  </Files>

    ServerName natewest.jp
Include /etc/letsencrypt/options-ssl-apache.conf
ServerAlias www.natewest.jp
SSLCertificateFile /etc/letsencrypt/live/natewest.jp/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/natewest.jp/privkey.pem
</VirtualHost>

000-default.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.
        #ServerName www.example.com

        ServerAdmin webmaster@localhost
        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
RewriteEngine on
RewriteCond %{SERVER_NAME} =natewest.jp [OR]
RewriteCond %{SERVER_NAME} =www.natewest.jp
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>

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

and apachectl -s output

VirtualHost configuration:
*:80                   natewest-gcd-vm.asia-northeast2-a.c.nate-west-website.internal (/etc/apache2/sites-enabled/000-default.conf:1)
*:443                  natewest.jp (/etc/apache2/sites-enabled/wordpress-https.conf:1)
ServerRoot: "/etc/apache2"
Main DocumentRoot: "/var/www/html"
Main ErrorLog: "/var/log/apache2/error.log"
Mutex watchdog-callback: using_defaults
Mutex rewrite-map: using_defaults
Mutex ssl-stapling-refresh: using_defaults
Mutex ssl-stapling: using_defaults
Mutex proxy: using_defaults
Mutex ssl-cache: using_defaults
Mutex default: dir="/var/run/apache2/" mechanism=default 
Mutex mpm-accept: using_defaults
PidFile: "/var/run/apache2/apache2.pid"
Define: DUMP_VHOSTS
Define: DUMP_RUN_CFG
User: name="www-data" id=33
Group: name="www-data" id=33

Osiris · January 1, 2025, 3:07pm

I don't directly see anything very weird in your Apache configuration. The only thing "weird" perhaps is that your 000-default.conf is functioning as the HTTP virtualhost with the redirect and wordpress-https.conf is taking care of the HTTPS virtualhost.. But that in't wrong or should not give you the internal error. The redirect is working just fine by the way. (You might want to refuse HTTP access to anything else than natewest.jp and www.natewest.jp, but that's just a detail.)

Looking at your wordpress-https.conf I also don't see anything incorrect, which would cause the internal error. And it does look like it's your HTTPS vhost that's causing the issue. Because if I bypass your redirect by specifying a completely other hostname (e.g. example.com), but still use your IP address with the command curl -v --resolve example.com:80:34.97.31.233 http://example.com/, I can see your website.

My suggestion is to check your Apache error log to see the actual cause of the internal error.

natew · January 1, 2025, 3:59pm

Thank you so much for the response and information. I see, so it doesn't affect things too much if the https is handled by wordpress-https.conf?

I've copied the error.log, it's quite long, I apologize it doesn't mean too much to me... I am a 99% front-end developer that is dabbling in his own backend work to save money and practice. Any advice is appreciated!

[Wed Jan 01 07:07:24.813104 2025] [mpm_prefork:notice] [pid 630:tid 630] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 07:07:24.813219 2025] [core:notice] [pid 630:tid 630] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 07:08:34.433561 2025] [mpm_prefork:notice] [pid 630:tid 630] AH00170: caught SIGWINCH, shutting down gracefully
[Wed Jan 01 07:09:17.613195 2025] [ssl:warn] [pid 1361:tid 1361] AH01909: natewest-gcd-vm.asia-northeast2-a.c.nate-west-website.internal:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jan 01 07:09:18.059406 2025] [ssl:warn] [pid 1362:tid 1362] AH01909: natewest-gcd-vm.asia-northeast2-a.c.nate-west-website.internal:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jan 01 07:09:18.099431 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 07:09:18.099468 2025] [core:notice] [pid 1362:tid 1362] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 08:41:46.584166 2025] [core:alert] [pid 1928:tid 1928] [client 45.83.64.2:26990] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 08:41:47.863384 2025] [core:alert] [pid 1723:tid 1723] [client 45.83.64.82:27000] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 09:27:26.847768 2025] [core:error] [pid 1928:tid 1928] [client 1.95.150.188:41516] AH10244: invalid URI path (/cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh)
[Wed Jan 01 09:27:27.626117 2025] [core:error] [pid 2023:tid 2023] [client 1.95.150.188:41528] AH10244: invalid URI path (/cgi-bin/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/bin/sh)
[Wed Jan 01 09:41:05.962181 2025] [proxy_fcgi:error] [pid 1918:tid 1918] [client 93.174.93.12:60000] AH01071: Got error 'PHP message: PHP Warning:  Undefined array key "host" in /var/www/html/wp-includes/canonical.php on line 717PHP message: PHP Warning:  Undefined array key "host" in /var/www/html/wp-includes/canonical.php on line 728PHP message: PHP Warning:  Undefined array key "host" in /var/www/html/wp-includes/canonical.php on line 731PHP message: PHP Warning:  Undefined array key "scheme" in /var/www/html/wp-includes/canonical.php on line 752PHP message: PHP Warning:  Undefined array key "host" in /var/www/html/wp-includes/canonical.php on line 717PHP message: PHP Warning:  Undefined array key "host" in /var/www/html/wp-includes/canonical.php on line 728PHP message: PHP Warning:  Undefined array key "host" in /var/www/html/wp-includes/canonical.php on line 731PHP message: PHP Warning:  Undefined array key "scheme" in /var/www/html/wp-includes/canonical.php on line 752'
[Wed Jan 01 09:55:14.593189 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00171: Graceful restart requested, doing restart
[Wed Jan 01 09:55:20.960259 2025] [ssl:warn] [pid 1362:tid 1362] AH01909: natewest-gcd-vm.asia-northeast2-a.c.nate-west-website.internal:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jan 01 09:55:20.960577 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 09:55:20.960588 2025] [core:notice] [pid 1362:tid 1362] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 09:55:25.578979 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00171: Graceful restart requested, doing restart
[Wed Jan 01 09:55:25.685245 2025] [ssl:warn] [pid 1362:tid 1362] AH01909: natewest-gcd-vm.asia-northeast2-a.c.nate-west-website.internal:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jan 01 09:55:25.685427 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 09:55:25.685435 2025] [core:notice] [pid 1362:tid 1362] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 09:58:28.030570 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00171: Graceful restart requested, doing restart
[Wed Jan 01 09:58:30.755348 2025] [ssl:warn] [pid 1362:tid 1362] AH01909: natewest-gcd-vm.asia-northeast2-a.c.nate-west-website.internal:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jan 01 09:58:30.755678 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 09:58:30.755693 2025] [core:notice] [pid 1362:tid 1362] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 09:58:32.574784 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00171: Graceful restart requested, doing restart
[Wed Jan 01 09:58:32.688269 2025] [ssl:warn] [pid 1362:tid 1362] AH01909: natewest-gcd-vm.asia-northeast2-a.c.nate-west-website.internal:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jan 01 09:58:32.688444 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 09:58:32.688451 2025] [core:notice] [pid 1362:tid 1362] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 10:01:35.660849 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00171: Graceful restart requested, doing restart
[Wed Jan 01 10:01:37.604906 2025] [ssl:warn] [pid 1362:tid 1362] AH01909: natewest-gcd-vm.asia-northeast2-a.c.nate-west-website.internal:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jan 01 10:01:37.605224 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 10:01:37.605234 2025] [core:notice] [pid 1362:tid 1362] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 10:01:43.537069 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00171: Graceful restart requested, doing restart
[Wed Jan 01 10:01:43.833371 2025] [ssl:warn] [pid 1362:tid 1362] AH01909: natewest-gcd-vm.asia-northeast2-a.c.nate-west-website.internal:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jan 01 10:01:43.833563 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 10:01:43.833571 2025] [core:notice] [pid 1362:tid 1362] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 10:03:02.010401 2025] [core:alert] [pid 4658:tid 4658] [client 104.164.173.32:48618] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:02.999194 2025] [core:alert] [pid 4659:tid 4659] [client 154.28.229.91:50974] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:23.642037 2025] [core:alert] [pid 4665:tid 4665] [client 159.89.127.165:59718] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:23.686132 2025] [core:alert] [pid 4667:tid 4667] [client 159.223.132.86:36166] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:27.302968 2025] [core:alert] [pid 4670:tid 4670] [client 159.89.127.165:60512] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:27.558023 2025] [core:alert] [pid 4668:tid 4668] [client 159.223.132.86:36260] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:27.761728 2025] [authz_core:error] [pid 4670:tid 4670] [client 165.22.235.3:50830] AH01630: client denied by server configuration: /var/www/html/server-status
[Wed Jan 01 10:03:27.764679 2025] [core:alert] [pid 4666:tid 4666] [client 159.89.127.165:60526] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:28.080568 2025] [core:alert] [pid 4667:tid 4667] [client 159.223.132.86:36262] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:28.217430 2025] [authz_core:error] [pid 4658:tid 4658] [client 167.99.182.39:36258] AH01630: client denied by server configuration: /var/www/html/server-status
[Wed Jan 01 10:03:28.222716 2025] [core:alert] [pid 4657:tid 4657] [client 159.89.127.165:60538] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:28.689222 2025] [core:alert] [pid 4665:tid 4665] [client 159.223.132.86:36266] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:28.769719 2025] [core:alert] [pid 4659:tid 4659] [client 159.89.127.165:60540] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:29.243551 2025] [core:alert] [pid 4662:tid 4662] [client 159.223.132.86:36276] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:29.299367 2025] [core:alert] [pid 4672:tid 4672] [client 159.89.127.165:60554] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:29.775961 2025] [core:alert] [pid 4669:tid 4669] [client 159.223.132.86:58126] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:29.919346 2025] [core:alert] [pid 4670:tid 4670] [client 159.89.127.165:60560] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:30.301902 2025] [core:alert] [pid 4674:tid 4674] [client 159.223.132.86:58134] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:30.387536 2025] [core:alert] [pid 4670:tid 4670] [client 159.89.127.165:60572] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:30.799090 2025] [core:alert] [pid 4664:tid 4664] [client 159.223.132.86:58138] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:30.853418 2025] [core:alert] [pid 4663:tid 4663] [client 159.89.127.165:60582] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:31.047210 2025] [proxy_fcgi:error] [pid 4661:tid 4661] [client 165.22.235.3:50908] AH01071: Got error 'Primary script unknown'
[Wed Jan 01 10:03:31.301470 2025] [core:alert] [pid 4665:tid 4665] [client 159.223.132.86:58152] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:31.354400 2025] [core:alert] [pid 4659:tid 4659] [client 159.89.127.165:60590] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:31.376415 2025] [proxy_fcgi:error] [pid 4660:tid 4660] [client 167.99.182.39:36340] AH01071: Got error 'Primary script unknown'
[Wed Jan 01 10:03:31.796514 2025] [core:alert] [pid 4662:tid 4662] [client 159.223.132.86:58154] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:31.862916 2025] [core:alert] [pid 4672:tid 4672] [client 159.89.127.165:60602] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:32.290840 2025] [core:alert] [pid 4668:tid 4668] [client 159.223.132.86:58162] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:32.371824 2025] [core:alert] [pid 4675:tid 4675] [client 159.89.127.165:60608] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:32.785530 2025] [core:alert] [pid 4673:tid 4673] [client 159.223.132.86:58178] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:32.831382 2025] [core:alert] [pid 4671:tid 4671] [client 159.89.127.165:60620] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:33.280241 2025] [core:alert] [pid 4658:tid 4658] [client 159.223.132.86:58188] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:33.287293 2025] [core:alert] [pid 4657:tid 4657] [client 159.89.127.165:60634] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:33.747094 2025] [core:alert] [pid 4675:tid 4675] [client 159.89.127.165:60646] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:33.767108 2025] [core:alert] [pid 4667:tid 4667] [client 159.223.132.86:58196] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:34.202616 2025] [core:alert] [pid 4663:tid 4663] [client 159.89.127.165:38076] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:34.263063 2025] [core:alert] [pid 4673:tid 4673] [client 159.223.132.86:58208] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:34.663266 2025] [core:alert] [pid 4671:tid 4671] [client 159.89.127.165:38082] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:34.757258 2025] [core:alert] [pid 4661:tid 4661] [client 159.223.132.86:58222] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:35.130334 2025] [core:alert] [pid 4670:tid 4670] [client 159.89.127.165:38098] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:35.245000 2025] [core:alert] [pid 4665:tid 4665] [client 159.223.132.86:58230] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:35.589531 2025] [core:alert] [pid 4659:tid 4659] [client 159.89.127.165:38100] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:35.744878 2025] [core:alert] [pid 4660:tid 4660] [client 159.223.132.86:58240] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:36.045638 2025] [core:alert] [pid 4658:tid 4658] [client 159.89.127.165:38114] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:36.250248 2025] [core:alert] [pid 4664:tid 4664] [client 159.223.132.86:58246] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:03:36.755297 2025] [core:alert] [pid 4666:tid 4666] [client 159.223.132.86:58248] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:04:05.517321 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00171: Graceful restart requested, doing restart
[Wed Jan 01 10:04:07.990220 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 10:04:07.990245 2025] [core:notice] [pid 1362:tid 1362] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 10:04:07.990251 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00171: Graceful restart requested, doing restart
[Wed Jan 01 10:04:08.226710 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 10:04:08.226849 2025] [core:notice] [pid 1362:tid 1362] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 10:04:52.680379 2025] [core:alert] [pid 4695:tid 4695] [client 126.83.112.8:60015] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://natewest.jp/wp-admin/index.php
[Wed Jan 01 10:04:54.800586 2025] [core:alert] [pid 4691:tid 4691] [client 126.83.112.8:24324] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:04:54.864227 2025] [core:alert] [pid 4690:tid 4690] [client 126.83.112.8:60017] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: https://natewest.jp/
[Wed Jan 01 10:05:26.452594 2025] [mpm_prefork:notice] [pid 1362:tid 1362] AH00170: caught SIGWINCH, shutting down gracefully
[Wed Jan 01 10:05:27.647230 2025] [mpm_prefork:notice] [pid 4711:tid 4711] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 10:05:27.647327 2025] [core:notice] [pid 4711:tid 4711] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 10:05:42.646605 2025] [core:alert] [pid 4715:tid 4715] [client 126.83.112.8:60026] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://natewest.jp/
[Wed Jan 01 10:05:47.704383 2025] [core:alert] [pid 4713:tid 4713] [client 126.83.112.8:24261] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:06:50.456138 2025] [core:alert] [pid 4717:tid 4717] [client 35.226.227.254:52284] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:08:07.967789 2025] [core:alert] [pid 4715:tid 4715] [client 126.83.112.8:24468] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:08:09.124742 2025] [core:alert] [pid 4714:tid 4714] [client 126.83.112.8:24469] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:08:09.979553 2025] [core:alert] [pid 4713:tid 4713] [client 126.83.112.8:60039] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:08:16.761462 2025] [core:alert] [pid 4712:tid 4712] [client 126.83.112.8:23893] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:08:58.300827 2025] [core:alert] [pid 4713:tid 4713] [client 205.169.39.8:42527] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://www.natewest.jp
[Wed Jan 01 10:09:08.277541 2025] [core:alert] [pid 4732:tid 4732] [client 34.132.93.116:34030] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:09:24.841056 2025] [core:alert] [pid 4715:tid 4715] [client 126.83.112.8:60047] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:09:29.770777 2025] [core:alert] [pid 4713:tid 4713] [client 126.83.112.8:24077] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:09:35.815267 2025] [core:alert] [pid 4732:tid 4732] [client 126.83.112.8:24140] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:09:41.001079 2025] [core:alert] [pid 4732:tid 4732] [client 126.83.112.8:23884] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:09:41.021962 2025] [core:alert] [pid 4717:tid 4717] [client 126.83.112.8:23885] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:09:41.136363 2025] [core:alert] [pid 4714:tid 4714] [client 126.83.112.8:23756] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:09:50.048152 2025] [core:alert] [pid 4714:tid 4714] [client 126.83.112.8:23826] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:13:17.630454 2025] [core:alert] [pid 4712:tid 4712] [client 44.236.207.248:49709] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:13:17.734207 2025] [core:alert] [pid 4713:tid 4713] [client 44.236.207.248:18661] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:13:18.120914 2025] [core:alert] [pid 4716:tid 4716] [client 44.236.207.248:20864] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:13:18.466165 2025] [core:alert] [pid 4714:tid 4714] [client 44.236.207.248:32527] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: https://natewest.jp/
[Wed Jan 01 10:29:45.766063 2025] [core:alert] [pid 4714:tid 4714] [client 126.83.112.8:60183] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:40:46.124829 2025] [core:alert] [pid 4816:tid 4816] [client 126.83.112.8:25203] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:40:47.369866 2025] [core:alert] [pid 4712:tid 4712] [client 126.83.112.8:24947] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:40:48.304291 2025] [core:alert] [pid 4713:tid 4713] [client 126.83.112.8:60252] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:41:05.810581 2025] [core:alert] [pid 4817:tid 4817] [client 126.83.112.8:60260] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:42:51.795721 2025] [core:alert] [pid 4716:tid 4716] [client 126.83.112.8:25227] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:44:01.226426 2025] [core:alert] [pid 4712:tid 4712] [client 126.83.112.8:25547] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:44:02.259236 2025] [core:alert] [pid 4713:tid 4713] [client 126.83.112.8:60276] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:44:05.595545 2025] [core:alert] [pid 4716:tid 4716] [client 126.83.112.8:60279] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:44:08.014776 2025] [core:alert] [pid 4817:tid 4817] [client 126.83.112.8:24747] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:44:20.554565 2025] [core:alert] [pid 4714:tid 4714] [client 126.83.112.8:25259] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:44:20.599760 2025] [core:alert] [pid 4717:tid 4717] [client 126.83.112.8:60287] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:44:20.672568 2025] [core:alert] [pid 4816:tid 4816] [client 126.83.112.8:60288] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:44:25.265934 2025] [core:alert] [pid 4716:tid 4716] [client 126.83.112.8:60290] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:49:21.516928 2025] [core:alert] [pid 4818:tid 4818] [client 126.83.112.8:60322] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:49:27.648983 2025] [core:alert] [pid 4713:tid 4713] [client 126.83.112.8:25110] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:49:27.695335 2025] [core:alert] [pid 4715:tid 4715] [client 126.83.112.8:24854] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:49:27.795056 2025] [core:alert] [pid 4817:tid 4817] [client 126.83.112.8:24855] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:49:29.287162 2025] [core:alert] [pid 4717:tid 4717] [client 126.83.112.8:24726] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:49:59.301489 2025] [core:alert] [pid 4732:tid 4732] [client 126.83.112.8:25526] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:49:59.326305 2025] [core:alert] [pid 4713:tid 4713] [client 126.83.112.8:24695] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:49:59.330100 2025] [core:alert] [pid 4715:tid 4715] [client 126.83.112.8:24694] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:50:00.212169 2025] [core:alert] [pid 4817:tid 4817] [client 126.83.112.8:60337] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:50:00.244019 2025] [core:alert] [pid 4717:tid 4717] [client 126.83.112.8:24951] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:50:00.314373 2025] [core:alert] [pid 4716:tid 4716] [client 126.83.112.8:24822] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 10:50:02.658323 2025] [core:alert] [pid 4818:tid 4818] [client 126.83.112.8:25079] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 10:55:23.047557 2025] [core:alert] [pid 4715:tid 4715] [client 192.175.111.233:1284] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://natewest.jp/
[Wed Jan 01 10:55:25.769260 2025] [core:alert] [pid 4717:tid 4717] [client 192.175.111.250:31086] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://natewest.jp/
[Wed Jan 01 10:55:27.440910 2025] [core:alert] [pid 4818:tid 4818] [client 192.175.111.250:28145] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://natewest.jp/
[Wed Jan 01 10:55:28.296432 2025] [core:alert] [pid 4714:tid 4714] [client 192.175.111.230:55966] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://natewest.jp/
[Wed Jan 01 10:57:51.951218 2025] [mpm_prefork:notice] [pid 4711:tid 4711] AH00171: Graceful restart requested, doing restart
[Wed Jan 01 10:57:57.356515 2025] [mpm_prefork:notice] [pid 4711:tid 4711] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 10:57:57.356552 2025] [core:notice] [pid 4711:tid 4711] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 11:15:45.460589 2025] [core:alert] [pid 5202:tid 5202] [client 126.83.112.8:60534] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:19:42.213202 2025] [core:alert] [pid 5200:tid 5200] [client 64.41.200.113:56354] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:20:27.185492 2025] [core:alert] [pid 5200:tid 5200] [client 34.97.31.233:44146] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:24:03.757849 2025] [core:alert] [pid 5201:tid 5201] [client 126.83.112.8:60594] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:24:04.679318 2025] [core:alert] [pid 5349:tid 5349] [client 126.83.112.8:60595] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:24:07.037742 2025] [core:alert] [pid 5199:tid 5199] [client 126.83.112.8:60596] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:37:21.646966 2025] [core:alert] [pid 5202:tid 5202] [client 126.83.112.8:60653] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:39:18.721748 2025] [core:alert] [pid 5231:tid 5231] [client 126.83.112.8:60673] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:40:39.897764 2025] [core:alert] [pid 5200:tid 5200] [client 126.83.112.8:25803] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:40:44.939399 2025] [core:alert] [pid 5201:tid 5201] [client 126.83.112.8:60686] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:48:00.029574 2025] [core:alert] [pid 5199:tid 5199] [client 126.83.112.8:60721] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:51:21.201006 2025] [core:alert] [pid 5231:tid 5231] [client 126.83.112.8:60756] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:51:27.279869 2025] [core:alert] [pid 5201:tid 5201] [client 126.83.112.8:60760] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:51:27.312920 2025] [core:alert] [pid 5200:tid 5200] [client 126.83.112.8:60759] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: https://www.natewest.jp/
[Wed Jan 01 11:51:37.221045 2025] [core:alert] [pid 5349:tid 5349] [client 126.83.112.8:26347] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 11:57:48.129390 2025] [core:alert] [pid 5203:tid 5203] [client 87.236.176.215:58469] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:00:34.420963 2025] [core:alert] [pid 5349:tid 5349] [client 104.166.80.156:34694] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:11:40.971575 2025] [core:alert] [pid 5203:tid 5203] [client 34.27.46.102:48722] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:11:42.278118 2025] [core:alert] [pid 5199:tid 5199] [client 34.30.85.189:36484] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:11:43.561394 2025] [core:alert] [pid 5202:tid 5202] [client 34.68.145.243:36550] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:11:44.669165 2025] [core:alert] [pid 5231:tid 5231] [client 34.68.145.243:36564] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:11:51.214348 2025] [core:alert] [pid 5201:tid 5201] [client 34.27.46.102:50214] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:11:52.753425 2025] [core:alert] [pid 5349:tid 5349] [client 35.236.230.103:47366] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:11:54.078148 2025] [core:alert] [pid 5200:tid 5200] [client 34.68.145.243:59940] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:11:55.202319 2025] [core:alert] [pid 5203:tid 5203] [client 34.68.145.243:59948] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:13:46.650597 2025] [core:alert] [pid 5199:tid 5199] [client 51.81.46.212:42214] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:36:12.545835 2025] [core:alert] [pid 5203:tid 5203] [client 98.83.109.208:37979] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:36:13.061844 2025] [core:alert] [pid 5199:tid 5199] [client 98.83.109.208:32104] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: https://natewest.jp/
[Wed Jan 01 12:38:55.054975 2025] [core:alert] [pid 5349:tid 5349] [client 20.105.137.134:60996] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:41:16.802981 2025] [core:alert] [pid 5200:tid 5200] [client 104.253.203.57:6934] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:41:17.022056 2025] [core:alert] [pid 5203:tid 5203] [client 104.253.203.57:6920] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: https://natewest.jp/
[Wed Jan 01 12:42:08.608445 2025] [core:alert] [pid 5231:tid 5231] [client 104.253.203.138:32168] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:42:09.331780 2025] [core:alert] [pid 5349:tid 5349] [client 104.253.203.138:30564] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: https://natewest.jp/
[Wed Jan 01 12:47:08.052463 2025] [core:alert] [pid 5200:tid 5200] [client 95.164.158.154:39588] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:47:10.096253 2025] [core:alert] [pid 5199:tid 5199] [client 176.103.243.3:15570] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:47:11.691906 2025] [core:alert] [pid 5349:tid 5349] [client 18.207.120.134:50850] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:47:12.526022 2025] [core:alert] [pid 5200:tid 5200] [client 34.234.11.9:39144] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 12:48:30.317196 2025] [core:alert] [pid 5203:tid 5203] [client 52.20.19.158:62976] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 13:03:21.392303 2025] [core:alert] [pid 5200:tid 5200] [client 34.248.137.227:54924] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 13:03:22.619118 2025] [core:alert] [pid 5203:tid 5203] [client 34.248.137.227:54928] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 13:03:23.867520 2025] [core:alert] [pid 5202:tid 5202] [client 34.248.137.227:54938] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 13:03:25.079034 2025] [core:alert] [pid 5231:tid 5231] [client 34.248.137.227:54952] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 13:08:25.449262 2025] [core:alert] [pid 5976:tid 5976] [client 52.55.247.251:37142] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 13:08:29.258575 2025] [core:alert] [pid 5203:tid 5203] [client 38.154.214.45:54370] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 13:13:16.302504 2025] [core:alert] [pid 5200:tid 5200] [client 207.241.225.134:41266] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 13:38:40.425167 2025] [core:alert] [pid 5201:tid 5201] [client 205.169.39.18:46273] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 13:48:06.965262 2025] [core:error] [pid 5976:tid 5976] [client 102.211.152.45:57312] AH10244: invalid URI path (/cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh)
[Wed Jan 01 13:48:16.369224 2025] [core:error] [pid 5201:tid 5201] [client 102.211.152.45:38778] AH10244: invalid URI path (/cgi-bin/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/bin/sh)
[Wed Jan 01 14:16:58.795560 2025] [core:alert] [pid 5231:tid 5231] [client 20.229.51.198:38970] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:26:24.506381 2025] [core:alert] [pid 5976:tid 5976] [client 51.68.163.46:43689] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:07.559359 2025] [core:alert] [pid 5203:tid 5203] [client 193.56.113.27:46236] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:07.559851 2025] [core:alert] [pid 5200:tid 5200] [client 193.56.113.27:52488] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:09.268981 2025] [core:alert] [pid 5231:tid 5231] [client 193.56.113.27:46246] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:09.307445 2025] [core:alert] [pid 5202:tid 5202] [client 193.56.113.27:59065] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:11.015225 2025] [core:alert] [pid 5349:tid 5349] [client 193.56.113.27:46272] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:11.097681 2025] [core:alert] [pid 5976:tid 5976] [client 193.56.113.27:46276] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:12.723757 2025] [core:alert] [pid 5199:tid 5199] [client 193.56.113.27:35050] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:12.814860 2025] [core:alert] [pid 5201:tid 5201] [client 193.56.113.27:35064] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:14.451356 2025] [core:alert] [pid 5200:tid 5200] [client 193.56.113.27:35080] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:14.548892 2025] [core:alert] [pid 5203:tid 5203] [client 193.56.113.27:35086] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:16.177419 2025] [core:alert] [pid 5231:tid 5231] [client 193.56.113.27:35088] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:16.269724 2025] [core:alert] [pid 5202:tid 5202] [client 193.56.113.27:35092] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:17.896351 2025] [core:alert] [pid 5349:tid 5349] [client 193.56.113.27:35106] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:17.987911 2025] [core:alert] [pid 5976:tid 5976] [client 193.56.113.27:25362] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:19.611015 2025] [core:alert] [pid 5199:tid 5199] [client 193.56.113.27:35118] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:19.713764 2025] [core:alert] [pid 5201:tid 5201] [client 193.56.113.27:35130] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:21.339008 2025] [core:alert] [pid 5200:tid 5200] [client 193.56.113.27:39749] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:21.453494 2025] [core:alert] [pid 5203:tid 5203] [client 193.56.113.27:35148] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:23.073937 2025] [core:alert] [pid 5231:tid 5231] [client 193.56.113.27:52106] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:23.172797 2025] [core:alert] [pid 5202:tid 5202] [client 193.56.113.27:37401] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:24.789266 2025] [core:alert] [pid 5349:tid 5349] [client 193.56.113.27:21297] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:24.876050 2025] [core:alert] [pid 5976:tid 5976] [client 193.56.113.27:52122] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:26.506966 2025] [core:alert] [pid 5199:tid 5199] [client 193.56.113.27:1731] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:26.591934 2025] [core:alert] [pid 5201:tid 5201] [client 193.56.113.27:20983] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:28.226592 2025] [core:alert] [pid 5200:tid 5200] [client 193.56.113.27:52146] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:28.366206 2025] [core:alert] [pid 5203:tid 5203] [client 193.56.113.27:52148] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:29.999177 2025] [core:alert] [pid 5231:tid 5231] [client 193.56.113.27:52154] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:30.140962 2025] [core:alert] [pid 5202:tid 5202] [client 193.56.113.27:52166] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:31.782167 2025] [core:alert] [pid 5349:tid 5349] [client 193.56.113.27:16416] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:30:31.863979 2025] [core:alert] [pid 5976:tid 5976] [client 193.56.113.27:52170] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:31:20.169829 2025] [core:alert] [pid 5201:tid 5201] [client 204.101.161.19:45218] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:32:03.709767 2025] [core:alert] [pid 5231:tid 5231] [client 140.228.24.62:37566] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:40:25.414409 2025] [core:alert] [pid 5976:tid 5976] [client 154.213.184.16:43834] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:47:55.089892 2025] [core:alert] [pid 5199:tid 5199] [client 126.83.112.8:61097] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:58:07.000173 2025] [core:alert] [pid 5231:tid 5231] [client 45.138.53.215:60622] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 14:58:18.661516 2025] [core:alert] [pid 5202:tid 5202] [client 45.138.53.215:37664] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 15:05:30.748100 2025] [core:alert] [pid 5201:tid 5201] [client 45.138.53.215:51078] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 15:08:16.194961 2025] [core:alert] [pid 5231:tid 5231] [client 54.209.250.207:49598] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 15:08:16.702255 2025] [core:alert] [pid 5202:tid 5202] [client 54.209.250.207:57167] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: https://natewest.jp/
[Wed Jan 01 15:08:20.844827 2025] [core:alert] [pid 5349:tid 5349] [client 54.209.250.207:41484] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 15:09:00.776160 2025] [core:alert] [pid 5200:tid 5200] [client 4.151.218.216:52968] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 15:15:27.254210 2025] [core:alert] [pid 5231:tid 5231] [client 133.242.174.119:60284] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 15:17:51.822849 2025] [core:alert] [pid 5200:tid 5200] [client 218.219.168.196:58216] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 15:17:54.827782 2025] [core:alert] [pid 5976:tid 5976] [client 84.54.105.133:64064] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 15:19:02.708095 2025] [core:alert] [pid 5976:tid 5976] [client 84.54.105.132:50444] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 15:19:02.870593 2025] [core:alert] [pid 5199:tid 5199] [client 84.54.105.132:50448] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 15:19:05.578319 2025] [core:alert] [pid 5201:tid 5201] [client 84.54.105.132:50450] /var/www/html/.htaccess: Require not allowed in <Files> context, referer: http://34.97.31.233/
[Wed Jan 01 15:37:03.285832 2025] [core:alert] [pid 6838:tid 6838] [client 45.134.79.105:50080] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 15:37:04.972622 2025] [core:alert] [pid 6839:tid 6839] [client 45.134.79.105:50082] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 15:42:23.555738 2025] [core:alert] [pid 5976:tid 5976] [client 207.102.138.19:47878] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 15:45:25.489428 2025] [core:alert] [pid 5199:tid 5199] [client 126.83.112.8:31565] /var/www/html/.htaccess: Require not allowed in <Files> context
[Wed Jan 01 15:50:04.433207 2025] [mpm_prefork:notice] [pid 4711:tid 4711] AH00170: caught SIGWINCH, shutting down gracefully
[Wed Jan 01 15:50:06.495301 2025] [mpm_prefork:notice] [pid 7074:tid 7074] AH00163: Apache/2.4.62 (Debian) OpenSSL/1.1.1w configured -- resuming normal operations
[Wed Jan 01 15:50:06.495392 2025] [core:notice] [pid 7074:tid 7074] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 01 15:50:21.136155 2025] [core:alert] [pid 7075:tid 7075] [client 126.83.112.8:30908] /var/www/html/.htaccess: Require not allowed in <Files> context

I will be heading to bed after this and will check things in the morning. Thank you again.

Osiris · January 1, 2025, 4:13pm

Most are just alerts.. I don't think those are causing internal server errors..

That said, there also are not many relevant errors. Some are just from some scripts trying to exploit something (and fail). Those proxy_fcgi:error are worrisome though.. Although I can't understand why those errors show up sometimes, but not when Apache is returning an internal server error. And why only when using HTTPS..?

I don't really understand.. Maybe those alerts might give a clue and maybe the issue is in /var/www/html/.htaccess?

natew · January 2, 2025, 3:47am

Here are the contents of .htaccess -

# Wordfence WAF
<Files ".user.ini">
<IfModule mod_authz_core.c>
        Require all denied
</IfModule>
<IfModule !mod_authz_core.c>
        Order deny,allow
        Deny from all
</IfModule>
</Files>

# END Wordfence WAF

Wordfence is a Wordpress security plugin I installed. It has a firewall, but it's supposed to be in training mode for the first week, not active. Maybe I should have set it up after getting an SSL certificate though? Maybe it would be good if I gave a blow-by-blow of what happened.

Step taken	Site status
Created new Google Cloud VM instance with Wordpress Click to Deploy, set a static external IP, created the DNS records
Removed unused Wordpress themes and plugins, installed Wordfence and let it run its firewall configuration
Logged into SSH and installed stepd, checked for older versions of certbot and step installed certbot
Ran the bot (as printed out in first post), returned to website to change Wordpress's URL settings to https

MikeMcQ · January 2, 2025, 4:16am

I would comment out the lines in that .htaccess file and see what happens.

I am also puzzled but the problem is not unique to HTTPS. I see a similar problem as @Osiris did but using HTTP. Using the domain name in the URL gets a different reply than when using the IP address. Since you only have one port 80 VirtualHost it normally would handle all incoming requests.

There must be something else interfering with inbound requests to your server. Other than this .htaccess is there anything else like a firewall or router than might be running Apache "in front of" your Apache server? And that would only be involved when the inbound request used the domain name?

As further debug info, I just sent these two requests. Do either or both show up in your access.log for the VirtualHost for port 80? Note the unique names and timestamps of the response

curl -i http://34.97.31.233/Test404UsingIP
HTTP/1.1 404 Not Found
Date: Thu, 02 Jan 2025 04:22:16 GMT
Server: Apache
Content-Length: 196

curl -i http://natewest.jp/Test404UsingDomainName
HTTP/1.1 301 Moved Permanently
Date: Thu, 02 Jan 2025 04:22:44 GMT
Server: Apache
Location: https://natewest.jp/Test404UsingDomainName
Content-Length: 250

MikeMcQ · January 2, 2025, 5:04am

Ouch. My previous comment about the different response using HTTP is expected. Your redirects looked specifically for the hostname. And, incoming with IP address would not redirect. So, my bad.

I would have deleted the post entirely except you marked it as the Solution so maybe something in there led you to find it anyway. Let us know what that was and we'll mark that as the Solution. That would be better than my misleading comments - sorry

It seems you found it so probably the .htaccess file was related. And, checking the access logs is sometimes helpful to ensure requests arrive as intended. It is the 404 vs 301 that is incorrect.

natew · January 2, 2025, 5:13am

Commenting out the .htaccess content worked, thank you Osiris and MikeMcQ for finding the root cause! MikeMcQ, I found both requests in the access.log, if that is helpful.

My apologies that I thought this was caused by certbot, but it seems it was caused by Wordfence instead - thank you for helping.

Incidentally, I tested removing Wordfence and all configurations completely and reinstalling, and as soon as I ran the 'configure firewall' step again - boom, same 500 Internal Error. I will be checking with Wordfence manual and support if necessary to learn why its firewall is causing this. I can reply here with any info I find if anyone would like that!

natew · January 2, 2025, 6:32am

Thank you again, everyone! I'm up and running with Wordfence firewall enabled as well. I got to the root of the problem by searching more about the .htaccess: Require not allowed in <Files> context error, and found out that apparently it wasn't happy with Wordfence's Require all denied rule in .htaccess. I needed to add AuthConfig to the AllowOverride in the site config (for me, wordpress-https.conf). In case it helps anyone searching for this problem later, this is what I did -

In the site conf, make sure that AllowOverride includes AuthConfig. Mine now says AllowOverride FileInfo AuthConfig
Restart apache. For my system, sudo systemctl restart apache2
See if the site loads, if not, check again for the "Require not allowed" error

For reference,

https://httpd.apache.org/docs/2.4/mod/mod_authz_core.html#require

system · February 1, 2025, 6:33am

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

Topic		Replies	Views
Certbot failed to authenticate some domains Help	3	73	September 22, 2024
Error on line 46 Help	7	799	October 8, 2019
Can't access wordpress after certbot install Server	3	1599	April 12, 2017
Just installed Let's Encrypt and got untrusted certificate Help	17	1448	August 20, 2022
NOOB here, errors on certbot renew with wordpress Help	9	424	April 28, 2024

500 Internal Error after running certbot, perhaps pointed to wrong virtual host conf file?

Related topics