Change URL from HTTP to HTTPS in Bitnami Wordpress

PlanetHurf 2017-02-14 18:59:19 UTC #1

Application name and version: Bitnami 4.6.1
- Is it an installer, cloud image or virtual machine?: AMI (Amazon AWS EC2)
- Operative system/Platform (Linux, Windows, OSX)(x86/x64): Linux
- Was it installed as the root user? YES

Hi, I am trying to setup HTTPS using Amazon Certificate - The certificate is in place and configured correctly ( via Elastic Load Balancing).

In the Bitnami Wordpress install, I am unable to change the site WordPress Address (URL) and Site Address (URL) from HTTP:// to HTTPS:// but I believe this is not done via the Admin Control Panel.

I have tried the solution, here: https://community.bitnami.com/t/change-http-to-https-in-my-wordpress-aws-bitnami-hosting/47246

Which advises adding:

  RewriteEngine On
    RewriteBase /
    
    # Redirect non-www to www (you can skip this block or substitute if with www to non-www)
    RewriteCond %{HTTP_HOST} .
    RewriteCond %{HTTP_HOST} !^www\. [NC]
    RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
    
    #SSL redirection
    RewriteCond %{HTTPS} !on
    RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
    
    # Rewrite index.php
    RewriteRule ^index\.php$ - [S=1]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]

To the directory block within /opt/bitnami/apps/wordpress/conf/httpd-app.conf

To to so, I replace the Existing Rewrite rules:

 RewriteEngine On
#RewriteBase /wordpress/
RewriteRule ^index\.php$ - [S=1]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . index.php [L]

With the code in the code block from that post.

With this in place (and after restarting apache). The redirect works (HTTP to HTTPS) and I get the green padlock showing certificate is verified by Amazon but I get a Too many redirects message in Safari and 'The page isn't redirecting properly - Firefox has detected that the server is redirecting the request for this address in a way that will never complete.' in Firefox.

So I believe I am close, but I assume this means I still need to replace the HTTP:// references within Wordpress?

I've also tried adding

define('WP_HOME','http://yourdomain.com');
define('WP_SITEURL','http://yourdomain.com');

to wp-config (though this is for Bitnami Azure, not AWS) as referenced, here: https://community.bitnami.com/t/how-to-change-wordpress-and-site-url-in-bitnami-wordpress-azure-installation/29633 because I need a solution.

Any assistance would be GRATEFULLY received.

Thanks

Force to https for Bitnami Wordpress on AWS

crhernandez 2017-02-15 12:10:29 UTC #2

Hi!

Option 1
It is possible that your problem is due to you replaced the existing rewrite rules in /opt/bitnami/apps/wordpress/conf/httpd-app.conf by the new that you found in the other topic. You should add the new code in the same file, but doesn't remove the existing rules. Can you try to add this code without deleting the existing rules?

Option 2

Add the following in the /opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf file inside the first VirtualHost directive, remembering to replace the DOMAIN placeholder with the actual domain name you wish to use:

<VirtualHost *:80>
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^/(.*) https://%{DOMAIN}/$1 [R,L]
...
</VirtualHost>
<VirtualHost *:443>
...
</VirtualHost>

Only specify your domain name in the /opt/bitnami/apps/wordpress/htdocs/wp-config.php file. Edit and replace the following lines as shown, remembering to replace the DOMAIN placeholder with the actual domain name you wish to use:

define('WP_SITEURL', 'http://' . $_SERVER['HTTP_HOST'] . '/');
define('WP_HOME', 'http://' . $_SERVER['HTTP_HOST'] . '/');

with

define('WP_SITEURL', 'https://DOMAIN/');                   
define('WP_HOME', 'https://DOMAIN/');

Do not forget restart the Apache server:
$ sudo /opt/bitnami/ctlscript.sh restart apache

This way, all HTTP traffic will be redirected to HTTPS.

I hope this information is useful for you. If you have any other question, please do not hesitate to let us know.

Best Regards,
Carlos R. Hernández

Redirection loop while forcing to HTTPS

Changing the wp-admin and wp-login.php URL

2 wordpress websites in one stack

bulgaru 2017-02-15 12:31:38 UTC #3

Hey, @PlanetHurf!

First of all - don't touch the wp-config settings. If you're not using WP instance under a folder directory, make sure there's no prefix inside those settings.

