Hi Bobby - I just confirmed that Litespeed is not used on the site or server. Flywheel uses its own caching. Our developer went in and did not see any issues with the login, but went ahead and reset the login attempts just in case.
Please let me know if you need anything else from me.
Thank you, I have asked the team to try accessing the site again as they were not able to do so before, as the site is not using Litespeed we will have to continue debugging
I will update you here as soon as I have feedback.
We have run some tests and at the moment it looks like Flywheel's URL normalization / re encoding is causing this behavior.
If possible, please contact the hosting provider (Flywheel) and request that they disable URL normalization/re-encoding specifically for redirects targeting the ATE endpoint: hidden link
In particular, they should ensure that redirects to this URL are passed through unchanged (no modification of the Location header and no additional encoding of the return_url parameter).
If you copy and paste the above information to their team they should know what to do.
Carlos from the senior team here! I appreciate your patience on this. I took a closer look into the server settings for hc2capital.com and I’m actually not seeing any custom rules or redirects that would be normalizing or stripping those URLs. To double-check I ran some tests on that ATE endpoint (/api/wpml/jobs/) and instead of a redirect, the server is hitting a 404 Not Found: hidden link.
So it does appear the request is reaching the site just fine but the WordPress side of things isn't recognizing the request. I did notice a few things that may be causing issues which I wanted to pass along. The main thing is outdated plugins, with some in vulnerable states. Both Ninja Forms and Yoast SEO are running versions with known security holes. These vulnerabilities often interfere with how a site handles API data, which does match the re-encoding trouble WPML mentioned. Since WPML also uses a few different bridge plugins to work with things like Ninja Forms, having one part of the chain outdated could be breaking the whole translation sync.
My best recommendation from here would be to create a backup of the site: hidden link, then go through and update the plugins to see if that resolves things. If the issue persists we'd be happy to investigate further - talk soon!
Let me know what you think. Do you agree with Carlos?
I'd say let's do what Carlos suggests, please do this and let me know your results, especially since they are willing to debug further after this step is met.
