Ignoring what’s output for now, in the database, are *both* siteurl and home set to https://filimonov123.vc ?
https://codex.wordpress.org/Changing_The_Site_URL#Changing_the_URL_directly_in_the_database
Are you using any sort of caching plugin, or do you see a “Clear/Purge Cache” button in your Dashboard or admin bar? If so, would you please try clearing the cache?
Note: You do not need to install a caching plugin at this point just to clear a cache you don’t have. If you don’t have a caching plugin or a way to clear a server-level cache, just say so. 🙂
I think, before you dig into this any further, you’ll want to get a valid SSL certificate.
This is what everyone with the current version of Chrome will see when they visit your site: http://d.pr/i/1kI9W/4dl9XyBy
Everyone with the current version of Firefox will see http://d.pr/i/1cko6/1F4BApjC
The problems with your SSL certificate are detailed at https://www.ssllabs.com/ssltest/analyze.html?d=filimonov.vc&hideResults=on
This could be why your browser is still trying to load elements over HTTP.
Thanks James! I’ll make it valid for sure. But the issue with echoing the weird url is still there and it concerns only WordPress. The problem is that now the site is broken completely because I turned off the SSL certificate trying to solve the first issue with https — not showing insecure content like stylesheets that were leading via http because WP still thought that I’m on http though siteurl was set to https in the database.
Removing the SSL certificate is not the right way to debug an HTTPS issue, HTTPS can’t function without a valid SSL certificate. SSL is actually the S of HTTPS.
I believe the invalid certificate is why WP was trying to load elements over HTTP in the first place.
Once you have a valid certificate, we can investigate further, but for right now that’s my first and only suspect for your problem.
James, I’ve turned the SSL back on. Now site is live again.
Please look at the problem here:
http://take.ms/UCySC
http://take.ms/HLEmw
@tunecatcher it sounds like you’re behind a reverse proxy, e.g. NginX (your page headers tell me that you have NginX):
https://ssl.webaware.net.au/https-detection/
Try installing SSL Insecure Content Fixer and see what it recommends for HTTPS Detection on the Settings page. For more detail, run the SSL Tests page (under Tools) and see what that tells you.
If it recommends setting HTTP_X_FORWARDED_PROTO detection, then you can simply add this to your wp-config.php file:
if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] === 'https') {
$_SERVER['HTTPS'] = 'on';
}
cheers,
Ross
+1 to James,
If SSL is not valid, it won’t work in WP admin settings..
While working on some servers, I had to setup a full CACERT stuff to make it work (RHL), maybe your issue but that really depends on host/server/provider to make it work. (my case was, RHEL on Openshift on Amazon AWS).
Good luck guys ..
1 thing to add to webaware’s suggestion, check your theme files and make sure nothing is hard-coded as http://filimonov.vc
Thank you all especially webware! Now all stylesheets are loading perfectly and the site detects https. But I got into another issue. After I added
if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] === 'https') {
$_SERVER['HTTPS'] = 'on';
}
I cannot access my admin area anymore. Though the users status is 0.
I’m not an Nginx person myself, so I can’t comment on how that rule would affect anything, but I have seen plugins and theme settings choke after siteurl changes, so it’s worth a shot.
Try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.
If that does not resolve the issue, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue (theme functions can interfere like plugins).
I’ve solved the problem completely by setting these settings: http://take.ms/CzIHu
Now talking to my hosting provider so that they configured my server to work without this plugin.
Thanks everybody!
Awesome, what plugin is that?
