AKJK

Does anyone knows if this issue has been addressed and solved in version 4.0.21? Also is 4.0.21 working flawlessly?

Don’t want to risk updating to 4.0.21, find that it does not work, deactivate it and run into this SSL problem again.

Thanks Viktor. Also from your experience so far, once you delete the database and do a fresh install, will everything work fine or is it only the hide backend feature that works fine?

Viktor
Was wondering if your method will work if I had previously used the plugin to change the database prefix from wp to something else?
Am worried that this feature would have made changes to my wp-config file and once the database entries are erased, it may mess up my site?
Do advise and thanks

Faced this issue as well. Noticed it only after I upgraded to 4.0.7.
Here was what happened. I had previously upgraded to 4.0.3, rolled back to 3.6.6 after issues with the hide backend feature. When 4.0.7 was released, decided to try my luck again with version 4.0.7 and that was when this issue floated up.
I tried going into FTP to change my htaccess file permission from 404 to 644 but no luck. Also changed my wp-config from 444 to 644 but again no luck. Plugin still says “unable to release lock.”
I then decided to deactivate the plugin and it immediately broke my site. Contacted my webhost and was told that these lines were written into my wp-config file.
define( ‘FORCE_SSL_LOGIN’, true );
define( ‘FORCE_SSL_ADMIN’, true );
The funny thing is that I did not even use the SSL feature in the plugin so not sure why those lines were even triggered.
When the webhost removed the above lines, I was able to login again via wp-admin. Given the bad experience, I once again rolled back to 3.6.6.
I am now monitoring this support forum for the date when all issues are solved before trying to upgrade once more.
Meanwhile, does anyone know why this is happening i.e. the statement that it is “unable to release lock” as well as the lines forcing SSL?

Had this same issue when I deactivated the plugin. Anyone knows why?