How to Check Website Error Log of ASP.Net Websites in Plesk

Learn how to check the website error log of ASP.NET websites in Plesk. Our Plesk Support team is here to help you with your questions and concerns.

How to Check Website Error Log of ASP.Net Websites in Plesk

If your website experiences downtime or functionality issues, troubleshooting should always begin with reviewing the web server logs.

These logs offer insight into what went wrong. This may include configuration errors, missing files, or application failures.

For example, incorrect file or directory permissions can trigger hidden errors that logs will reveal. Here’s how to resolve the “Fixing permissions on panel packages files” error in Plesk.

In this blog, we will look at two ways to check error logs in Plesk: using the built-in Website Log Check tool and manually inspecting logs via File Manager.

What is Website Log Check?

Plesk offers a helpful feature called the Website Log Check to simplify this process. This tool scans the web server logs for common issues and recommends fixes.

The Website Log Check is part of Plesk’s .NET Core extension and provides a guided approach to error log management.

Method 1: Using the Website Log Check Feature

1. First, log in to the Plesk Panel.
2. In the left-hand menu, click on Websites & Domains.
3. Now, scroll down and select the .NET Core extension.
4. Here, we will see the Application Info, including Application URL, Document Root, and Startup File.
5. Then, click on the Log Check option to view the current path to the log file directory.
6. If needed, we can change the log directory path manually.
7. Once finalized, click Apply to save the new log path.
8. Then, click on Log List to check if logs are being generated.
9. If logs are not yet visible, enable Real-Time Updates, wait a few moments, then refresh the page.
10. Next, check if logs for the ASP.NET website are now visible.
11. If no errors are shown and the logs are still being generated, go to File Manager.
12. Head to the relevant directory to locate and view the log files.

Sometimes, you may run into issues like “No files found for glob var log maillog error in Plesk.” If so, this guide can help you troubleshoot.

Method 2: Manual Log Inspection via File Manager

If you prefer direct file access, try these steps:

1. To begin with, log in to the Plesk Panel.
2. Then, click Websites & Domains in the left-hand menu.
3. Now, click on the Files section to open the File Manager.
4. Then, go to the domain’s logs directory. We will see the following folders:
   • FailedRequests: Contains logs of failed IIS requests.
   • iis: Contains IIS server logs.
   • php_errors: Stores PHP-specific error logs.
5. Depending on what we are troubleshooting, open the appropriate folder:
   • For PHP issues, go to php_errors and look for files like error_log.
   • For IIS issues, open the iis folder and check the most recent .log files.
6. View the files directly in File Manager or download them for deeper analysis.

If you’re experiencing an internal server error when using GraphQL, you’ll often find relevant clues in the logs. Learn how to troubleshoot it in our article: GraphQL Internal Server Error in Plesk.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

Whether you’re a developer, a server admin, or a website owner, logs are your best friend in diagnosing and resolving misconfigurations, missing files, script failures or server errors.

By regularly reviewing the error logs, we can proactively address issues and keep the website running smoothly.

In brief, our Support Experts demonstrated how to check the ASP.NET website error log of ASP.NET websites in Plesk.