Questions[bitnami](server)

I have a AWS Lightsail Bitnami LAMP 7.4.27-16 machine that every night stops responding at random time. I installed LetsEncrypt certificate and vsftpd for a new specific ftp user.

On the machine all seems working properly. The server is listening, cpu is ok, ram is ok, I can connect to it by SSH. Apache and MariaDb services are running. Only the website load infinitely (http or https).

These are the last access_log lines:

45.95.169.230 - - [11/Mar/2022:02:59:24 +0000] "GET //website/wp-includes/wlwmanifest.xml HTTP/1.1" 404 7120
45.95.169.230 - - [11/Mar/2022:02:59:25 +0000] "GET //wp/wp-includes/wlwmanifest.xml HTTP/1.1" 404 7115
45.95.169.230 - - [11/Mar/2022:02:59:25 +0000] "GET //news/wp-includes/wlwmanifest.xml HTTP/1.1" 404 7117
45.95.169.230 - - [11/Mar/2022:02:59:25 +0000] "GET //2020/wp-includes/wlwmanifest.xml HTTP/1.1" 404 7117
45.95.169.230 - - [11/Mar/2022:02:59:25 +0000] "GET //2019/wp-includes/wlwmanifest.xml HTTP/1.1" 404 7117
45.95.169.230 - - [11/Mar/2022:02:59:25 +0000] "GET //shop/wp-includes/wlwmanifest.xml HTTP/1.1" 404 7117
45.95.169.230 - - [11/Mar/2022:02:59:26 +0000] "GET //wp1/wp-includes/wlwmanifest.xml HTTP/1.1" 404 7116
45.95.169.230 - - [11/Mar/2022:02:59:26 +0000] "GET //test/wp-includes/wlwmanifest.xml HTTP/1.1" 404 7117
45.95.169.230 - - [11/Mar/2022:02:59:26 +0000] "GET //wp2/wp-includes/wlwmanifest.xml HTTP/1.1" 404 7116
45.95.169.230 - - [11/Mar/2022:02:59:26 +0000] "GET //site/wp-includes/wlwmanifest.xml HTTP/1.1" 404 7117
45.95.169.230 - - [11/Mar/2022:02:59:26 +0000] "GET //cms/wp-includes/wlwmanifest.xml HTTP/1.1" 404 7116
45.95.169.230 - - [11/Mar/2022:02:59:27 +0000] "GET //sito/wp-includes/wlwmanifest.xml HTTP/1.1" 404 7117
3.208.15.15 - - [11/Mar/2022:03:09:30 +0000] "GET / HTTP/1.1" 301 234
3.208.15.15 - - [11/Mar/2022:03:09:31 +0000] "GET / HTTP/1.1" 200 2760

and these the error_log:

[Thu Mar 10 00:00:04.415191 2022] [mpm_event:notice] [pid 31589:tid 140507846433664] AH00493: SIGUSR1 received.  Doing graceful restart
[Thu Mar 10 00:00:04.442377 2022] [mpm_event:notice] [pid 31589:tid 140507846433664] AH00489: Apache/2.4.52 (Unix) OpenSSL/1.1.1d configured -- resuming normal operations
[Thu Mar 10 00:00:04.442392 2022] [core:notice] [pid 31589:tid 140507846433664] AH00094: Command line: '/opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf'
[Fri Mar 11 00:00:03.441124 2022] [mpm_event:notice] [pid 31589:tid 140507846433664] AH00493: SIGUSR1 received.  Doing graceful restart
[Fri Mar 11 00:00:03.458966 2022] [mpm_event:notice] [pid 31589:tid 140507846433664] AH00489: Apache/2.4.52 (Unix) OpenSSL/1.1.1d configured -- resuming normal operations
[Fri Mar 11 00:00:03.458981 2022] [core:notice] [pid 31589:tid 140507846433664] AH00094: Command line: '/opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf'
[Fri Mar 11 03:09:55.831036 2022] [ssl:error] [pid 30732:tid 140507162339072] [client 3.208.15.15:33716] AH02042: rejecting client initiated renegotiation

No error in MySql log.

What can I do now? There are some commands or logs to check?

