wilhud

Got it to work once theme support was added to the child theme to make the zoom and other options active.

Hello,

I was actually able to figure out the issue. Because we had WP Hide Login installed which removes access to the wp-login.php screen and moves the login screen to a custom url instead, that was causing the invalid client error above. Once I disabled that plugin, then the redirect worked properly.

Is there a way to custom set the redirect url when sending the user back to the server to login or is that only available via the paid plugin?

Thanks,
Wil

That appears to have been the issue. Removing the percent sign % from the password made it so that the curl request went through successfully on all platforms. I will just make sure not to use a percent sign in the password.

Thanks,
Wil

Hello,

Thanks for the quick reply!

I tested in Postman and also in my terminal using curl and the same invalid password error is getting thrown. Is it possible that the special characters in the password are causing an issue? It has both an exclamation ! and a percent sign % included in the password. I was going to try maybe changing the password to not include those characters to see if that changes anything.

Thanks,
Wil

Faslse alarm. The google authenticator plugin had the wrong folder name. That is why it could not be found. Once corrected all seems to be working as expected again.

Thanks,
Wil

Thanks for the quick update correcting the issue!

Receiving the same error. My site has buddypress and bbPress installed as well.

Hello,

That was how I had setup the API and the plugin would not pull the videos accordingly. It was not until I removed the restriction to allow any domains to access the videos that it started working as expected.

Thanks,
Wil

Sorry for posting in another users thread. I was going to post my own ticket but was just able to resolve the issue. I was accidentally creating a server API key in google rather than a browser API key. Just setup the browser API key and all is working as expected now.

Thanks,
Wil

Was this by chance resolved? Any solution? I am having the same issue. Also de-activated all plugins and set default 2016 theme and still was not working. I even tried setting up the Google API key but to no avail.

Thanks,
Wil

I have found that if I manually run the admin-ajax.php URL provided after each failure, it appears to continue the scan process…

https://www.mydomain.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&cronKey=6f5809a35c0b83646578f60b

Does manually navigating to this URL each time the fork error is triggered lose any of the functionality of the scan? If not, then I can slowly progress through the full scan manually.

Thanks,
Wil

I have tried uninstalling and reinstalling the plugin. Attempted using a default WP htaccess file. Increased the memory limit. Still the same forking issue is occurring. My hosting company ran tests to make sure the wordfence server was able to communicate with the admin-ajax.php file and they were able to confirm that it was working on both port 80 and port 443. I am at a loss as to why this is failing. Any other recommendations?

Thanks,
Wil

After further review, it appears that each subnav is wrapped in its own UL so I was able to target the top level LI elements that I needed to style.

Wil

In case someone has this same issue in the future, I’m posting what I’ve done which appears to have resolved the problem. I tried a variety of things and one of these 3 items did the trick. I believe it was #1 but I’m not 100% positive, since I put all 3 into effect simultaneously…

1. Set the CryptX script to load in the footer instead of the header. This I believe is what ultimately triggered the fix.
2. Set CryptX to encode using Javascript instead of Unicode. Although I prefer the look of the Unicode, this may or may not have helped in solving the issue. I haven’t yet tested to see what would happen if I put it back to Unicode.
3. Some of the links had target=”_blank” on them which did not work in conjunction with the Javascript encoding that I had turned on. I removed the targets and all went back to working as expected. This was more a result of turning on the Javascript option than anything.

I’m hoping this is now resolved. I will wait a few days and then set the topic to resolved if no issues pop up again.

Wil

In case someone has this same issue in the future, I’m posting what I’ve done which appears to have resolved the problem. I tried a variety of things and one of these 3 items did the trick. I believe it was #1 but I’m not 100% positive, since I put all 3 into effect simultaneously…

1. Set the CryptX script to load in the footer instead of the header. This I believe is what ultimately triggered the fix.
2. Set CryptX to encode using Javascript instead of Unicode. Although I prefer the look of the Unicode, this may or may not have helped in solving the issue. I haven’t yet tested to see what would happen if I put it back to Unicode.
3. Some of the links had target=”_blank” on them which did not work in conjunction with the Javascript encoding that I had turned on. I removed the targets and all went back to working as expected. This was more a result of turning on the Javascript option than anything.

I’m hoping this is now resolved. I will wait a few days and then set the topic to resolved if no issues pop up again.

Wil