Hi ,
Hangfire works perfect on local iis, and I have deployed hangfire with my .net 4.5 app to azure no problem, as db tables are populated etc. Problem is, even when app is using AlwaysOn in Azure, the hangfire dashboard displays completely blank, no errors, but nothing shows at all.
strange.
I had this issue, took a little bit of tracking down but for anyone who encounters this it's because (or was in my case at least) of the default authorization filter which disables remote access.
To enable access use:
app.UseHangfireDashboard("hangfire", new DashboardOptions
{
AuthorizationFilters = Enumerable.Empty<IAuthorizationFilter>()
});
Be warned this does open up the dashboard to anybody so it's worth considering what authorization filters to use.
Perhaps the default filter should be changed to output something to the log or request body in this instance as a clue as to what is going on?
Thank you very much for this info!
I had given up on hang fire and moved to quartz but now I can give hang fire another shot
Cheers
Nigel
Sent from Samsung Mobile
I had this issue, took a little bit of tracking down but for anyone who encounters this it's because (or was in my case at least) of the default authorization filter which disables remote access.
To enable access use:
app.UseHangfireDashboard("hangfire", new DashboardOptions
{
AuthorizationFilters = Enumerable.Empty<IAuthorizationFilter>()
});
Be warned this does open up the dashboard to anybody so it's worth considering what authorization filters to use.
Perhaps the default filter should be changed to output something to the log or request body in this instance as a clue as to what is going on?
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/HangfireIO/Hangfire/issues/534#issuecomment-202996783
app.UseHangfireDashboard("/hangfire", new DashboardOptions
{
Authorization = Enumerable.Repeat(new HangfireAuthorizationFilter(), 1)
});
Most helpful comment
I had this issue, took a little bit of tracking down but for anyone who encounters this it's because (or was in my case at least) of the default authorization filter which disables remote access.
To enable access use:
Be warned this does open up the dashboard to anybody so it's worth considering what authorization filters to use.
Perhaps the default filter should be changed to output something to the log or request body in this instance as a clue as to what is going on?