XF 1.3 SSL Issues

[CollinL]

Hi, I'm having some issues with getting my site to properly load in SSL. If you go to www.minetime.com, it's fine, but if you go to https://www.minetime.com, it appears to load in basic HTML.

I went in the Chrome development console and found the causes of the issue. http://i.imgur.com/KVaVBQk.png

The weird thing is that http content that is breaking my SSL (shown in the Imgur link) is locally hosted on my machine. (???)

If these were external links, I could just change them from http to https, but I have no idea how to go about making the site's local content load as HTTPS.

Any help is greatly appreciated and please let me know if you need more information. Thanks!

 

[Jake Bunce]

Flexile?

Try reverting the PAGE_CONTAINER template:

Admin CP -> Appearance -> Templates -> PAGE_CONTAINER

That has a chance of fixing the protocol mismatch.

 

[CollinL]

Flexile?

Try reverting the PAGE_CONTAINER template:

Admin CP -> Appearance -> Templates -> PAGE_CONTAINER

That has a chance of fixing the protocol mismatch.

I could only find one http link in there. It was a Facebook link which I changed to https. This didn't appear to fix the issue.

Is this what I need to edit?

 

[Jake Bunce]

I could only find one http link in there. It was a Facebook link which I changed to https. This didn't appear to fix the issue.

Is this what I need to edit?

I'm thinking base href which is in the head. That sets the base location for all relative locations in the page. If that is using the wrong protocol then it will result in those warnings.

The default template accounts for the protocol.

 

[Mike]

Indeed, the base tag is wrong but this should be generated from the code. What webserver are you using? You generally want to pass along a server variable that indicates that HTTPS is being used (see here for Nginx: http://forum.nginx.org/read.php?2,4949,4956).

 

[CollinL]

Indeed, the base tag is wrong but this should be generated from the code. What webserver are you using? You generally want to pass along a server variable that indicates that HTTPS is being used (see here for Nginx: http://forum.nginx.org/read.php?2,4949,4956).

I am using Apache, which is behind CloudFlare's nginx.

 

[CollinL]

I'm thinking base href which is in the head. That sets the base location for all relative locations in the page. If that is using the wrong protocol then it will result in those warnings.

The default template accounts for the protocol.

So, where it says "<meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1" />", should I just change the http to https?

 

[Mike]

It sounds like you aren't actually using SSL on your own server? (So CloudFlare is accessed via HTTPS but the proxy request back to you isn't?) If so, that would be the cause -- XenForo isn't actually being requested via HTTPS. Ideally, I would suggest making the request to your server with HTTPS (as you're half defeating the point of it if you're not).

 

[CollinL]

It sounds like you aren't actually using SSL on your own server? (So CloudFlare is accessed via HTTPS but the proxy request back to you isn't?) If so, that would be the cause -- XenForo isn't actually being requested via HTTPS. Ideally, I would suggest making the request to your server with HTTPS (as you're half defeating the point of it if you're not).

Yes, thank you. I was able to get it working.

 

[Xon]

Indeed, the base tag is wrong but this should be generated from the code. What webserver are you using? You generally want to pass along a server variable that indicates that HTTPS is being used (see here for Nginx: http://forum.nginx.org/read.php?2,4949,4956).

The nginx automatically populates a varaible so you don't need to use an if(). Adding something like the following the line to the wesbite's fastcgi_params file;

fastcgi_param  HTTPS  $https;

ref

https
“on” if connection operates in SSL mode, or an empty string otherwise