HTTP 404 issue

Peter_1985 2,691

Hi,
Due to the issue

Server Error in '/' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested URL: /Login4/Default.aspx

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.4494.0

when going to

http://localhost/Login4/Default.aspx

and I do not see any proper reason (of the above), from the log file in the following path

C:\inetpub\logs\LogFiles\W3SVC3

Please help.

Accepted answer

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-18T07:50:54.103+00:00

Hi @Peter_1985 ,

Based on the screenshot information in the previous thread you posted, I tried to reproduce your issue. Something like this:
]1

I deployed it in IIS and it can be accessed correctly via this url http://localhost:8088/. Simple result like this below:

So just modify the request url to fix it: ** http://localhost:<your-port> **

Best regards,
Xudong Peng

If the answer is the right solution, please click "Accept Answer" and kindly upvote. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Peter_1985 2,691 Reputation points

2022-11-18T08:11:41.81+00:00

Hi XuDong,
With the following configuration, I still have got the same issue.

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-18T08:32:38.427+00:00

Hi @Peter_1985 ,

I think you have made some changes to this site configuration, I found:
in previous thread :

Since you have modified its physical path, you need to modify the corresponding request url. Please try this url to see if it works for you: http://localhost:443/Login4. In my case, I test it and it works fine.

Peter_1985 2,691 Reputation points

2022-11-18T09:07:44.46+00:00

Currently the physical path is like the following

I still get the same issue to go to the following URL.
http://localhost/Login4/Default.aspx

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-18T09:13:48.947+00:00

Hi @Peter_1985 ,

You could try this url: http://localhost:443/Login4 or http://localhost:443/Login4/default.aspx and check if this work for you.

Peter_1985 2,691 Reputation points

2022-11-18T09:30:37.647+00:00

Hi,
I did try and could not go to URL - http://localhost:443/Login4.

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-18T09:51:29.983+00:00

Hi @Peter_1985 ,

What is the specific error message, I'm afraid I can't confirm the cause of the problem through your description. Is port 443 already in use? Can you start the website in the IIS server and see this error message popup? If this is the case, try to change the port of this website and test again.

Peter_1985 2,691 Reputation points

2022-11-18T09:55:41.563+00:00

Hi,
The following is the error I've got

Unable to reach this site The connection has been reset.
Recommended practice:

Check connection status
Check Proxy and Firewall
Perform Windows Network Diagnostics
ERR_CONNECTION_RESET
check internet connection
Check that your network cable is securely connected. Restart any routers, modems, or other network devices you may be using.
Allow Chrome to access networks blocked by firewall or antivirus software settings.
If the program is already on the list that is allowed to access the network, we recommend that you remove it from the list and add it again.
If you use a proxy server...
Check your proxy settings, or contact your network administrator to make sure your proxy server is working properly. If you don't think you need a proxy server: Go to Chrome menu > [Settings] > [Show advanced settings...] > [Change Proxy settings...] > [LAN settings] and uncheck [On your local network Use a proxy server] checkbox.

when going to http://localhost:443/Login4. Must I make use of the other port instead?

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-21T02:52:46.77+00:00

Hi @Peter_1985 ,

As mentioned in the error message, are you using a proxy server? If this is the case, follow the instructions in this error message to close it. Or follow these steps to close it: windows search -> type internet options and open it -> swtich to connections tab -> LAN settings -> uncheck Use a proxy server... checkbox.
In addition, I suggest you change the port of this site first to test if it works correctly.

Peter_1985 2,691 Reputation points

2022-11-21T03:47:14.693+00:00

There is no proxy server.
Do you mean 443 port should be changed on https?

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-21T07:20:55.477+00:00

Hi @Peter_1985 ,

Do you mean 443 port should be changed on https?

Yes, and the 443 is standard port numbers for HTTPS. It is already mentioned in Note of this section. Please change the port and I think it should work fine.

Peter_1985 2,691 Reputation points

2022-11-21T07:29:47.38+00:00

I changed to 441 port and cannot locate to the URL below.

http://localhost:441/Login4

having the error like

Unable to reach this site The connection has been reset.
Recommended practice:

Check connection status
Check Proxy and Firewall
Perform Windows Network Diagnostics
ERR_CONNECTION_RESET

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-21T08:26:46.503+00:00

Hi @Peter_1985 ,

Can you provide detailed error information? I tried changing this port and it works correctly, like this:

You could try to restart the IIS server and check if it can work.

Peter_1985 2,691 Reputation points

2022-11-21T08:42:33.467+00:00

Hi,
I did restart the site but the same issue does still persist.

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-21T09:11:45.983+00:00

Hi @Peter_1985 ,

Well, there could be many reasons for this problem, I'm afraid I can't be sure, can you open the browser devtools(F12) to check the following information?

