Mixed Content Issue with AWS ELB + ACM + Subfolder

Keywords: WordPress - AWS - Technical issue - Secure Connections (SSL/HTTPS)

bnsupport ID: 8d519730-ac5c-5ea4-1055-624dfdbfa723

bndiagnostic output:

? Apache: Found possible issues
? Resources: Found possible issues
? Php: Found possible issues
https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-errors-apache/
https://docs.bitnami.com/bch/apps/moodle/troubleshooting/deny-connections-bots-apache/
https://docs.bitnami.com/installer/faq/linux-faq/administration/increase-memory-linux/
https://docs.bitnami.com/general/apps/wordpress/configuration/configure-phpfpm-processes/

bndiagnostic failure reason: The suggested guides are not related with my issue

Description:
Hi there,

I’m trying to install a WordPress for a subfolder on my domain.

I’ve launched a Single WordPress installation on Lightsail and with route53 added the IP of the new Bitnami instance.

As you can see here (https://weshoot.it/viaggi-fotografici/) there is an issue of mixed content.

I’ve tried several guides to change the wp-config by using my domain, with or without HTTPS.

There is no CDN.

I’ve tried also this tutorial (force-https-apache) to force https but I guess the ACM is enough and shouldn’t be forced.

Note that all the other wordpress assets on the domain are working fine such as the
https://MYDOMAIN/blog

This is what is on the config file (/opt/bitnami/apps/wordpress/htdocs/wp-c
onfig.php)

define(‘WP_SITEURL’, ‘http: //MYDOMAIN/viaggi-fotografici/’);
define(‘WP_HOME’, ‘http: //MYDOMAIN/viaggi-fotografici/’);

At this point I don’t know what else we can do.

Hi @lucamicheli,

Thanks for using Bitnami. We have a guide for configuring WordPress with an ELB load balancer and HTTPS support, can you check it?

https://docs.bitnami.com/aws/how-to/configure-elb-ssl-aws/

The wp-config.php file is almost fine from my point of view, although you will need to set the WP_SITEURL and WP_HOME values with https://. I also don’t see any Apache configuration for redirecting HTTP requests to HTTPS as mentioned in our guide. Can you check you are not missing any step there?