As for the settings inside the app conf, they are indeed correct. Make sure to restart apache. The most reliable way to test if everything works properly is using Incognito Mode or Private Browsing. SSL certificates may leave behind some cookies and it may take some time for the browser to adjust.

PlanetHurf 2017-02-15 14:36:44 UTC #4

Hi Carlos,

Thanks for your suggestions.
For clarity, I've included my original HTTPD-APP.CONF file, here (along with the modified version as you suggest in Option 1:
(Note: I restarted Apache Server in all instances and checked in incognito mode.)

ORIGINAL HTTPD-APP.CONF

RewriteEngine On
RewriteRule /<none> / [L,R]

<IfDefine USE_PHP_FPM>
    <Proxy "unix:/opt/bitnami/php/var/run/wordpress.sock|fcgi://wordpress-fpm" timeout=300>
    </Proxy>
</IfDefine>

<Directory "/opt/bitnami/apps/wordpress/htdocs">
    Options +MultiViews +FollowSymLinks
    AllowOverride None
    <IfVersion < 2.3 >
        Order allow,deny
        Allow from all
    </IfVersion>
    <IfVersion >= 2.3>
        Require all granted
    </IfVersion>
    
    

    <IfDefine USE_PHP_FPM>
       <FilesMatch \.php$>
         SetHandler "proxy:fcgi://wordpress-fpm"
       </FilesMatch>
    </IfDefine>
    
    RewriteEngine On
    #RewriteBase /wordpress/
    RewriteRule ^index\.php$ - [S=1]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . index.php [L]

    Include "/opt/bitnami/apps/wordpress/conf/banner.conf"
</Directory>

Include "/opt/bitnami/apps/wordpress/conf/htaccess.conf"

RESULT: Original. Works with HTTP only.

MODIFIED HTTPD-APP.CONF ( As suggested in OPTION 1)

RewriteEngine On
RewriteRule /<none> / [L,R]

<IfDefine USE_PHP_FPM>
    <Proxy "unix:/opt/bitnami/php/var/run/wordpress.sock|fcgi://wordpress-fpm" timeout=300>
    </Proxy>
</IfDefine>

<Directory "/opt/bitnami/apps/wordpress/htdocs">
    Options +MultiViews +FollowSymLinks
    AllowOverride None
    <IfVersion < 2.3 >
        Order allow,deny
        Allow from all
    </IfVersion>
    <IfVersion >= 2.3>
        Require all granted
    </IfVersion>
    
    

    <IfDefine USE_PHP_FPM>
       <FilesMatch \.php$>
         SetHandler "proxy:fcgi://wordpress-fpm"
       </FilesMatch>
    </IfDefine>
    
    RewriteEngine On
    #RewriteBase /wordpress/
    RewriteRule ^index\.php$ - [S=1]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . index.php [L]

RewriteEngine On
    RewriteBase /
    
    # Redirect non-www to www (you can skip this block or substitute if with www to non-www)
    RewriteCond %{HTTP_HOST} .
    RewriteCond %{HTTP_HOST} !^www\. [NC]
    RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
    
    #SSL redirection
    RewriteCond %{HTTPS} !on
    RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
    
    # Rewrite index.php
    RewriteRule ^index\.php$ - [S=1]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]

    Include "/opt/bitnami/apps/wordpress/conf/banner.conf"
</Directory>

Include "/opt/bitnami/apps/wordpress/conf/htaccess.conf"

RESULT: Causes redirect loop.

I'm not clear on Option 2, I'm afraid. I've attached original here.

ORIGINAL HTTPD-VHOSTS.CONF

<VirtualHost *:80>
    ServerName wordpress.example.com
    ServerAlias www.wordpress.example.com
    DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"
    
    Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"
</VirtualHost>

<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>

RESULT: Works with HTTP only.

I took Option 2 to mean, add:

RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^/(.*) https://%{www.mydomainname.com}/$1 [R,L

directly underneath:

<VirtualHost *:80>

and leave the rest the same?

Note: With Option 2, I haven't gone as far as editing wp-config.php as you suggest because I need to know I've understood the edit required to HTTPD-VHOSTS.CONF

Thanks for taking your time to assist me with this; I really appreciate it.

PlanetHurf 2017-02-15 14:39:55 UTC #5

Hi, Bulgaru,