Are there any error messages in the console?

Check the page request header information(in network tab)

Peter_1985 2,691 Reputation points

2022-11-21T09:24:52.18+00:00

Hi,
There is no other error on pressing F12. Can you refer to the following regarding Network tab?

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-21T09:55:36.973+00:00

Hi @Peter_1985 ,

Do you mean that there is no error message in Console? And please select the page and check the header of request, like this:

Peter_1985 2,691 Reputation points

2022-11-21T10:10:03.4+00:00

Where to get into Header below?

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-22T01:25:40.79+00:00

Hi @Peter_1985 ,

Just click on the page in list and you will get the request info, like this::

Peter_1985 2,691 Reputation points

2022-11-22T01:51:34.217+00:00

Hi,
FYI

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-22T02:49:02.79+00:00

Hi @Peter_1985 ,

What is the status code of the request, as shown in the image above? And based on this information, it seems that you have changed some configurations again, such as the port of this website, is it still the same error?

In addition, can you access the Default Web site correctly?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

2 additional answers

Peter_1985 2,691 Reputation points

2022-11-22T03:20:44.397+00:00

Hi,
Yes, it is the same issue even if I make use of 8088 port. Can you share the details to access Default web site?
Please sign in to rate this answer.
XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-22T04:32:15.297+00:00

Hi @Peter_1985 ,

Please try to access http://localhost/iisstart.htm or http://localhost:80/iisstart.htm and check if it can work correctly. On the other hand, I'm not sure if you have made any other configuration related changes, I suggest you can recreate the site and test in IIS.

Peter_1985 2,691 Reputation points

2022-11-22T06:04:41.947+00:00

I can not go to the following URLs.

http://localhost/iisstart.htm
http://localhost:80/iisstart.htm

I do re-create the site and re-deploy the project but I still cannot go to the following one.

https://localhost/Login4/Default.aspx

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-22T08:13:24.393+00:00

Hi @Peter_1985 ，

What is the specific error message? Based on the url provided after your new creation/deployment, did you add this app under the default web site (I don't see the port for it, and I'm not sure how you configured it.)

In addition, I want to confirm that the Default.aspx is indeed under the Login4 folder? If you confirm that the path of this Default.aspx is correct and there is no spelling error, then I think you can try to reinstall IIS and re-create website. I already tested and it work for me.

Peter_1985 2,691 Reputation points

2022-11-22T08:23:05.27+00:00

Hi,
Yes, I did well deploy the project with a success, into this path - C:\inetpub\VS2015B\Login4, (C:\inetpub\VS2015B is the physical path of the site), after having re-created the site in IIS.

When going to

https://localhost:8088/Login4

I have such issue below.

Your connection is not private
Attackers may try to steal your information (such as passwords, emails, or credit card details) from localhost. Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
For the highest level of security in Chrome, enable Hardened Protection

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-22T08:46:19.18+00:00

Hi @Peter_1985 ,

Are you deploying your site as https type? Or http? If possible, can you share the exact steps you took to deploy your site(reomve your private info)? like this:

Peter_1985 2,691 Reputation points

2022-11-22T09:05:11.763+00:00

Hi,
Yes, I use Https. Please see the details below

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-22T09:34:00.467+00:00

Hi @Peter_1985 ,

This error is caused by an issue with the website's SSL certificate – it's missing, or it's expired, or it wasn't issued by a legitimate certificate authority, or the client can't access it for some other reason. SSL certificates are necessary for serving websites over secure HTTPS connections.

For example, I can reproduce this issue with self-signed certificate, if the certificate you are using matches any of the above, then this result is correct. Just click Advanced button and click Proceed to your site(unsafe), something like this:

Peter_1985 2,691 Reputation points

2022-11-22T09:48:22.92+00:00

Hi XuDong,
Where do you see there was problem to the certificate? I did create the certificate on Namecheap.com and also I worked on other certificate (also from Namecheap.com) regarding the Email service and everything was also fine on that.

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-22T10:04:32.03+00:00

Hi @Peter_1985 ,

Basic information about the certificate, you can view it in the browser: like this(example in Edge):
![LAC7d.gif][1]

But I'm afraid I can't help you more with certificate related issues, it depends on how you get this certificate. Hope you can understand.

[1] : https://i.stack.imgur.com/LAC7d.gif

Peter_1985 2,691 Reputation points

2022-11-22T13:02:41.223+00:00

Hi,
But I also have http that is not related to Http and I also have the same 404 issue to go to the following

http://localhost:80/Login4

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-23T02:56:52.957+00:00

Hi @Peter_1985 ,

404 errors are usually caused by path problems, and according to this url(port 80 for default web site), did you add your app under Default Web Site? Something like this:

Peter_1985 2,691 Reputation points

2022-11-23T03:37:11.943+00:00

