Fix Server Error in ‘/‘ Application. Runtime Error [4 Tested Ways]

The server error in ‘/’ application can occur when your programs and file types are not compatible with your .NET Version. This prevents your website from running on the Server.

This is a server side issue that prevents the web app from running properly. The problem is associated with ISS and ASP.NET.

Here’s how to fix it:

How do I fix server error in ‘/’ application runtime error?

To start off, if you get this error in a browser, check the URL of the page you’re trying to access. Make sure it’s correct. It the issue persists, move to the solutions below:

1. Try a different browser

If you notice that this error appears on your default browser, try using a different one and see if the issue persists. Any browser will do, but if you want a reliable, and responsive option, we recommend Opera.

Being often updated to meet the latest standards, if you don’t have any underlying issues with your .NET framework or drivers, you won’t have this error if you use it.

If you can load the page in Opera One, then you may be better off setting it as your default browser. All of its components are of the latest version at all times, so errors such as the one described above are less likely to occur.

Opera

Browse the web with a lighter browser that keeps up with the latest security and performance needs!

Free Check website

2. Restart IIS using a graphical user interface

1. Click the start windows button at the lower-left corner of your Desktop.
2. Search for Administrative Tools and click on the result.
3. Next, click on Internet Information Services (IIS) Manager to perform a restart when it opens.
   
4. On the left pane, right-click on the server node and select All Tasks and then Restart IIS.
   
5. Choose whether to restart IIS, stop IIS, start IIS, or reboot the Server and click OK.
6. To restart an individual web or FTP site, right-click on the node for the site and select Stop, then repeat and select Start.

This method might help you fix Server error in ‘/’ application runtime error in Azure web app, so be sure to try it out.

3. Adding MIME Type to resolve server error in ‘/’ application.

1. Search for the Administrative Tools on the Windows Start menu.
2. Click on the Administrative Tools icon which will come on the search result.
   
3. When Administrative Tools window displays, select Internet Information Services (IIS) Manager.
   
4. Next, look on the left-hand pane, and select the Server.
   
5. Click on Sites.
6. Now, select your domain located in the central pane.
7. Double-click MIME Types.
   
8. Click Add Under the Actions column by the right.
   
9. Fill in the File name extension and MIME Type fields In the pop-up window that will display.
10. Confirm by clicking OK, then check to see if you are still getting the server error in ‘/’ application message.

You might need to run an Internet search so you can find the exact MIME type that will work with your file extension.

After making these changes, Server error in ‘/pods’ application will be gone.

4. Verify the .NET version

1. Type Administrative Tools in Windows Start menu search box.
2. Select the Administrative Tools icon to launch it.
   
3. You will see Internet Information Services (IIS) when the Administrative Tools window opens.
4. Click to maximize the server window in the left hand pane.
5. Select Application Pools.
   
6. Continue by right-clicking on the Domain Name, and choosing Basic Settings to move to the next option.
   
7. Next, a pop window will display, click the .NET Version that is compatible with your program and file in the drop-down
8.  Finally, select OK to confirm your option.

This is a simple method, and it can help you if you’re having Server error in ‘/’ application runtime error in Visual Studio.

This error can be frustrating because it prevents you from making proper use of your site. But thankfully the methods discussed in this article will solve the Server error in ‘/’ application on Windows 10.

Make sure to read through the steps correctly so that you can get rid of this problem permanently. In case the problem is still there, visit our Internal server error in NGINX guide.

Leave comments below, so we know if you are okay with the solutions provided in this article.