Solving the Unable to Refresh Statistics Error in Hangfire Dashboard

Описание: Learn how to troubleshoot and resolve the `Internal Server Error` issue in your Hangfire Dashboard with this step-by-step guide.
---
This video is based on the question https://stackoverflow.com/q/67749213/ asked by the user 'Melon NG' ( https://stackoverflow.com/u/7697261/ ) and on the answer https://stackoverflow.com/a/67998307/ provided by the user 'Melon NG' ( https://stackoverflow.com/u/7697261/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Unable to refresh the statistics in hangfire dashboard

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Troubleshooting the Hangfire Dashboard: Resolving Internal Server Errors

Using Hangfire in an ASP.NET Core application can greatly enhance your background processing capabilities. However, you might encounter roadblocks that hinder your progress - one common issue is the ability to refresh the statistics in the Hangfire dashboard. This post explains the problem of receiving an “Unable to refresh the statistics: the server responded with 500 (Internal Server Error)” message and how to fix it.

Understanding the Problem

When accessing the Hangfire dashboard on your server, you may receive the following message:

[[See Video to Reveal this Text or Code Snippet]]

This error indicates that something went wrong when the Hangfire dashboard attempted to fetch real-time statistics about jobs and their statuses.

Identifying the Specific Error

Upon investigation using Chrome DevTools, you may find that accessing http://localhost/hangfire/stats also results in a 500 Internal Server Error. Logs could show errors related to the Antiforgery token, such as:

[[See Video to Reveal this Text or Code Snippet]]

This type of error typically arises due to issues with the configuration of the Antiforgery service in ASP.NET Core.

The Root Cause

The error messages in the log files suggest a failure related to the Antiforgery token. Specifically, the server cannot find the required key in the key ring for decrypting the token. Without a valid token, the Hangfire dashboard cannot function correctly, leading to the inability to refresh statistics or execute further requests.

A Potential Middleware Solution

Many developers attempt to bypass this by ensuring that requests from localhost are not blocked. You might have added code like this:

[[See Video to Reveal this Text or Code Snippet]]

However, this does not solve the fundamental issue associated with the Antiforgery token, and the errors continue.

The Solution: Configuring Hangfire Properly

The good news is that there is a straightforward solution. You need to modify your Startup.cs file to disable the Antiforgery token for the Hangfire dashboard. Here’s how:

Step-by-Step Instructions

Open your Startup.cs file.

Locate the configuration for the Hangfire dashboard. It should look something like this:

[[See Video to Reveal this Text or Code Snippet]]

Explanation

IgnoreAntiforgeryToken: By setting this option to true, you instruct Hangfire to ignore Antiforgery tokens for the dashboard requests. This avoids the 500 Internal Server Error caused by missing or unrecognized tokens.

Conclusion

By updating your Hangfire configuration in Startup.cs, you should be able to resolve the dashboard's inability to refresh statistics. Remember that the integration of background job processing can sometimes lead to unexpected issues, but with the right knowledge, most problems can be tackled efficiently. If you continue to experience issues, review your logging to identify further details or consult the Hangfire documentation for additional troubleshooting steps.

Implement this solution and experience a smooth Hangfire dashboard that accurately reflects your job statistics!