Hi,
I tried to browse it. Within the server, I can go to URL below
https://mydom??.org:8080/Login4/

but how to go to the same one (from the other client PC)?

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-23T06:34:25.303+00:00

Hi @Peter_1985 ,

Just get your sever IP and add the hostname in target PC in C:\ Windows\System32\drivers\etc\hosts. Something like this(modify to your own server IP):

The you can access your website via https://mydomain.com:8080/Login4/ on target PC.

There is already a discussion about this question and there is an answer for it, I tried it and it worked correctly. Since I think this question is not related to the original issue, I suggest you post it as a new thread.

In addition, did your original problem been solved?

Peter_1985 2,691 Reputation points

2022-11-23T06:45:21.523+00:00

Hi,
To the way using "C:\ Windows\System32\drivers\etc", are you sure this is fine on Windows server 2016? There is no such path. The original issue was not resolved yet.

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-23T08:32:54.933+00:00

Hi @Peter_1985 ,

My mistake. . . There is an extra space in the path I gave, it should be C:\Windows\System32\drivers\etc\hosts, open it with Notepad and edit it mentioned above. I test and it works fine.

And about your original problem, I suggest you to re-install IIS. if it still return 404 error when access Default Web Site after clearing browser cache and restarting the IIS. Because I'm not sure where you deployed this site and made any other modifications. Hope you can understand.

Peter_1985 2,691 Reputation points

2022-11-23T09:03:02.95+00:00

Hi,
Sorry to that I put the line to hosts file (per your advice) on Target PC, but still I cannot go to the same URL below. Please help.
https://mydom??.org:8080/Login4/

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-23T09:18:47.09+00:00

Hi @Peter_1985 ,

Okay, I think I need to confirm: Is the configuration part added in the hosts file your own server IP(Confirm with the ipconfig cmd), and whether it is the domain of your own site. What is the error message given, I'm afraid I can't identify the cause of the problem with your simple description.

Peter_1985 2,691 Reputation points

2022-11-23T09:34:13.297+00:00

Hi,
Please see the error below (on Target PC).

Unable to connect to the site mydom??.org The response time is too long.
Recommended practice:

Check connection status
Check Proxy and Firewall
Perform Windows Network Diagnostics
ERR_CONNECTION_TIMED_OUT

On Target PC, I am fine to ping mydom??.org.

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-23T09:58:57.73+00:00

Hi @Peter_1985 ,

Well, there could be more reasons for this error. I suggest you try the following:

Clear browser data.

Recycle IIS application pool.

Reinstall IIS.

Temporarily turn off the firewall to see if the cause of the problem.

Flush DNS.

Peter_1985 2,691 Reputation points

2022-11-23T10:05:59.057+00:00

Hi,
Sorry to that, on the same Target PC, it is fine (using the same browser) to access the same page that is deployed on another server. What is wrong with the current server having the issue?

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-24T02:40:28.733+00:00

Hi @Peter_1985 ,

As I already mentioned, there could be many reasons for this issue, I can't determine this issue because I don't know if there is something wrong with your current environment configuration, or the configuration file has been modified/broken, etc. So you need to narrow down the problem.

In addition, you can use the failed request tracking module in IIS to view related request log information. This should help with problem solving. And there may be sensitive information in these log messages, so you need to analyze it yourself to try to find the cause of the problem.

Hope you can understand.

Peter_1985 2,691 Reputation points

2022-11-24T03:20:23.083+00:00

Hi DongPeng,
Anything to adjust below to ensure that I will be with the proper log file?

XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-24T06:20:51.223+00:00

Hi @Peter_1985 ,

Use the FRT module instead of logging, please refer to this doc and enable it on your website: https://learn.microsoft.com/en-us/iis/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis
Modify the status code to 200-600, check all options in Areas, then try to access the website to get the log info and analyze it.

And I think this problem needs complex troubleshooting, environment configuration and log info (may contain sensitive information), so I suggest you open a support ticket. This will help solve this problem better, thank you for your understanding.

Peter_1985 2,691 Reputation points

2022-11-24T08:04:35.1+00:00

Hi Dong Peng,

Appreciated a lot to your follow-up on this.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
XuDong Peng-MSFT 10,841 Reputation points Microsoft Vendor

2022-11-24T10:06:05.947+00:00

Hi @Peter_1985 ,

I checked this log message (I'm not sure if it's sensitive, and I don't recommend you post it in the forum), and I found that the request was executed correctly, with 200 status code. I think you may have chosen the wrong log info file. And as I mentioned, it will be more helpful for you to open a support ticket.
Please sign in to rate this answer.
Peter_1985 2,691 Reputation points

2022-11-25T07:35:39.267+00:00

Hi Dong Peng,
I want to make your last reply as the answer of this. How?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Your answer