rymst

Hi,
I am in the same boat. It happened in the development environment, so I have not installed it in the production environment yet. When will new version be released this issue? I can’t convince my owner with this approach that I have to downgrade once.

Hi,
hjogiupdraftplus-san
Thank you for your reply.

——–
found issue was solved. means you can not access with secret word url the login page ?
———
We have registered the secresword url in my browser favorites.
The login page, where we have to enter user password, is not usually displayed.
However, when I try to access the dashboard ….I am redirected to “127.0.0.1” which is the forwarding URL.

The current solution is
1. delete cookies on the terminal side.
2. on the WordPress side
　　　|— User Settings
　　　　　　|— Account Management
　　　　　　　　　|—Press “Log out from all places”　　　　　　　　　　　I understand that if you do this, you will be able to view the login screen as normal.
Your “cookies last 24 hours” information is probably it.
By the way
AIOS　|–User login
　　　　|–Enable forced logout
　　　　　　|–Enable forced logout for WP users.
This config is not set.
It is not checked.Indeed, according to our colleague, the above trouble seems to occur after the next day after 24 hours or more.
However, even if the forced logout is set to 1440 minutes,
“127.0.0.1” The above trouble continues.
Is it necessary to set the forced logout to within a day?
We have been using this plugin for several years and have never needed to set a forced logout.
The same issue has been going on since this thread was written.
As you can see on this page, re-installing does not change the trouble.
Is this another trouble?

• This reply was modified 2 years, 3 months ago by rymst.

@hjogiupdraftplus　-san
Thank you for your reply.

Hmmm…
So is it a different problem that sometimes the 127.0.0.1[Brute force settings] still shows up even after updating to the latest version?

Hi,
Has this problem been resolved with the latest version?
I have installed the latest version and still have the same problem.
By the way, I have not yet performed the manual solution described in this thread.