Thanks for jumping in on this. I haven't touched the wp-config settings this time around. I just tried those yesterday out of desperation! I though it would be useful to share the code I'm using, in full, to make sure I'm executing the suggested changes correctly.

I have restarted the Apache server each time, and tested in Incognito mode.

I appreciate your assistance so far.

bulgaru 2017-02-15 14:43:21 UTC #6

Here you have two block starting with RewriteEngine On. Delete the first one. Restart Apache again.

PlanetHurf 2017-02-15 16:40:46 UTC #7

Hi,

This is what I tried originally (replacing the new/second block with the first) as I thought it odd to have two redirect blocks.

Here's the code I have just tried:

 RewriteEngine On
RewriteRule /<none> / [L,R]

<IfDefine USE_PHP_FPM>
    <Proxy "unix:/opt/bitnami/php/var/run/wordpress.sock|fcgi://wordpress-fpm" timeout=300>
    </Proxy>
</IfDefine>

<Directory "/opt/bitnami/apps/wordpress/htdocs">
    Options +MultiViews +FollowSymLinks
    AllowOverride None
    <IfVersion < 2.3 >
        Order allow,deny
        Allow from all
    </IfVersion>
    <IfVersion >= 2.3>
        Require all granted
    </IfVersion>
    
    

    <IfDefine USE_PHP_FPM>
       <FilesMatch \.php$>
         SetHandler "proxy:fcgi://wordpress-fpm"
       </FilesMatch>
    </IfDefine>
    
    RewriteEngine On
    RewriteBase /
    
    # Redirect non-www to www (you can skip this block or substitute if with www to non-www)
    RewriteCond %{HTTP_HOST} .
    RewriteCond %{HTTP_HOST} !^www\. [NC]
    RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
    
    #SSL redirection
    RewriteCond %{HTTPS} !on
    RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
    
    # Rewrite index.php
    RewriteRule ^index\.php$ - [S=1]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]

    Include "/opt/bitnami/apps/wordpress/conf/banner.conf"
</Directory>

Include "/opt/bitnami/apps/wordpress/conf/htaccess.conf"

Which results in the redirect loop:

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

This problem can sometimes be caused by disabling or refusing to accept cookies.

I have restarted Apache and tested in Incognito.

Thanks again for your assistance (and patience!)

bulgaru 2017-02-15 18:59:13 UTC #8

Hey!

Can you send me a private message with the domain you're using?

And can you post here the contents of the current 6 files:

/opt/bitnami/apps/wordpress/conf/httpd-app.conf
/opt/bitnami/apps/wordpress/conf/htaccess.conf
/opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf
/opt/bitnami/apps/wordpress/htdocs/wp-config.conf
/opt/bitnami/apache2/conf/bitnami/bitnami-apps-prefix.conf
/opt/bitnami/apache2/conf/bitnami/bitnami-apps-vhosts.conf

PlanetHurf 2017-02-15 20:05:24 UTC #9

Hi Bulgaru,

As requested, the contents of the six files:

I've enclosed any modifications I've made with [START MODIFICATION] [END MODIFICATION]

I've obscured password details.

and I'll PM domain now.

Thanks so much for your help.

HTTPD-APP.CONF

RewriteEngine On
RewriteRule /<none> / [L,R]

<IfDefine USE_PHP_FPM>
    <Proxy "unix:/opt/bitnami/php/var/run/wordpress.sock|fcgi://wordpress-fpm" timeout=300>
    </Proxy>
</IfDefine>

<Directory "/opt/bitnami/apps/wordpress/htdocs">
    Options +MultiViews +FollowSymLinks
    AllowOverride None
    <IfVersion < 2.3 >
        Order allow,deny
        Allow from all
    </IfVersion>
    <IfVersion >= 2.3>
        Require all granted
    </IfVersion>
    
    

    <IfDefine USE_PHP_FPM>
       <FilesMatch \.php$>
         SetHandler "proxy:fcgi://wordpress-fpm"
       </FilesMatch>
    </IfDefine>
    
   RewriteEngine On
    #RewriteBase /wordpress/
    RewriteRule ^index\.php$ - [S=1]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . index.php [L]

    Include "/opt/bitnami/apps/wordpress/conf/banner.conf"
</Directory>

Include "/opt/bitnami/apps/wordpress/conf/htaccess.conf"

——

HTACCESS.CONF

