After Le'ts encrypt tool wordpress stop working (Awesome! WordPress is now installed.)

rubent 2021-02-18 09:16:43 UTC #1

Keywords: WordPress - AWS - Technical issue - Secure Connections (SSL/HTTPS)
bnsupport ID: 8647b0e3-62be-9948-c6cf-853af9d362b3
Description:
I used a marketplace bitnami template, installed my wordpress and it was working ok, also configured apache to have vhost, so I can use aslo a webemail, both of them where working ok on http. I used then the default tool Let's encrypt, after that wordpress stop working and now it's showing "Awesome! WordPress is now installed."

Thanks for your help

rubent 2021-02-18 09:58:39 UTC #2

I just found that if I run the script / tool again and force it to NOT re direct http to https, then both work (or more or less) as http works perfectly fine, however HTTP´s have removed images and lot of stuff from wordpress: "Enable HTTP to HTTPS redirection [Y/n]: N"

jcarmona 2021-02-18 10:39:12 UTC #3

Hi @rubent

Thanks for using Bitnami WordPress!

I was looking into your issue at the same time you were performing the changes. I was able to see the Bitnami Welcome Page but now I am able to access the site just fine.

My advice prior to your changes was that in the VirtualHost you have defined for your WordPress installation, you seem to have removed the one intended to handle HTTPs requests (listening on port 443). Hence, the site would show the default landing page as WordPress did not have a VirtualHost listening for incoming connection on that port:

apps/wordpress/conf/httpd-vhosts.conf

...
-#<VirtualHost *:443>
-#    ServerName wordpress.example.com
-#    ServerAlias www.wordpress.example.com
-#    DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"
-#    SSLEngine on
-#    SSLCertificateFile "/opt/bitnami/apps/wordpress/conf/certs/server.crt"
-#    SSLCertificateKeyFile "/opt/bitnami/apps/wordpress/conf/certs/server.key"
-#
-#    Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"
-#</VirtualHost>

+ <VirtualHost *:443>
+    ServerName sXXXXXXXXXadas.com
+    ServerAlias www.sXXXXXXXXXadas.com
+    DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"
+    SSLEngine on
+    SSLCertificateFile "/opt/bitnami/apache2/conf/sXXXXXXXXXadas.com.crt"
+    SSLCertificateKeyFile "/opt/bitnami/apache2/conf/sXXXXXXXXadas.com.key"
+
+    Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"
+</VirtualHost>

Best regards,
Jose Antonio Carmona

Was my answer helpful? Click on

rubent 2021-02-18 12:07:26 UTC #4

Hola Jose Antonio!

I created a vhost for the site:

<VirtualHost *:443>
    ServerName siempxxxxxadas.com
    ServerAlias www.siempxxxxxxdas.com
    DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"
    SSLEngine on
    SSLCertificateFile "/opt/bitnami/apache2/conf/sxxxxmadas.com.crt"
    SSLCertificateKeyFile "/opt/bitnami/apache2/conf/siexxxxomadas.com.key"

    Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"
</VirtualHost>

Without re-direct from http to https both work fine... is the redirect that makes both of them fail (re direct created through the tool)

rubent 2021-02-18 12:08:29 UTC #5

And now both of them work fine, individually, but if I use the tool and set to redirect http to https is when it fails...

jcarmona 2021-02-19 07:54:29 UTC #6

And now both of them work fine, individually, but if I use the tool and set to redirect http to https is when it fails...

I am sorry to hear that! Could you please indicate the steps you have followed? I'd like to reproduce this issue on my side and report the team if necessary.

It would also be nice if you could re-run the bnsupport-tool so that I can get the updated status of your configuration files. Nevertheless, we have a guide that deals with HTTP to HTTPs redirections, I think you may find it handy!

https://docs.bitnami.com/google/apps/wordpress/administration/force-https-apache/

Best regards,
Jose Antonio Carmona

Was my answer helpful? Click on

rubent 2021-02-19 10:09:28 UTC #7

Hola! New support number created now http and https enable but with no re-directs:

07b2389e-8497-e2bc-64f9-896755d1d814

As soon as I use Le'ts encrypyt and just change it to re-direct then it stops working, do you need another support run with the change?

Regards y gracias!!!

jcarmona 2021-02-19 10:54:07 UTC #8

Hi @rubent

Thanks for the new ID! I have been checking your configuration files and spotted some misconfigurations, here is my advice!

1) Modify your apache2/conf/bitnami/bitnami.conf . You are using a custom VirtualHost for your application, you don't need the rewrite rule in here. Though the directives look good to me, I reckon they should be placed outside of the Directory scope.

<VirtualHost _default_:80>
  DocumentRoot "/opt/bitnami/apache2/htdocs"
  ...
-       RewriteEngine On
-       RewriteCond %{HTTPS} !=on
-       RewriteRule ^/(.*) https://www.sieXXXXXXXXdas.com/$1 [R,L]

        </Directory>
...
</VirtualHost>

2) Add the Redirection directives to the actual VirtualHost, apps/wordpress/conf/httpd-vhosts.conf

