Mixed Content: http elements on https website

Hi @ernst1234,

Thank you for contacting us! In this case, I’d suggest checking your WordPress settings and checking that there’s no mismatch in your URLs, and they are set to HTTPS. We always use those standard URL settings, so this could be causing the warning.

I hope this helps! Could you please let me know if you have any questions?

Thanks! ??

Hi Manuel

Thanks for the response.

All settings on my site are https. Specifically “home” and “siteurl” settings. But also all other settings in the db related to url of our site. I doubt there is an http hardcoded in our php or other files.

Look, it must be your code that is referencing that png. And if the reference is relative to siteurl, then it should not give an issue. But it must be enforcing http somehow. Where might it be getting that http url from? If you can tell me specifically how this is picked up, then I’ll try and find it. Otherwise I’ll need to search through your plugin code to locate why it is asking for an http url instead of https.

If you cannot determine this, then it’s OK.

We did recently migrate the site and I guess some issue crept in with this migration causing the above problem.

Thank you

Problem solved:

Note: It could well be, that none of the below was necessary to fix the problem for others. The reason might just have been that I had connected to the facebook page source in Facebook Feed Plugin Settings, when our site was still http. And then we moved to https. But either way, the below worked for us.

What I did was edit wp-config.php:
1) Regenerated new salts/keys for the auth section.
2) Added:

define( 'WP_DEBUG', false );
define( 'WP_SITEURL', 'https://YOUR_DOMAIN/' );
define( 'WP_HOME', 'https://YOUR_DOMAIN/' );
define( 'WP_CONTENT_URL', 'https://YOUR_DOMAIN/wp-content');
define(' WP_CONTENT_DIR', '/bitnami/wordpress/wp-content');
define( 'WP_PLUGIN_DIR', '/bitnami/wordpress/wp-content/plugins' );
define( 'PLUGINDIR', 'bitnami/wordpress/wp-content/plugins' );
define( 'WP_PLUGIN_URL', 'https://YOUR_DOMAIN/wp-content/plugins' );

Replace YOUR_DOMAIN with your actual domain.

In other words, explicitly defined the correct urls and directories as there were issues reported of plugins not correctly resolving relative urls in wp-content and sub-directories. Specifically, /opt/bitnami/wordpress/wp-content is sym-linked to /bitnami/wordpress/wp-content, and some plugins experience issues with this.

Note, these definitions of …DIR, are JUST for bitnami and might not hold for future releases of their software even. Check docs and understand your wordpress folder structure. It may not be appropriate in other’s cases.

After the above was done, the Facebook Feed Plugin disconnected from the facebook page source and I just reconnected again in Settings. After the reconnect it worked fine and the mixed content warning/error disappeared.

This might help someone. Thank you.

• This reply was modified 2 years, 4 months ago by ernst1234.
• This reply was modified 2 years, 4 months ago by ernst1234.

Hi @ernst1234,

Thanks for the update here and we’re glad to hear you got the issue resolved! Thanks also for including the detailed information about how you resolved the problem. If you ever need any other assistance in the future, please don’t hesitate to let us know.

Best regards,

Louis

Hi @smashballoonlouis

I thought that had fixed it.
I even found further a further problem that may have been the cause – missing ca-bundle for SSL. That fixed issues on another plugin with https issues.

But the issue is back – it shows the mixed content warning again.

The stack that we are building on does not read .htaccess files in any wordpress directories or subdirectories. Do you make use of custom .htaccess files?

If not, any other ideas? It’s just the cff-avatar.png which has an http request instead of https.

I was starting to look at the code and trying to make sense of where the issue might originate. But I’m not a php guy, so it’s slow-going.

Please see if you can track this down.

Hi @ernst1234,

Sorry to hear the issue is still occurring. Could you temporarily disable the caching plugin on the site so we can see the site without any caching? We’ll be able to better investigate this further that way.

Best regards,

Louis

@smashballoonlouis
Hummingbird cache plugin disabled.
Also hit the “clear cache” before deactivating.
Let me know if anything else is needed.
We are not on a CDN or anything as yet, so there should not be other cache’s except browser caches.

Hi @ernst1234,

Thank you for doing that. We’re checking on the site and I’ll update you here as soon as I have more information.

Best regards,

Louis

Hi @ernst1234,

We checked on this, but we are not seeing the mixed content warning anymore. Could you take a look if you’re seeing the same thing on your end? If so, you could re-enable Hummingbird, check again, and if the warning returns you may want to reach out to Hummingbird’s support to see if they can provide some insight here.

If I can provide any further assistance, please don’t hesitate to let me know.

Best regards,

Louis

@smashballoonlouis
That’s interesting!
I re-enabled Hummingbird Cache and the problem re-appeared.
We’ll probably be moving to WP-Rocket anyways, so I’ll check if the problem persists after that change. And I’ll report back. We are not in a rush, so it may not be soon. But I’ll remember to update here for other users.

Thanks again.