Hi @modernape.,
The most common misconfiguration that we have come across repeatedly is when a user has incorrect URL in WordPress Address URL or Site Address URL settings.
WordPress and Site Address settings
For example, lets assume that your site’s url is http://www.example.com and you go to Settings » General and set it to http://example.com. Most web hosts allow you to choose whether you would like to add a www prefix to your domain name or have it without www. In case you had selected to add www to your URL, then adding http://example.com in your WordPress settings will cause the error. Or if you opted to use your domain without www prefix, then adding it with www prefix in WordPress settings will cause this error.
When a user will come to http://example.com, they will be redirected by your server’s configuration to http://www.example.com where they will be redirected back to http://example.com by WordPress because that’s what you have set up in the settings.
If your site was working fine, and you you did not make any changes to those settings. Then you need to contact your web host, because it is most probably a configuration issue at their end.
However, if you do not have a reliable WordPress hosting provider, and they deny having any issues and/or refuse to help you, then you should consider switching web hosts or fix it yourself.
To fix this, you need to change your WordPress Address and Site Address. Go to Settings » General, change your WordPress and Site Address. If you have your address with www prefix, then change it to non-www URL, and if you have it with non-www URL then add the www prefix.
Important: Make sure that you don’t leave a trailing slash at the end of your URL like http://www.example.com/
Thanks
All the site URL settings are correct, as they have been for a couple of years. It’s just the latest post that’s the problem.
Did you try to update anything?
It was a setting in iThemes security, it offers a ‘per content’ ssl setting. So it’s fixed now.
Thanks for your help though.
