Hey @mytechhelper,
Thanks a lot for reaching out.
Sorry about the trouble with Installatron after updating to v2.2. Looks like the login security updates we introduced might be getting a bit too protective with Installatron’s server-side requests.
To help me get to the bottom of this, could you share a few details?
1. How does Installatron talk to your WordPress site? (Via wp-cron, XML-RPC, or a direct admin URL? Your Installatron settings should mention this.)
2. Which AIO Login features do you currently have turned on? (Custom login URL, redirect rules, login security, etc.)
3. Could you check your server’s error or access logs when Installatron tries to connect? Any 403s, redirect loops, or blocked requests would be super helpful to see.
4. Your WordPress version, PHP version, and cPanel version too if you know them.
In the meantime, here’s a quick workaround that might save you, instead of disabling the whole plugin, try turning off just the login security module from the plugin settings. That should narrow it down to which feature is actually causing the conflict and your site keeps running with the rest of the features enabled.
Thanks again for your patience!
Hi @frankysweb,
Just following up on this thread, our team has been reviewing the behavior internally.
At the moment, we’ve been unable to consistently reproduce the issue with Installatron on our test environments, which is making it a bit difficult to isolate the exact trigger.
If you’re still experiencing the problem, could you please share:
- The exact Installatron workflow where the failure occurs
- Any error logs/messages generated during the process
- Your PHP version
- Whether this happens only during updates or also during fresh installs
A screencast would also be extremely helpful if possible.
We appreciate your patience while we continue investigating this further.
