Matthew Leffler

you’ve probably figured out by now … you’re going to need to restore from backup. And then try a different plugin.

• This reply was modified 4 years, 10 months ago by Matthew Leffler.

so to translate … omicron is agreeing that the plugin is broken, and adds that the suggested work around isn’t likely going to be a long term fix.

SO … this plugin is NOT to be used with an updated site and the use of this plugin will make irreversible db changes soooo …. hopefully anyone who installs this did or does a database backup first to undo the plugin that isn’t likely to work. Got it.

• This reply was modified 4 years, 10 months ago by Matthew Leffler.

and we’re good. I never found where it happened…but I just made a new server, then sftp into the old one downloaded everything but wordfence and uploaded it to the new server so I’m back up. Thanks

Welp, due to the speed of help I figured it was prudent to just use a backup and make a new server. So thats up at least … the problem server is still live just a new 54.84.118.113 address. Id prefer to have it but this is a week till the election and its a campaign site so cant just be down.

What Ive done after that. I as root in ssh changed the file permissions for wflog and still could read them so I deleted them. Now I no longer have a 403 I just have refused connection.

wflogs a folder out side of plugins has a bunch of firewall files in it…via ssh as root it will not allow me to edit ips.php or config-liveawf.php.

I wonder if deleting would help or lock in the issues

Also BTW there is no other security levels…like this is a Google Cloud LAMP server with no firewall other than Cloudflare and Wordfence. ie. No WHM or Cpanel firewall…