I have searched many site and also Bitnami support pages and I was unable to find an answer to this issue I see. I cannot post on Bitnami support cummunity as a new topic as I have just joined :/

I have summarised as best I can but there is a lot of detail because I have added all the relevant configuration files.

I am running Wordpress MultiSite application running on AWS Lightsail Linux instance launched using Bitnami Installation System Package. My site is running fine and I have also successfully added and configured an Lets Encrypt SSL certificate. I can send both HTTP and HTTPS requests for my root and subdomain and see 200 OK in both curl types. Therefore the SSL certificate configured on port 443 is working as expected.

curl -L -svo /dev/null https://trevorwalsh.art

The only redirect currently configured on Apache is redirecting requests subdomain 'www.trevorwalsh.art' ----> 'trevorwalsh.art'. This is added when setting up this WordPress multisite.

curl -L -svo /dev/null www.trevorwalsh.art

I verified that for Wordpress MultiSite, the process for adding the Lets Encrypt SSL cert does currently allow for the configuration of HTTP to HTTPS redirection in Apache unlike in if using standard Wordpress and Apache. Therefore I researched and following the guidance seen in the following Bitnami doc. My stack is 'Approach A: Bitnami Installations Using System Packages' [1] Force HTTPS Redirection With Apache:-

• https://docs.bitnami.com/aws/apps/wordpress-multisite/administration/force-https-apache/

I have added the contents of each relevant file that are required to be edited below:-

File --> /opt/bitnami/apache2/conf/bitnami/bitnami.conf

# Let Apache know we're behind a SSL reverse proxy
SetEnvIf X-Forwarded-Proto https HTTPS=on

<VirtualHost _default_:80>
   DocumentRoot "/opt/bitnami/apache/htdocs"
# BEGIN: Configuration for letsencrypt 
   Include "/opt/bitnami/apps/letsencrypt/conf/httpd-prefix.conf"
   RewriteEngine On
   RewriteCond %{HTTPS} !=on
   RewriteCond %{HTTP_HOST} !^(localhost|127.0.0.1)
   RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]   
# END: Configuration for letsencrypt
 <Directory "/opt/bitnami/apache/htdocs">
   Options Indexes FollowSymLinks
   AllowOverride All
   Require all granted
 </Directory>

 # Error Documents
 ErrorDocument 503 /503.html
 </VirtualHost>

 Include "/opt/bitnami/apache/conf/bitnami/bitnami-ssl.conf"

File --> /opt/bitnami/apache2/conf/bitnami/bitnami-ssl.conf

<IfModule !ssl_module>
  LoadModule ssl_module modules/mod_ssl.so
</IfModule>

Listen 443
SSLProtocol all -SSLv2 -SSLv3
SSLHonorCipherOrder on
SSLCipherSuite "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH !aNULL !eNULL !LOW !3DES !MD5 !EX$
SSLPassPhraseDialog  builtin
SSLSessionCache "shmcb:/opt/bitnami/apache/logs/ssl_scache(512000)"
SSLSessionCacheTimeout  300

<VirtualHost _default_:443>
   DocumentRoot "/opt/bitnami/apache/htdocs"
   SSLEngine on
   SSLCertificateFile "/opt/bitnami/apache/conf/trevorwalsh.art.crt"
   SSLCertificateKeyFile "/opt/bitnami/apache/conf/trevorwalsh.art.key"
# BEGIN: Configuration for letsencrypt
   Include "/opt/bitnami/apps/letsencrypt/conf/httpd-prefix.conf"
   RewriteEngine On
   RewriteCond %{HTTPS} !=on
   RewriteCond %{HTTP_HOST} !^(localhost|127.0.0.1)
   RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L] 
# END: Configuration for letsencrypt
   <Directory "/opt/bitnami/apache/htdocs">
     Options Indexes FollowSymLinks
     AllowOverride All
     Require all granted
   </Directory>

  # Error Documents
   ErrorDocument 503 /503.html
 </VirtualHost>

File --> /opt/bitnami/apache2/conf/vhosts/00_status-vhost.conf