<VirtualHost *:80>
    ServerName sieXXXXXXXXdas.com
    ServerAlias www.sieXXXXXXXXdas.com
    DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"
+   RewriteEngine On
+   RewriteCond %{HTTPS} !=on
+   RewriteRule ^/(.*) https://www.sieXXXXXXXXdas.com/$1 [R,L]
    Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"
</VirtualHost>
...

You can now check the configuration is okay by running:

$ sudo apachectl -t

If the syntax is okay, you are set to go with the changes and restart apache:

$ sudo /opt/bitnami/ctlscript.sh restart apache

Best regards,
Jose Antonio Carmona

Was my answer helpful? Click on

rubent 2021-02-19 11:38:34 UTC #9

Hello! interesting behaviour so, it's working but now you need to use www. if you don't then you get the www in front... while before it was working, so I suppose we need to force a re-direct as well?

jcarmona 2021-02-22 10:29:35 UTC #10

Hi @rubent

Yes, you can force the redirection to the www. domain. You can do that easily by adding the following modifications to the apache2/conf/bitnami/bitnami.conf file:

<VirtualHost _default_:80>
  DocumentRoot "/opt/bitnami/apache2/htdocs"
+ RewriteEngine On
+ RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
+ RewriteRule ^(.*)$ http://%1$1 [R=permanent,L]
  ...
</VirtualHost>

<VirtualHost _default_:443>
  DocumentRoot "/opt/bitnami/apache2/htdocs"
  SSLEngine on
+ RewriteEngine On
+ RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
+ RewriteRule ^(.*)$ https://%1$1 [R=permanent,L]
...
</VirtualHost>

Could you please try that (also check the syntax and restart the server) and report back ?

Best regards,
Jose Antonio Carmona

Was my answer helpful? Click on

rubent 2021-02-22 11:21:27 UTC #11

Hi, thanks for your help! Muchas gracias!, I´ve done the changes but still not working, new support generated: 9ea4a964-46c2-5762-3c9d-0bd346a6a9ff

Also I'm trying to set up a new wordpress instance on the server so created another vhost outside of apps/wordpress with a silly basic index.html however I got a permission denied: ForbiddenYou don't have permission to access this resource.
(DNS not set yet, so using a modification of local hosts to redirect).

Gracias de ante mano! Thansk beforehand

Kind regards.

rubent 2021-02-23 09:23:27 UTC #12

Any suggestions?.. I've tried couple of changes but nothing so far...

jcarmona 2021-02-23 11:17:16 UTC #13

Hi @rubent

I´ve done the changes but still not working,

I have reviewed my proposed changes and they are incorrect, so this should explain it! Let's get down to the root here so you can choose what is more convenient.

Your instance right now is defining 6 VirtualHosts, 2 of them in apache2/conf/bitnami/bitnami.conf (port 80 and 443) and another four custom ones in apps/wordpress/conf/httpd-vhosts.conf.

The ones defined in bitnami.conf are the default ones, that will handle any request incoming to that port and matching the server name defined in /opt/bitnami/apache2/conf/httpd.conf

...
ServerName siXXXXXXas.com:80
...

That is why accessing your site with no www. prefix (that is, matching the ServerName defined in that file) results in the Bitnami page. When using the www., the servername does not match and hence your application uses the custom VirtualHost configured with ServerAlias www.sieXXXXXXXXdas.com.

A) If you don't plan to use the default VirtualHost in bitnami.conf, you could simply change the /opt/bitnami/apache2/conf/httpd.conf so as not to match the domain:

...
- ServerName siXXXXXXas.com:80
+ ServerName localhost:80
...

B) You can also force the redirection from that default VirtualHost using my proposed changes before (notice the updated rules this time)

<VirtualHost _default_:80>
  DocumentRoot "/opt/bitnami/apache2/htdocs"
+ RewriteEngine On
+ RewriteCond %{HTTP_HOST} !(^www) [NC]
+ RewriteRule ^/(.*) http://www.sieXXXXXXXXdas.com/$1 [R=permanent,L]
  ...
</VirtualHost>

<VirtualHost _default_:443>
  DocumentRoot "/opt/bitnami/apache2/htdocs"
+ RewriteEngine On
+ RewriteCond %{HTTP_HOST} !(^www) [NC]
+ RewriteRule ^/(.*) https://www.sieXXXXXXXXdas.com/$1 [R=permanent,L]
  SSLEngine on
...
</VirtualHost>

Basically, this means that every requests handled by these VirtualHosts that do not start with the www. prefix will be redirected to www.sieXXXXXXXXdas.com/whatever-path

Remind to test your syntax before restarting apache

Also I'm trying to set up a new wordpress instance on the server so created another vhost outside of apps/wordpress with a silly basic index.html however I got a permission denied: ForbiddenYou don't have permission to access this resource.

Would you mind opening a new ticket for this? We usually try to have single-themed threads so that users in the community can find answers to specific topics easier. We will be more than happy to provide you with assistance there as well .

Could you please try either proposed changes?

Best regards,
Jose Antonio Carmona

Was my answer helpful? Click on

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!