G’day sfpguru,
What do you get when you run the SSL Tests page?
Tools > SSL Tests
cheers,
Ross
It shows me this with each of 5 methods of HTTPS detection
“Your server environment shows this:
error”
Is there anything logged in your website logs?
Are you able to let me login to look? If so, please send login details via my support form (don’t post them here!)
cheers,
Ross
Very sorry, webaware, I can’t due to security policy of our company.
You mean apache logs? Only this after I ran HTTPS Test:
PHP Catchable fatal error: Object of class WP_Post could not be converted to string in /domain.com/wp-content/plugins/qtranslate/qtranslate_core.php on line 455
No worries.
It sounds like something is causing some error messages to be dumped into the AJAX calls. That’s probably the problem with the Settings page at least. You can try adding this to the wp-config.php file to stop that:
define('WP_DEBUG_DISPLAY', false);
The message suggests that it’s qtranslate, but I just tried running that with the SSL Insecure Content Fixer and didn’t have a problem, so I don’t know what could be causing it.
However, it should not be affecting the HTTPS test, which runs outside of WordPress. Can you see what the browser console shows in the AJAX response? Again, best to post it to my support form to keep it away from prying eyes.
Generally, you might want to try adding these lines to your wp-config.php file to see if that lets WordPress know when it’s loading on HTTPS. If it doesn’t work, remove the lines again.
if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] === 'https') {
$_SERVER['HTTPS'] = 'on';
}
cheers,
Ross
Doesn’t help. There still “error” in Tools page (with green tick after Tests Completed)
Have you any suggestions how to solve this, Ross?
cheers,
Mike
Did you get the green tick before? The green tick says that WordPress can detect SSL. Has your problem with jQuery scripts been resolved now?
The errors in the Tools > SSL Tests page probably means that you are blocking access to scripts running from within the plugins folders. That’s probably a security rule in your NginX or Apache config.
That’s about all I can guess without seeing the website.
cheers,
Ross