<VirtualHost 127.0.0.1:80>

  RewriteEngine On
  RewriteCond %{HTTPS} !=on
  RewriteCond %{HTTP_HOST} !^(localhost|127.0.0.1)
  RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]

 ServerName status.localhost
  <Location /server-status>
    Require local
    SetHandler server-status
  </Location>

 </VirtualHost>

I added the correct 'ServerName' and 'ServerAlias' root domain and subdomain values based on the guidance seen in the this doc:- [2] Configure Blogs For Different Domains With Different SSL Certificates:-

• https://docs.bitnami.com/aws/apps/wordpress-multisite/administration/use-different-ssl-certificates/

File --> /opt/bitnami/apache2/conf/vhosts/wordpress-https-vhost.conf

<VirtualHost 127.0.0.1:443 _default_:443>
  ServerName trevorwalsh.art
  ServerAlias *.trevorwalsh.art
  SSLEngine on
  SSLCertificateFile "/opt/bitnami/apache/conf/trevorwalsh.art.crt"
  SSLCertificateKeyFile "/opt/bitnami/apache/conf/trevorwalsh.art.key"
  DocumentRoot /opt/bitnami/wordpress
# BEGIN: Configuration for letsencrypt
  Include "/opt/bitnami/apps/letsencrypt/conf/httpd-prefix.conf"
  RewriteEngine On
  RewriteCond %{HTTPS} !=on
  RewriteCond %{HTTP_HOST} !^(localhost|127.0.0.1)
  RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]
# END: Configuration for letsencrypt
  <Directory "/opt/bitnami/wordpress">
    Options -Indexes +FollowSymLinks -MultiViews
    AllowOverride None
    Require all granted
    # BEGIN WordPress fix for plugins and themes
    # Certain WordPress plugins and themes do not properly link to PHP files because of symbolic links
    # https://github.com/bitnami/bitnami-docker-wordpress-nginx/issues/43
    RewriteEngine On
    RewriteRule ^bitnami/wordpress(/.*) $1 [L]
    # END WordPress fix for plugins and themes
    # BEGIN nip.io redirection
    RewriteEngine On
    RewriteCond %{HTTP_HOST} ^([0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3})(:[0-9]{1,5})?$
    RewriteRule ^/?(.*) %{REQUEST_SCHEME}://%1.nip.io%2/$1 [L,R=302,NE]
    # END nip.io redirection
    # BEGIN WordPress Multisite
    # Using subdomain network type: https://wordpress.org/support/article/htaccess/#multisite
    RewriteEngine On
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    # add a trailing slash to /wp-admin
    RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ - [L]
    RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
    RewriteRule ^(.*\.php)$ $1 [L]
    RewriteRule . index.php [L]
    # END WordPress Multisite
  </Directory>
  Include "/opt/bitnami/apache/conf/vhosts/htaccess/wordpress-htaccess.conf"
 </VirtualHost>

File --> /opt/bitnami/apache2/conf/vhosts/wordpress-vhost.conf

<VirtualHost 127.0.0.1:80 _default_:80> ServerAlias * DocumentRoot /opt/bitnami/wordpress
 # <VirtualHost _default_:80>  # BEGIN: Configuration for letsencrypt
 # BEGIN: Configuration for letsencrypt
     Include "/opt/bitnami/apps/letsencrypt/conf/httpd-prefix.conf"
     RewriteEngine On
     RewriteCond %{HTTPS} !=on
     RewriteCond %{HTTP_HOST} !^(localhost|127.0.0.1)
     RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]  
