The login codes are all generated locally within your website. If they are failing, then you are probably getting server errors that are stopping your site from running
Check your service logs for anything like ‘Server error 500’, especially ones referencing ‘insufficient memory’ or ‘unable to start process’
Many shared service providers put limits on your account that can cause these problems. It is worth noting that in these cases, the limits apply across ALL of the sites running under your shared service account. Specifically, the PHP memory allocation (defined in /etc/php.ini ) is global. Most basic WordPress sites will need 30-60Mb, but if you have lots of plugins, lots of pages or lots of PHP clever stuff, it’s quite easy to exceed this. It’s best to increase the php.ini memory limit to address these issues – 256Mb should be enough to make a difference without upsetting your ISP (check their limits though).
If you switch on WordPress debugging (edit wp-config.php and add these lines:
and then also turn on RapID diagnostics in wp-content/plugins/rpsl-auth/rpsl_diag.php :
$rpsl_diagnostics_on = true;
$rpsl_trace_on = true;
$rpsl_trace_certs = false;
Then you will get lots of info written to wp-content/debug.log
At the end of each RapID log, it gives an indication of memory usage (current/peak/limit)
But, as noted above, the limit applies across ALL of your sites.
Viewing 1 post (of 1 total)
The forum ‘RapID Secure Login Knowledge base’ is closed to new topics and replies.