All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Just broke my wp site..kinda :P
Please move to "help" section. Forgot^^
So I have been issuing Cloudflare SSL to my site recently and changed the sites domain within WordPress to https://domain.com . However there apparently was a problem because now I am getting the "non stop redirect loop error". Cloudflare mentions this error within their kb however only provide solutions which can be applied IF you have access to the dashboard which I do not have anymore. So obviously I still was able to point my wp site back to http:// by defining wp site/home from within wp-config.php but now I cant switch it in the wp settings from dashboard anymore and thus cant seem to use ssl/https at all anymore. I do have a backup from couple days ago just wondering if there is another quick way to fix this. I guess one could fix this if I knew where wp settings save their file to. Anyway hope you could follow me there. If not feel free to ask :P
Comments
phpmyadmin > wp-options?
I believe the settings are there.
Go into the database for that wordpress site and change the setting from https://domain.com back to http://domain.com
It is in the database, just have to find where
Awesome thanks guys!
EDIT:
I also got mixed content errors earlier as websites images were not https. Am I right with my guess I just need to check all the source files and replace src=''http://..." with src="//..." to get green ssl logo for whole site?
You can't edit the url from wp-admin backend if ('WP_SITEURL', or define('WP_HOME', are in your wp-config.php file.
This, this is also the best way to change the URL without DB digging.
That is my current solution I added instantly after the site broke (in wp-conf). But this disables wp-settings in wp admins which is why I was looking for another solution^^
Why don't you just disable cloudflare (or just use it as dns, like what I do), and just use the cache of w3total cache? OR play around cloudflare's SSL settings, there are options where you can off it, full, strict, etc. There is also rule processing to force ssl. Or, change wordpress url to not have https, then on the ssl at cloudflare. I hope I made sense.
Haha acctually had to disable w3 cache to make cf work and slowed my site down by 3 seconds without the caching. Getting rid of cf for now and trying it out on a testserver :P
This is known issue, change back the site URL using phpmyadmin and install the plugin https://wordpress.org/plugins/cloudflare/
I had this plugin installed but images wouldnt show as they are not https. I guess I have to change all img src to src="//..."
How about this plugin https://wordpress.org/plugins/cloudflare-flexible-ssl/
You can also update the site url settings in your theme functions.php script
update_option( 'siteurl', 'http://example.com' ); update_option( 'home', 'http://example.com' );
simple rewrite rule can do this. or something like
rewrite may be the better way, if you later may disable ssl again, but I am sure you will be capable of
destroyingoptimizing your site finally.(yet you forgot to
spammention your websites URL again :-P)Haha aight seems like I know all I need now
Thanks everyone!
@Ympker
Are you using CloudFlare flexible SSL or Full SSL? Because if you're using Flexible SSL might as well install a self-signed cert and go Full (non-strict). In my experience WordPress + CloudFlare Flexible SSL causes too many issues that a simple self-signed cert + CloudFlare Full SSL fixes quickly.
Besides, I've always felt that using CloudFlare Flexible SSL was kind of dishonest to the site user, pretending that their connection is encrypted when in reality only half of it is.
If you have your own certificate, then turn on Cloudflare's Full SSL option in order to avoid the redirect error.
I have found that this plugin solves all of the mixed content error: https://wordpress.org/plugins/really-simple-ssl/
+1 for really-simple-ssl plugin
I have a comodo positive ssl. How would I go about activiating this with cf?
@neps
Well, you need CloudFlare's $20/mo plan to use your own SSL, but you can use SSL free (you just lose the ability to use your own certificate). Might as well point it directly and throw the SSL on the actual webserver
+1