Can't login to staging server

Also, just to add, I use wordfence on this site and when I attempt to login to the staging server I get the email notification that an admin has logged in however I never actually get taken to the staging back end, just goes back to the login page. Hope this helps.

Have you moved your default login page to a custom path?

It’s important that /yourstaginsite/wp-login.php is reachable

If this is not the case enable the option: “Disable admin authorization” in settings and try to create another staging site.

Note: You than have to make sure to use any other authorization method like using .htaccess so not everyone can access your staging site.

If this does not help you can reach me via mail: support [at] wp-staging.com

No default login has not been messed with and the login form is accessible @ //myrealsite.com/mystagingsite/wp-login.php

I will try the disable admin login option and see if that works using .htaccess for the auth.

Mhh thats odd. I will install wordfence and check if this could be the reason.

Strange, all I did was go into settings to prep for another install as you suggested and I chose the option to disable the wf plugin, disable admin passwords and ticked the option to delete all data upon uninstall of plugin and saved but before I deleted the staging already built I decided to give it one more try and it let me log in even though those settings shouldn’t have a direct effect on an already provisioned staging server, I can now log in. Maybe something happens during the settings “save” routine that fixed my issue?

This sounds like any browser cached redirect.
Changing the settings will not affect previously created staging sites!

I noticed something similar in the past on my own testing server:

Chrome used the auto correction to change the url from mysite/staging/wp-login.php to mysite/wp-login. I had to delete the login cookie and purge its cache than it was working.

However, i am glad to hear that it is working now, but i’d wish we were able to track down the cause of this issue more.

Yes I’m a developer too so I paid very close attention to the url, the redirection url string and the browser cache, however it was chrome and I did not try another browser. I’ll test on a few other sites and let you know if I discover anything.

For now, my real focus is on whether this will be a quicker and easier process than just building another subdomain manually w/ another wp install and duplicating with wp migrate db etc. The big one is the file copy process as w/ cpanel / ssh its very fast to zip/unzip. However this can come in real handy when one doesn’t have access to those tools.

I am thinking about a new feature allowing us to not copy media files, instead linking them to the original source. So we would save a lot of time and space, especially on large sites. Do you think this could be useful?

> will be a quicker and easier process than just building another subdomain manually w/ another wp install and duplicating with wp migrate db etc

This was my intention when i developed WP Staging. wp migrate db is a great tool but i needed a easier to use tool which allows me and my users the creating of a staging site with a simple click.

This comes in handy when your client wants you to give technical support on his live system;-)