Archived topic
Anomaly when Accessing Password Protected Page
3 replies · Started by R on January 21, 2022
I wonder if anyone has any leads to a solution for my issue, below.
After introducing GP (premium,) to my site, there were several occasions when accessing a password protected page that an error was received (see attached screenshot).
However, the second attempt succeeds. It took a while to realise that it wasn't due to a wrong password in the first instance.
Later accesses to the page also succeed until something changes. I am beginning to suspect that when my personal IP changes, or if my browser cached files or cookies are deleted, then the phenomenon returns.
I have kept all my plugins up to date and have tried removing/disabling many of the ones I can without compromising the website. I have also recreated the protected page from scratch - but the issue remains
The issue occurs with MS Edge, Firefox and Google Chrome on Windows 10. I am told it also occurs on iPhone and Android devices. It is difficult to reproduce the issue but it seems more consistent with MS Edge.
My web host is suggesting it could be my theme, but I am hesitant to change that.
Knowledge of any similar issues or ideas for further investigation would be very welcome.
PS I see there is no option to attach a file to this post:
The error that is returned says that the 'site cannot be reached' and returns with 'wp-login.php/?action=postpass' in the search bar.
As you can see, the preceding website url is missing (it should read 'website-url/wp-login.php/?action=postpass' )
Many thanks
Hi there,
I haven't seen that kind of error before, and there isn't anything in the theme that interferes with password protection or permalinks.
I have seen issues relating to a password requiring more than one login attempt - and thats generally caused by Page Caching, whether that be a plugin or server side. The general fix for that is to exclude those pages URIs from the cache ( ie. don't cache them )
Thank you, David, for your reply.
Presumably, to exclude a page from caching this has to be done at the visitor's browser. Unfortunately, I don't think that many of our members would be able/want to do that.
I wonder if my problem is actually that, after the initial unsuccessful logon attempt to the protected page, that a file is then cached which enables the second and subsequent logon to be successful - until some other change/expiry comes along and it ceases to be valid?
Page Caching can be on your Server and or added via a plugin on your website.
If you have no cache plugins, check with your host to see if the server has page caching. If it does then the server ( or plugin ) may allow you to exclude pages from the cache.
This will at least eliminate the site delivering a cached page.
