When setting up Keyy it doesn’t seem to recognise the re-direct is in place when setting up the QR code. With WPS Hide Login enabled it tries wp-login, not the hidden login.
Hi,
I think I need more explanation of what the two sentences above mean. I’ve never used “WPS Hide Login”. Consequently, they are somewhat opaque to me. What are the symptoms of the problem?
Keyy, when a successful scan occurs, will trigger a ‘submit’ event on the login form. So, in theory, whatever another plugin does to modify the form, it should not interfere. What does WPS Hide Login do?
David
Thread Starter
pwald
(@pwald)
Hi David, WPS Hide Login lets you easily and safely change the url of the login form page to anything you want. It doesn’t literally rename or change files in core, nor does it add rewrite rules. It simply intercepts page requests and works on any WordPress website. The wp-admin directory and wp-login.php page become inaccessible, so you should bookmark or remember the url. Deactivating this plugin brings your site back exactly to the state it was before.
If I have it enabled whilst trying to use Keyy, going to my custom log-in url, I see username / password fields but don’t get to see the QR code. If I enter my username and password I get the error message..
ERROR: This user has set up their account to require a successful scan with Keyy, which was not done.
If I go to http://www.xxxxxxxx.com/wp-admin, I get the error message
This has been disabled
which is what I would expect to see with wps hide log-in enabled.
I have tried setting up Keyy both before and after wps hide log-in is set-up and activated, but I can’t get keyy to work alongside wps.
Many thanks
Philip
Hi Philip,
I installed this plugin, and everything worked fine for me. What version of Keyy do you have? If it’s the latest release (0.6.11), then try the development version (which is what I was testing on): https://downloads.wordpress.org/plugin/keyy.zip
David
Thread Starter
pwald
(@pwald)
I can’t get it to work consistently I am afraid. I have tried across several of my sites and with WPS hide login enabled. Currently it works on one site, but not the other 2. I suspect it’s something to do with a clash with W3 Total Cache, or Wordfence (but these are enabled on all 3 sites). I haven’t got the time or inclination (at this point) to work my way through disabling / re-enabling plugins to see which one is to blame. If you want to get Joe to PM me via the email he has for me I can send you url’s in question if that helps.
Many thanks
Hi,
If you use the menu on the app, then there’s a ‘support’ option there that will send directly into our support tracking system, and where you can add any arbitrary information. That’d be the best way.
It seems to not be WPS itself, given that we both have sites on which that’s working.
The login page definitely should not be cached, because Keyy tokens expire every 5 minutes. So cacheing the login page breaks Keyy – though, that’d be expected to manifest itself in errors about tokens, rather than the scan area not appearing at all (unless it’s showing a cached page from pre-Keyy).
David
Thread Starter
pwald
(@pwald)
Hi David,
I simply can’t get it to work with WPS Hide Login activated. I have told W3 cache to ignore / not cache the log-in page(s) (I am using the syntax wp-admin\.php
wp-login\.php which I hope is correct) but to no avail. I have other measures in place to deal with brute force attacks, so it may simply be a case of deciding between Keyy and WPS hide log-in (which hasn’t been updated in 7 months anyway).
I have sent a support request via the app so I can get you looking at one of the sites in question to see if we can work out what is going on.
Many thanks
Hey @pwald
Hope all is well with you !
Just want to quickly check if this was resolved. If it was not, do let me know and I’ll investigate right away.
If you find Keyy useful, then please give us a positive review, here: https://wordpress.org/support/view/plugin-reviews/keyy?rate=5#postform
(If we’re not yet worth 5 stars, then please don’t review, but instead reply here to let us know why not – reviews less than 5 stars bring our average down!).
