Current Issues that users might run into in the current released version
Timebase Components:
Historian: HTTPS Redirection Middleware Failed message
Unless HTTPS was configured, users will automatically receive the "Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware Failed" message. This can generally be ignored, unless the user has attempted to configure HTTPS.
Users can configure HTTPS using the Pulse Component documentation.
Historian: AntiForgery error message
Running on Docker (Linux) users may receive an error message relating to Antiforgery:
"Microsoft.AspNetCore.Antiforgery.DefaultAntiforgery: An exception was thrown while deserializing the token" This is caused by the Historian UI Component starting up for the first time.
app.UseAntiForgery() is required to run Blazor Components Prevent Cross-Site Request Forgery (XSRF/CSRF) attacks in ASP.NET Core | Microsoft Learn
The reason it happens in Docker is because the default Antiforgery key is created internally to the container and needs to be recreated every time a new container is created.
This will not influence the operation of the Timebase Historian