Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter rez009

    (@rez009)

    @simonskyverge I know people are angry at the errors thrown by the plugin, but seriously, using this plugin for the most part (barring weirdness like this error) makes setting this up much easier, and I personally really appreciate that you guys keep following along with the support forum.

    Additionally, good news on my end — the connection finally worked!! My site is now once again connected to FB with the correct page, pixel, catalog, Business Manager account, and Ad Manager acct.

    As a slightly less awesome bit of news — I didn’t do anything extra special to make it work on my end: the one thing different that I did do was at each point where something had been auto-selected, I un-selected and re-selected before hitting Next. I did this until the screen where it says ‘Turning off these services may make the plugin not work’ or whatever it says — at that screen I just crossed my fingers and hit Next, since I didn’t want to de- and re-select all those anyway.

    ^^ I doubt pretty seriously that any of these shenanigans did anything — my guess is that it was the fix FB rolled out behind the scenes. However, thanks for anything y’all did to make this work, much appreciated.

    • This reply was modified 4 years, 3 months ago by rez009.
    Thread Starter rez009

    (@rez009)

    Quick further update — still doesn’t work if I log out of FB completely and back in. Also doesn’t work from an incognito window. Not gonna bother using a different browser.

    Thread Starter rez009

    (@rez009)

    Mine has always had the correct details for the Business Manager, catalogs, fb page, and pixel, but for my ad account I also have ‘New’ next to it (although it HAS selected the correct one there).

    If I try to just click ‘Next’ with the Ad Account still showing ‘New’, I get an error that says I’m at my Ad Account limit and will need to make a payment or sth weird like that. However, if I then click into the Ad Account, and manually select the correct account (either before or after seeing the error), save, and then hit Next on the settings screen, it works fine — at least to get me through the next couple of screens before then throwing the Oops screen.

    I’ll see about logging out of FB completely and then back in before trying again.

    • This reply was modified 4 years, 3 months ago by rez009.
    Thread Starter rez009

    (@rez009)

    Hey Tamara,

    Thanks for the reply. Here’s a screenshot of where the error appears to happen. It’s this same place every time.

    https://snipboard.io/dImWnw.jpg

    Thread Starter rez009

    (@rez009)

    I’ve tried every troubleshooting step I could find, including those you’ve linked to here. Nothing worked.

    I’m on Linode, so I control/manage everything, and it’s definitely not a host issue.

    Instead of fighting with this plugin any longer, I simply switched to WP Mail SMTP, which worked right away with no issues at all. I’d used Easy SMTP in the past with success, but I’m just not feeling it any longer.

    Thread Starter rez009

    (@rez009)

    Alright, I believe I tracked down the main issue, and it was in the .htaccess file. On one of the sites that always worked, there was a section in the .htaccess file that looked like this:

    <FilesMatch “^(xmlrpc\.php)”>
    Require all granted
    Allow from xxx.xxx.xx.xxx # me
    Allow from xx.xx.xxx.xxx # server
    </FilesMatch>

    Then, on all the ones that didn’t work (same server), the same block looked like this:

    <FilesMatch “^(wp-login\.php|xmlrpc\.php)”>
    Order deny,allow
    Deny from all
    Allow from xxx.xxx.xx.xxx # me
    Allow from xx.xx.xxx.xxx # server
    </FilesMatch>

    While they’re pretty similar in the way they allow/deny access, the major difference was that on all the sites that weren’t working, I was also blocking access to wp-login.php. For whatever reason that was “breaking” the blocking tab.

    Removing the ” wp-login\.php| ” bit from the FilesMatch rule made them all start working as expected again.

    No real solid clue as to why this would have such an impact on how WF writes to the blocking tab, but hopefully if anyone else runs across this issue, this will help narrow down possible causes.

    • This reply was modified 4 years, 8 months ago by rez009.
    Thread Starter rez009

    (@rez009)

    Hey Gerroald,

    Thanks for the reply. I may have found a fix, but not sure as I haven’t tested it completely across all the sites. I exported the settings from one of the sites that is working to one that wasn’t, and then also made a slight change to my htaccess file, and one of those two things did the trick. I’ll report back with further updates if I can narrow down which is the actual fix. Prior to testing them all tho, see answers to your questions below:

    I can easily block myself out using any method you suggested, but still nothing appears on the Blocking tab.

    All the sites are on the same server (both the ones that work, and the ones that don’t).

    All the sites (both working and non) share similar plugins. There is nothing specific to the ones that are not working that seems to make any difference.

    Thanks again for your time and thoughts.

    Thread Starter rez009

    (@rez009)

    Still no fix for this? No further updates? It has been nearly a month with no further support. I’m still needing some way to figure this out.

    • This reply was modified 4 years, 8 months ago by rez009.
    Thread Starter rez009

    (@rez009)

    Bump. Does anyone have clues as to why there are never any IP addresses on the Blocking tab? Since I’ve got a 2 month length for blocking, it can’t be that they’ve already been unblocked.

    I’m checking to see if perhaps it’s because the Rate Limiting is all set to ‘throttle it’, even though that doesn’t really seem like it should affect the Brute Force Protection section of the Firewall. However, I’m setting a couple of those things to ‘block it’ in order to test out this theory.

    Any other ideas to try would be appreciated.

    Thanks.

    • This reply was modified 4 years, 9 months ago by rez009.
    Thread Starter rez009

    (@rez009)

    Really? Nothing? It’s been nearly two weeks since I tried the ‘test’ suggested above, and still nothing? Not even a “try this other thing (that likely won’t narrow down anything either)” ?

    I know you’re likely busy, but this is a super annoying issue that is happening across all my sites, and from what I can tell there IS no fix, apparently. What I don’t get is why the feature works on some of my sites, but on most it does not.

    Sigh. That particular blocking feature (being able to actually SEE the current blocks on the BLOCKING TAB) is one of the main reasons I use WF in the first place. With that not working, coupled with the difficulty WF can cause for my clients when they get themselves locked out, it’s a bummer. Especially since now there’s no way to unblock anyone if nothing is showing up on the blocking tab.

    • This reply was modified 4 years, 9 months ago by rez009.
    Thread Starter rez009

    (@rez009)

    Hi Gerroald,

    Thanks for your reply.

    So I tried to hit /wp-admin from my phone (wifi disabled so it would use the cell service), and I got a 403 error. The entry in the Live Traffic table that appeared to correlate to my attempts says it’s a bot, but I’m relatively certain that was me. Now, however, the front end of the site also doesn’t load on the phone, because it says it cannot establish a secure connection to the server. I’d assume this means it did get blocked.

    But to answer your question, it did not appear on the firewall>Blocks tab (still nothing there). Additionally, there is now apparently no way to unblock it.

    Thoughts? Next steps?

    Thanks,
    –Rez

Viewing 11 replies - 1 through 11 (of 11 total)