[START MODIFICATION}

## EXPIRES CACHING ##
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg "access plus 1 year"
ExpiresByType image/jpeg "access plus 1 year"
ExpiresByType image/gif "access plus 1 year"
ExpiresByType image/png "access plus 1 year"
ExpiresByType text/css "access plus 1 month"
ExpiresByType application/pdf "access plus 1 month"
ExpiresByType text/x-javascript "access plus 1 month"
ExpiresByType application/x-shockwave-flash "access plus 1 month"
ExpiresByType image/x-icon "access plus 1 year"
ExpiresDefault "access plus 2 days"
</IfModule>
## EXPIRES CACHING ##

<FilesMatch "\.(ttf|otf|eot|woff)$">
  <IfModule mod_headers.c>
    Header set Access-Control-Allow-Origin "*"
  </IfModule>
</FilesMatch>

[END MODIFICATION]


<Directory "/opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/akismet">
# 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-full-2x\.png$">
	<IfModule !mod_authz_core.c>
		Allow from all
	</IfModule>
	
	<IfModule mod_authz_core.c>
		Require all granted
	</IfModule>
</FilesMatch>
</Directory>
<Directory "/opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/versionpress">
# 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>

</Directory>
<Directory "/opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/versionpress/admin/public">
# Apache 2.2
<IfModule !mod_authz_core.c>
    Allow from all
</IfModule>

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

</Directory>

——

HTTPD-VHOSTS.CONF

<VirtualHost *:80>
    ServerName wordpress.example.com
    ServerAlias www.wordpress.example.com
    DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"
    
    Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"
</VirtualHost>

<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>

——

WP-CONFIG.CONF

<?php

[START MODIFICATION]

/** Enable W3 Total Cache */
define('WP_CACHE', true); // Added by W3 Total Cache

/**

[END MODIFICATION]

 * The base configuration for WordPress
 *
 * The wp-config.php creation script uses this file during the
 * installation. You don't have to use the web site, you can
 * copy this file to "wp-config.php" and fill in the values.
 *
 * This file contains the following configurations:
 *
 * * MySQL settings
 * * Secret keys
 * * Database table prefix
 * * ABSPATH
 *
 * @link https://codex.wordpress.org/Editing_wp-config.php
 *
 * @package WordPress
 */

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'bitnami_wordpress');

/** MySQL database username */
define('DB_USER', 'bn_wordpress');

/** MySQL database password */
define('DB_PASSWORD', ‘XXXXXXXXXX’);

/** MySQL hostname */
define('DB_HOST', 'localhost:3306');

/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');

/** The Database Collate type. Don't change this if in doubt. */
define('DB_COLLATE', '');

/**#@+
 * Authentication Unique Keys and Salts.
 *
 * Change these to different unique phrases!
 * You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
 * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
 *
 * @since 2.6.0
 */
define('AUTH_KEY', ‘XXXXXXXXXX’);
define('SECURE_AUTH_KEY', ‘XXXXXXXXXX’);
define('LOGGED_IN_KEY', ‘XXXXXXXXXX’);
define('NONCE_KEY', ‘XXXXXXXXXX’);
define('AUTH_SALT', ‘XXXXXXXXXX’);
define('SECURE_AUTH_SALT', ‘XXXXXXXXXX’);
define('LOGGED_IN_SALT', ‘XXXXXXXXXX’);
define('NONCE_SALT', ‘XXXXXXXXXX’);

/**#@-*/

/**
 * WordPress Database Table prefix.
 *
 * You can have multiple installations in one database if you give each
 * a unique prefix. Only numbers, letters, and underscores please!
 */
$table_prefix  = 'wp_';

/**
 * For developers: WordPress debugging mode.
 *
 * Change this to true to enable the display of notices during development.
 * It is strongly recommended that plugin and theme developers use WP_DEBUG
 * in their development environments.
 *
 * For information on other constants that can be used for debugging,
 * visit the Codex.
 *
 * @link https://codex.wordpress.org/Debugging_in_WordPress
 */
define('WP_DEBUG', false);

/* That's all, stop editing! Happy blogging. */
/**
 * The WP_SITEURL and WP_HOME options are configured to access from any hostname or IP address.
 * If you want to access only from an specific domain, you can modify them. For example:
 *  define('WP_HOME','http://example.com');
 *  define('WP_SITEURL','http://example.com');
 *
*/