# END: Configuration for letsencrypt
   <Directory "/opt/bitnami/wordpress">
     Options -Indexes +FollowSymLinks -MultiViews
     AllowOverride None
     Require all granted
     # BEGIN WordPress fix for plugins and themes
     # Certain WordPress plugins and themes do not properly link to PHP files because of symbolic links
     # https://github.com/bitnami/bitnami-docker-wordpress-nginx/issues/43
     RewriteEngine On
     RewriteRule ^bitnami/wordpress(/.*) $1 [L]
     # END WordPress fix for plugins and themes
     # BEGIN nip.io redirection
     RewriteEngine On
     RewriteCond %{HTTP_HOST} ^([0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3})(:[0-9]{1,5})?$
     RewriteRule ^/?(.*) %{REQUEST_SCHEME}://%1.nip.io%2/$1 [L,R=302,NE]
     # END nip.io redirection
     # BEGIN WordPress Multisite
     # Using subdomain network type: https://wordpress.org/support/article/htaccess/#multisite
     RewriteEngine On
     RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
     RewriteBase /
     RewriteRule ^index\.php$ - [L]
     # add a trailing slash to /wp-admin
     RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
     RewriteCond %{REQUEST_FILENAME} -f [OR]
     RewriteCond %{REQUEST_FILENAME} -d
     RewriteRule ^ - [L]
     RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
     RewriteRule ^(.*\.php)$ $1 [L]
     RewriteRule . index.php [L]
     # END WordPress Multisite
   </Directory>
   Include "/opt/bitnami/apache/conf/vhosts/htaccess/wordpress-htaccess.conf"
 </VirtualHost>

Lastly, I verified that I had the correct parameters in the 'wordpress-htaccess.conf' file seen below after reviewing the information seen in the following doc:- [3] Understand Default .Htaccess File Configuration - Add A New Section In The .Htaccess File

• https://docs.bitnami.com/ibm/infrastructure/lapp/administration/use-htaccess/#add-a-new-section-in-the-htaccess-file-when-installing-a-plugin

File --> /opt/bitnami/apache2/conf/vhosts/htaccess/wordpress-htaccess.conf

<Directory "/opt/bitnami/wordpress/wp-content/plugins/akismet">
# <Directory "/opt/bitnami/wordpress">
  # Only allow direct access to specific Web-available files.

  # Apache 2.2
  <IfModule !mod_authz_core.c>
        Order Deny,Allow
        Deny from all
  </IfModule>

  # Apache 2.4
  <IfModule mod_authz_core.c>
        Require all denied
  </IfModule>

  # Akismet CSS and JS
  <FilesMatch "^(form\.js|akismet\.js|akismet\.css)$">
        <IfModule !mod_authz_core.c>
                Allow from all
        </IfModule>
        
        <IfModule mod_authz_core.c>
                Require all granted
        </IfModule>
  </FilesMatch>

  # Akismet images
  <FilesMatch "^logo-(a|full)-2x\.png$">
        <IfModule !mod_authz_core.c>
                Allow from all
        </IfModule>
        
        <IfModule mod_authz_core.c>
                Require all granted
        </IfModule>
  </FilesMatch>
</Directory>

However I can not get the Forcing HTTP/HTTPS Redirect to work and after attempting to resolve this myself I need help as I maybe missing something here.

Thanks in advance for your help.

Exporting a custom image to Cloud Storage I did this, then downloaded the .VMDK file one large 30gb file.

I have VMware workstation Pro 15.5 I am new to this whole VM thing. I managed to make an image of my GCP webserver instance and then saved it in my bucket to a .VMDK file and downloaded it.

I get so far as "Clock Source: Switched clocksource to tsc" Then it stalls the Virtual Machine.

It is a Bitnami stack of Debian 10, wordpress pro, ngnix and lets encrypt.

I have 5 instances with google cloud, all running WordPress by bitnami. At 11am today, all websites are inaccessible...that's weird because I didn't alter anything and suddenly, not 1 website, but all websites down at the same time. Did try to stop and start again the instances, nothing work...SSH and FTP still accessible. I create a new instance with fresh WordPress, it is working. Any idea what happened to it?

**Case resolved. Malware found in the plugin directory. Please read my answer below for more info.

nohup <command> <arg> &

When I SSH into a Linux server, if I want to run a command and make sure that it will continue to run in the background after I logout from SSH, I will use the above commands.

Recently I am using a server stack called Bitnami Node.js stack. It is a self-contained software bundle. There is a node binary in the bin folder in the installation directory.

In the command line, I am able to use the node command to run my JS programs: node <js_program.js>. There is no problem.

But, I would like to continue to run the program after I logout from SSH. When I run nohup <installation_dir>/nodejs/bin/node <js_program.js> > <stdout.out> &, the program will run in the background. But, when I logout from SSH, the program will also terminate immediately. It seems that the nohup command has no effect in this case.

How can I fix this issue?