Title: Can’t access wordpress dashobard
Last modified: February 5, 2024

---

# Can’t access wordpress dashobard

 *  Resolved [dbodmer66](https://wordpress.org/support/users/dbodmer66/)
 * (@dbodmer66)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/cant-access-wordpress-dashobard/)
 * Hi, I cannot access my wordpress dashboard when logging in with WPS hide login.
   It may be related to a redirect issue. Besides using WPS hide login I am also
   WP 2FA. Renaming either WPS or WP 2FA directories backend to inactivate the the
   plugins does not help.
 * How to get back my wordpress dashboard or to otherwise solve the matter?

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Thread Starter [dbodmer66](https://wordpress.org/support/users/dbodmer66/)
 * (@dbodmer66)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/cant-access-wordpress-dashobard/#post-17401370)
 * In addition to the above, I should also add that I changed my URL for wordpress
   to [https://www.mydomain.com/wp-admin](https://www.mydomain.com/wp-admin) which
   was probably a misunderstanding. So I need to undo this action as well.
 *  Plugin Support [MaximeWPS](https://wordpress.org/support/users/seinomedia/)
 * (@seinomedia)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/cant-access-wordpress-dashobard/#post-17408947)
 * Hello,
 * Thanks for using WPS Hide Login.
 * Deactivate the plugin renaming the folder in /wp-content/plugins. Then, reach
   your database and find “whl_page” metakey to delete it.
 *  [anysongsuz](https://wordpress.org/support/users/anysongsuz/)
 * (@anysongsuz)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/cant-access-wordpress-dashobard/#post-17458638)
 * HELP! I upgraded Elementor plugin and it caused my site not to work. So restored
   from a previous backup before I upgraded and now I cannot access my dashboard
   for the site.
    - I removed the htaccess file,
    - I renamed the plugin directory,
    - I cleared my cache on my browser and I still cannot login.
    - I tried logging in on my phone and it gives me the same “Error: Cookies are
      blocked or not supported by your browser. You must enable cookies to use WordPress”.
      on my login page. 
      I’ve been having this issue for several weeks to no avail.
      Would greatly appreciate any assistance! Help! Thanks!
 *  Plugin Support [MaximeWPS](https://wordpress.org/support/users/seinomedia/)
 * (@seinomedia)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/cant-access-wordpress-dashobard/#post-17479561)
 * [@anysongsuz](https://wordpress.org/support/users/anysongsuz/)
 * You’ve to clear your cache or to add a query string like this : [https://www.mysite/my-secret-slug?azghjkl](https://www.mysite/my-secret-slug?azghjkl)
 * Then, you’ll have to exclude you login page from cache in your dedicated plugin.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Can’t access wordpress dashobard’ is closed to new replies.

 * ![](https://ps.w.org/wps-hide-login/assets/icon-256x256.png?rev=1820667)
 * [WPS Hide Login](https://wordpress.org/plugins/wps-hide-login/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wps-hide-login/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wps-hide-login/)
 * [Active Topics](https://wordpress.org/support/plugin/wps-hide-login/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wps-hide-login/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wps-hide-login/reviews/)

## Tags

 * [blocked](https://wordpress.org/support/topic-tag/blocked/)
 * [browser](https://wordpress.org/support/topic-tag/browser/)
 * [cookies](https://wordpress.org/support/topic-tag/cookies/)
 * [dashboard](https://wordpress.org/support/topic-tag/dashboard/)
 * [login](https://wordpress.org/support/topic-tag/login/)

 * 4 replies
 * 3 participants
 * Last reply from: [MaximeWPS](https://wordpress.org/support/users/seinomedia/)
 * Last activity: [2 years, 2 months ago](https://wordpress.org/support/topic/cant-access-wordpress-dashobard/#post-17479561)
 * Status: resolved