define('WP_SITEURL', 'http://' . $_SERVER['HTTP_HOST'] . '/');
define('WP_HOME', 'http://' . $_SERVER['HTTP_HOST'] . '/');


/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
	define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');

define('WP_TEMP_DIR', '/opt/bitnami/apps/wordpress/tmp');


define('FS_METHOD', 'ftpext');
define('FTP_BASE', '/opt/bitnami/apps/wordpress/htdocs/');
define('FTP_USER', 'bitnamiftp');
define('FTP_PASS', ‘XXXXXXXXXX’);
define('FTP_HOST', '127.0.0.1');
define('FTP_SSL', false);



//  Disable pingback.ping xmlrpc method to prevent Wordpress from participating in DDoS attacks
//  More info at: https://wiki.bitnami.com/Applications/Bitnami_Wordpress#XMLRPC_and_Pingback

// remove x-pingback HTTP header
add_filter('wp_headers', function($headers) {
    unset($headers['X-Pingback']);
    return $headers;
});
// disable pingbacks
add_filter( 'xmlrpc_methods', function( $methods ) {
        unset( $methods['pingback.ping'] );
        return $methods;
});

——

BITNAMI-APPS-PREFIX.CONF

# Bitnami applications installed in a prefix URL
Include "/opt/bitnami/apps/wordpress/conf/httpd-prefix.conf"
Include "/opt/bitnami/apps/phpmyadmin/conf/httpd-prefix.conf"

——

BITNAMI-APPS-VHOSTS.CONF

# Bitnami applications installed in a Virtual Host

——

bulgaru 2017-02-15 20:12:26 UTC #10

I suggest the following changes:

BITNAMI-APPS-PREFIX.CONF (disable prefix)

# Bitnami applications installed in a prefix URL
# Include "/opt/bitnami/apps/wordpress/conf/httpd-prefix.conf"
Include "/opt/bitnami/apps/phpmyadmin/conf/httpd-prefix.conf"

BITNAMI-APPS-VHOSTS.CONF (enable vhosts conf)

Include "/opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf"

HTTPD-VHOSTS.CONF (substitute the placeholder with your domain w/ and w/o www)

HTACCESS.CONF (no changes, but i'm afraid caching setting don't work since they're not inside directory)

HTTPD-APP.CONF (uncomment the RewriteBase and remove prefix)

RewriteBase /

Restart Apache afterwards

PlanetHurf 2017-02-15 22:19:18 UTC #11

Ok. Thank you. I'll give that a go and report back here, tomorrow. Cheers.

PlanetHurf 2017-02-15 23:53:58 UTC #12

Hi, I've made your suggested changes as follows:

BITNAMI-APPS-PREFIX.CONF

# Bitnami applications installed in a prefix URL
# Include "/opt/bitnami/apps/wordpress/conf/httpd-prefix.conf"
Include "/opt/bitnami/apps/phpmyadmin/conf/httpd-prefix.conf"

BITNAMI-APPS-VHOSTS.CONF

# Bitnami applications installed in a Virtual Host
Include "/opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf"

HTTPD-VHOSTS.CONF

<VirtualHost *:80>
    ServerName mydomainname.com
    ServerAlias www.mydomainname.com
    DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"
    
    Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"
</VirtualHost>

<VirtualHost *:443>
    ServerName mydomainname.com
    ServerAlias www.mydomainname.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>

HTACCESS.CONF

NO CHANGES

HTTPD-APP.CONF

RewriteEngine On
RewriteRule /<none> / [L,R]

<IfDefine USE_PHP_FPM>
    <Proxy "unix:/opt/bitnami/php/var/run/wordpress.sock|fcgi://wordpress-fpm" timeout=300>
    </Proxy>
</IfDefine>

<Directory "/opt/bitnami/apps/wordpress/htdocs">
    Options +MultiViews +FollowSymLinks
    AllowOverride None
    <IfVersion < 2.3 >
        Order allow,deny
        Allow from all
    </IfVersion>
    <IfVersion >= 2.3>
        Require all granted
    </IfVersion>
    
    

    <IfDefine USE_PHP_FPM>
       <FilesMatch \.php$>
         SetHandler "proxy:fcgi://wordpress-fpm"
       </FilesMatch>
    </IfDefine>
    
   RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [S=1]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . index.php [L]

    Include "/opt/bitnami/apps/wordpress/conf/banner.conf"
</Directory>

Include "/opt/bitnami/apps/wordpress/conf/htaccess.conf"

I have restarted Apache and the site appears to be functioning as it was originally but it still does not redirect to HTTPS (and manually changing the URL to HTTPS displays a broken version of the site - as you might expect).

Am I missing a crucial element, perhaps? Do I need to do anymore with the SSL Redirection section? Or could this be something to do with the fact that I'm using An Amazon (AWS) Certificate (via Load Balancing) rather than an Apache Certificate?

I'm encouraged that the site is still working with the changes but I'm clearly still missing something.
Thanks again; I'm optimistic that the solution is not far away.

bulgaru 2017-02-16 06:09:24 UTC #13

In the app conf for some reason you've deleted the redirect block. Here's what's now:

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [S=1]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . index.php [L]

Here's how it should be:

RewriteEngine On
RewriteBase /

# Redirect non-www to www (you can skip this block or substitute if with www to non-www)
RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} !^www. [NC]
RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

