dma999999

Thanks very much. The instructions were straightforward. Unfortunately, following the suggestions in the guide did not work when I turned on the hide backend feature and cleared all the caches. I’m on WPEngine and it’s only their caches I used, so I cleared both the one from within WP in their plugin, as well as the user portal. I tried clearing a couple of times after having reactivated the feature, but alas, same error message. There is no option in WPEngine to exclude wp-login from caching, at least none that I could find.

Figured it out – can’t use the “Hide backend” function in iThemes. Disabling that allows Clef to work.

That being said, it would be great if there were a way to use that functionality with Clef.

Thanks gents – appreciate the input. Looks like someone managed to hack my sad little blog.

Just as an aside – Alex – I’m a big fan of your work and just wanted to express my appreciation.

That’s a shame. I quite liked the feature (and did not actually notice that it didn’t work properly). Oh well.

BTW, just wanted to say thanks – still a great plugin and I’m a big fan of your other stuff as well.

Thanks for the note. I figured as much. Perhaps then consider having the plugin flag a warning or something when it sees 127.0.0.1 to alert folks to this issue? Just a thought.

As always, really appreciate the great work on this plugin – very helpful!

Also found this https://wordpress.stackexchange.com/questions/54139/w3total-cache-problem-with-nginx and gave it a try. I think this was Chris’ suggestion. Same result. My /etc/nginx/w3-total.conf only had the browser cache and didn’t reflect what was on the install page.

Came across while I was looking for something else. However, it seems I am experiencing the same issue – only the browser cache portion is found in the nginx.conf in the root directory.

Thanks Robin. After much frustration, I rebooted my virtual server once again and suddenly everything started working. Alas, I have no idea why or how…

I’m not sure, to be honest. I don’t think my browser is too unusual – it’s Chrome. To be honest I’m not sure I’d be able to tell you what, if anything, in the list would be blocking me.

Thanks for providing the reference. Not sure if I am comfortable editing a serialized array, but will take a look when I get home (they block phpMyAdmin access ports at work) and see.

The specific problem I am having is that I can’t deactivate the blacklist setting without getting the 403 error. As far as I can tell, when I deselect the checkbox and click save, it first writes .htaccess to *include* the blacklist, presumably to align the manually edited .htaccess with what the settings say should be there, before attempting to remove the blacklist. But of course, by then it’s too late, because of the 403 error.

Of course, this is purely a wild-assed guess on my part. All I know is that when I deselect and hit save, I get a 403 error. When I open up .htaccess, all the BWPS settings have reappeared. If I manually delete and re-upload, 403 goes away, but the blacklist is still selected.

Let me know if I can provide any other information.

Hey thanks for the note esmi. I had reset the password but that didn’t seem to work. I suppose I need to reset the username then. Would you or anyone else happen to know where I could find that? Or better yet point me to docs to show where it’s normally stored? The reason I ask is because I suspect I’ve deleted the database entry altogether, so will need to create it again in order to login.

Thanks again!

alchymyth – thanks very, very much for the note. I just checked it again and you are of course right. Odd. I have no idea what happened. Earlier on it just wasn’t there in style.css – completely missing. Oh well.

I do very much appreciate you taking the time to look into it.

techblawg.ca

Frederick – sorry for the undue alarm. After further testing I’ve determined that this error is being caused by Cloudflare and is related to their beta Rocket Loader function. When I turn it off, the error goes away. Back on, and it reappears. I will mention it to the Cloudflare folks.

Also wanted to thank you again for creating such a great plugin!

Esmi – thanks very much! The links were very helpful.

Thank you! It worked wonderfully. Most appreciated!