Hello Jeff,
thank you for the answer. After further testing, it seems to be happening with Wordfence Premium after I optimize the firewall. I genuinely don’t know why it does that, but that firewall is pretty important for us. All PHP requests will be processed by the firewall prior to running is what it says in the page for the plugin when it’s optimized, so I assume that TML is using some sort of PHP request maybe to determine if a user exists or not and it’s getting blocked, thus leading to the 404 after…
Do you have an idea on if it can even be fixed on our side? (Without turning off the firewall)
Thank you