#SSL redirection
RewriteCond %{HTTPS} !on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

# Rewrite index.php
RewriteRule ^index.php$ - [S=1]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

PlanetHurf 2017-02-16 09:17:01 UTC #14

Hi,

Thanks again for sticking with this.

I thought it may relate to this. I've adjusted this as follows:

    RewriteEngine On
RewriteRule /<none> / [L,R]

<IfDefine USE_PHP_FPM>
    <Proxy "unix:/opt/bitnami/php/var/run/wordpress.sock|fcgi://wordpress-fpm" timeout=300>
    </Proxy>
</IfDefine>

<Directory "/opt/bitnami/apps/wordpress/htdocs">
    Options +MultiViews +FollowSymLinks
    AllowOverride None
    <IfVersion < 2.3 >
        Order allow,deny
        Allow from all
    </IfVersion>
    <IfVersion >= 2.3>
        Require all granted
    </IfVersion>
    
    

    <IfDefine USE_PHP_FPM>
       <FilesMatch \.php$>
         SetHandler "proxy:fcgi://wordpress-fpm"
       </FilesMatch>
    </IfDefine>
    
   RewriteEngine On
RewriteBase /

# Redirect non-www to www (you can skip this block or substitute if with www to non-www)
RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} !^www. [NC]
RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

#SSL redirection
RewriteCond %{HTTPS} !on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

# Rewrite index.php
RewriteRule ^index.php$ - [S=1]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

    Include "/opt/bitnami/apps/wordpress/conf/banner.conf"
</Directory>

Include "/opt/bitnami/apps/wordpress/conf/htaccess.conf"

And restarted Apache. This does redirect to HTTPS:// but I get the redirect loop message as before.

Could this perhaps relate to W3TC caching settings?

bulgaru 2017-02-16 09:20:40 UTC #15

I'd actually suggest you disable the cache for the testing period.
I'd also like to check the redirect loop, when it occurs, so that i can check what is happening with redirecting.
Settings look good and it may be a caching issue.

PlanetHurf 2017-02-16 09:38:15 UTC #16

OK. W3TC Plugin disabled and cache cleared. "The plugin is currently disabled in community mode".

Changes as above back in place.

Redirect loop is showing now. You have the URL.

Thanks.

crhernandez 2017-02-20 12:37:55 UTC #17

Hi PlanetHurf,

Did you solve the problem? If it has not been solved, in what state are you currently?

Best regards,
Carlos R. Hernández

PlanetHurf 2017-02-20 12:56:32 UTC #18

Hi,

Yes, this has been resolved. The solution was to implement Certbot with LetsEncrypt certificate, with adjustments to our site configuration to suit this - @bulgaru provided invaluable assistance with this. Thanks for your support, once again!

crhernandez 2017-02-20 13:04:06 UTC #19

Perfect!
We are glad that you were able to fix the issue. Many thanks to @PlanetHurf and @bulgaru for the collaboration.

If you have any other questions, please do not hesitate to let us know.

Best regards,
Carlos R. Hernández

jkvandeg 2017-05-03 17:20:59 UTC #20

I'm currently having the same problem, however I have no idea how to locate my Bitnami.conf files.

As well, my site is no longer accessible (http) and the https form shows an error.

However, it does seem to be redirecting!

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