NodeBalancer + Apache + SSL + Wordpress -- site not rendering completely
I have two Linodes behind a NodeBalancer. Over port 80, everything works fine. Over port 443, the SSL connection seems to work fine according to the Qualys SSL Site Test (
The connection between the NodeBalancer and the Linode is over port 80, but on the client, connecting over HTTPS, I assume what is happening is that the browser is detecting some content as not secure and so not loading it.
I tried a pass-through on the NodeBalancer setup (using TCP as the protocol), but that seemed to not work at all.
Is anyone else using this combination successfully? Is there an Apache or Wordpress configuration change that can be made to allow the Wordpress site to function normally behind a NodeBalancer + SSL?
Thanks!
3 Replies
A badly made template (wordpress or other cms) would have protocol-specific URL's, which results in what you experience, a site working fine over http but appears broken over https, because mixed content is not allowed by browsers (and correctly so).
The solution, is to fix the template, so the produced URL's are protocol-agnostic.
What would be even better, is to completely stop serving unencrypted content and redirect users to https, especially now with free certificates, there is absolutely no reason why you should be serving unencrypted content.
I appreciate the input!
blog post about this issue
The summary is, WordPress supports SSL but it can't detect that you're trying to use it when you're using a NodeBalancer. Thus, you need to manually tell it in the config.