OrleanDashboard is not working with Orleans 3.7.1

[NicolasLiaoRan]

We updated orlean component to version 3.7.1,orlean dashboard component also had been updated to version 3.1.0 But we found orlean dashboard is not working,how to solve it? Our framework is .Net Core 3.1

this is our code for loading dashboard .UseDashboard(options => { options.CounterUpdateIntervalMs = 30000; })

Especially,we found it's working fine with orlean version equal or below 3.5.1. So counld you help us to solve it with orlean 3.7.1.

Thanks

[richorama]

Thanks for reporting this!

Could you explain how it doesn't work - does the dashboard not start? Do you get an error?

[NicolasLiaoRan]

In our program,dashboard is basic config just like your introduce,just port is customize,such as *: 8066 After we start our program,whatever debug or product environment,dashboard can not show,we checked monitor and confirmed the port is listened,and there is no error message Even AppDomain.CurrentDomain.UnhandledException can not catch any problem. Without any change of code and configs,just checkout orlean to 3.5.1,it works fine.

[clement128]

Not sure if it is the same issue?

I am using orleans 3.7.1 + dashboard 3.6.2(selfHost=false), I got a lot of errors on the front-end

Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-uskZECO0t/V7BmNS9lzi/Tx9F4MMPY4GQ7pfoMB2Nqw='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback.

[NicolasLiaoRan]

Your problem may be in local network，I have test the same version as you(3.7.1 for orlean and 3.6.2 for orleandashboard),when I worked in local network or private environment, occured the same problem as you.But if I changed it in public network ,it's work fine. But I still don't know why it's unavailiable in .Net Core 3.1 with orlean in 3.7.1 and dashboard in 3.1.0.

[clement128]

Ok I think the issue is because I enable CSP in my web server.