sylvansound

Hey @wfpeter

I haven’t been able to focus on this lately, sorry for the delay, I’m still working on this, hope you’re still around.

Just now I manually installed WF Assistant, tried to log in to my site, wasn’t able to (with no error message, just the way it happened before) – locked out. I removed the WF Assistant folder to be sure that wasn’t the cause but same behaviour.

Just to give you a head’s up… weeks have passed and I’m sure you must have forgotten about all this… I was locked out just like this after optimizing WF, then manually removed WF, managed to get back in but constantly getting logged out and not being able to install any plugin. And preceding all of this was my inability to offer downloads to WooCommerce customers, possibly because of inability to create new user accounts, possibly related to WF.

So now it seems like I took one step forward and suddenly two steps back again. No changes have been made to my site except for automatic updates of WP and all plugins and themes.

Is it possible that WF somehow got back in there through an update…???

Any suggestions??

I will be more on the ball from now on!

Thanks a bunch.

Martin

Hi Peter!

Thanks a lot for taking the time to help me!

1. Yes, that’s the recipe I followed to manually remove WF ( https://www.wordfence.com/help/advanced/remove-or-reset/). I went through it all again and it seems like I’d done everything to the point, except for some leftover database entries that I deleted just now. But it didn’t change anything, the session keeps on expiring or however one might want to describe that behaviour.

2. No, I have never enabled WF 2FA or reCAPTCHA, and I highly doubt I ever enabled “immediately lock out invalid usernames” unless it’s a WF default.

3. No, I never removed or changed the name of the plugins folder.

4. Yes, the htaccess lines related to WF were removed the first time around.

5. ” If any database/server backups have been restored from before Wordfence was installed but the plugin itself has not been fully removed, this error could also arise.” > No, that hasn’t happened.

6. “However, the issue around the wfconfig table looks as though this table has been deleted” > Indeed, that’s what I did the first time I cleaned it up.

7. BUT – and this is probably a long shot – I just thought I’d give you absolutely all the info I can… Before, I was running two sites in a WP Multisite but decided against it, so I converted them to two single site installations with the help of a developer. (And everything was running well when he finished the job.) However, he left the databases in a bit of a mess. There are now two databases which both reference both the sites. In both databases there are long lists of entries with the prefix “3”, which are related to the site in question, but also all the entries for the site without a prefix, the old “main site”. I don’t know if one or both databases are active and being referenced by which site so I try not to meddle too much. What I did today was to remove all WF entries in the SECOND database, but only those with the “3” prefix. However, the “main site” also runs WF so there are still plenty of WF entries in both databases, but as they don’t have the prefix “3” I can’t see how the site in question would be troubled by that… I hope that makes sense.

Also, just to mention it, I have Litespeed Cache and Ninjafirewall also running, but there was never a compatibility issue with WF in the past. Just for the record.

So, the status right now is that haven’t gone deeper into stuff, such as the Woocommerce user account issue, but as the constant logging out continues I take that as a sign that the problem is still there…

Please let me know if you have any other ideas, Peter. Thanks in advance.

Regards,
Martin

That’s the sidebar of the same plugin, two different ways of changing currency.

This issue remains unsolved. Any help, please?

No, wait, I can now see the site but /wp-admin still gives me a blank page.

I would really appreciate some help.

Thanks

Thank you so much for the response!

Yes, there must be a way to work around it but I’m worried about what might happen if I’m not able to.

So my question now boils down to this:

I’m assuming the warning of not being able to reuse the domain after deletion would only take effect if I try to reinstall it in THE SAME MULTISITE INSTALLATION, right?

If I completely reinstall a new instance of WP (probably single site) and use the same domain name there, surely there will be no such restriction?