restore fails

[udadminKeymaster]

P.S. The error message you’ve sent through isn’t from https://localhost at all:

Requested URL https://www.teamscs.com:80/our-work/our-clients/

So, I need some more information on the steps you’re taking in order to work out how you got that error message.

David

[ScsParticipant]

David,

Sorry for the confusion. I have a host file entry on the webserver that resolves localhost to http://www.teamscs.com. Here is the same error but with https://localhost:

HTTP Error 404.0 – Not Found

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

Most likely causes:
•The directory or file specified does not exist on the Web server.
•The URL contains a typographical error.
•A custom filter or module, such as URLScan, restricts access to the file.

Things you can try:
•Create the content on the Web server.
•Review the browser URL.
•Create a tracing rule to track failed requests for this HTTP status code and see which module is calling SetStatus. For more information about creating a tracing rule for failed requests, click here.

Detailed Error Information:

Module
IIS Web Core

Notification
MapRequestHandler

Handler
StaticFile

Error Code
0x80070002

Requested URL
https://localhost:80/our-work/

Physical Path
C:\inetpub\wwwroot\scsweb\our-work\

Logon Method
Anonymous

Logon User
Anonymous

More Information:
This error means that the file or directory does not exist on the server. Create the file or directory and try the request again.
View more information »

As for the directory structure
c:\inetpub\wwwroot\scsweb\ the wp-config.php and all of the other wordpress folders are in this folder.

[udadminKeymaster]

Hi Lisa,

If the permalinks are the only thing not working, then we’re very close! :-)

These are also webserver configuration – it’s the webserver that sees the URL like /our-work/, and decides that it should be funnelled into WordPress (via WordPress’s main index.php file). i.e. It’s something that takes place before the request hits WordPress itself.

Normally WordPress can drop a file into the root directory that IIS detects and gets the settings from. But something must have prevented that on your install. I’m not an expert on IIS … but there is an article at the official IIS website on it, here: https://www.iis.net/learn/extensions/url-rewrite-module/enabling-pretty-permalinks-in-wordpress

Best wishes,
David

[ScsParticipant]

Everything works perfectly now! Thanks! I will be going live on the migration in a few weeks so this is awesome!

[udadminKeymaster]

Hi Lisa,

Great! Glad you got it working.

David

[ScsParticipant]

Thank you for all of your help. As far as I’m concerned it was all your help that made it possible. I’ll definitely recommend UpDraft to everyone I know who uses WordPress!

[Author]

Posts