wilhud

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

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

Thanks for the quick update correcting the issue!

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

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

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

Yes, that did the trick. I kept re-installing the wordpress that I can downloaded earlier and the problem still persisted. Once I re-downloaded the wordpress zip and did a clean upload everything worked fine.

Thanks!