Plugin Author
Paul
(@paultgoodchild)
Do you have any other security plugin, or anything else that affect user logins?
If so, please also try disabling them, or turning off their addins to the login process.
Also, please see here: https://icontrolwp.freshdesk.com/support/solutions/articles/3000000959-i-m-locked-out-of-my-own-site-
Thread Starter
Anonymous User 14978628
(@anonymized-14978628)
Nothing else that affects logins, although the plugin was working fine with everything else before.
The only change i’ve made recently is using a cdn and installing Cache enabler plugin and comet cache pro. Could those have had any effect you know of?
I read in a previous forum post here about someone having an issue with the autoupdate not completing properly, thought this could be another possibility as i’ve got that enabled?
Don’t know but will be looking into this today.
Plugin Author
Paul
(@paultgoodchild)
yep, you’ll need to find the plugins that are conflicting, because something has changed for it to stop working. This should help:
https://icontrolwp.freshdesk.com/support/solutions/articles/3000043594
Thread Starter
Anonymous User 14978628
(@anonymized-14978628)
Seem to have found the problem. When i have the following in my htaccess to add trailing slash to urls the custom login page just refreshes after submitting login info. Any idea why this might be happening?
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !(.*)/$
RewriteRule ^(.*)$ http://example.com/$1/ [L,R=301]
Plugin Author
Paul
(@paultgoodchild)
Have you renamed your login URL using Shield?
Thread Starter
Anonymous User 14978628
(@anonymized-14978628)
yes, i’m using custom url created through shield
Plugin Author
Paul
(@paultgoodchild)
try adding an exception to your .htaccess file to account for your custom URL
Thread Starter
Anonymous User 14978628
(@anonymized-14978628)
Would this be the correct way to do it? I tried the following but it didn’t work:
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !https://www.example.com/customurl/
RewriteCond %{REQUEST_URI} !(.*)/$
RewriteRule ^(.*)$ http://example.com/$1/ [L,R=301]
Plugin Author
Paul
(@paultgoodchild)
Nope, I would guess:
RewriteCond %{REQUEST_URI} !customurl$
If you’re playing with custom .htaccess rewrite rules and you’re not completely sure how to write them, it can cause havoc. Make sure your customurl is unlikely to be anything like other URLs on the site.
Thread Starter
Anonymous User 14978628
(@anonymized-14978628)
Thanks for that Paul, login works normally now! 🙂
