Object reference not set path:nonfile

[Justincale]

Hi,

I’m getting a ton of Log Message: Unhandled Exception: Object reference not set to an instance of an object. For Endpoint: Fallback {*path:nonfile} after updating a site hosted on azure to .net10

the site seems to be ok. Any thoughts? Thanks.

[sbwalker]

@Justincale is there any additional exception details?

[Justincale]

It seems to be happening when URL’s that don’t exist get hit. Here’s the rest of the exception:

System.NullReferenceException: Object reference not set to an instance of an object.
at Oqtane.Components.App.GetPageResources(Alias alias, Site site, Page page, List`1 modules, Int32 moduleid, String action) in C:\Source\Projects\oqtane.build\Oqtane.Server\Components\App.razor:line 589
at System.Runtime.ExceptionServices.InternalCalls.g____PInvoke|1_0(StackFrameIterator* __pThis_native, UInt32* __uExCollideClauseIdx_native, Boolean* __fUnwoundReversePInvoke_native, Boolean* __fIsExceptionIntercepted_native)
at Oqtane.Components.App.OnInitializedAsync() in C:\Source\Projects\oqtane.build\Oqtane.Server\Components\App.razor:line 191
at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
at System.Runtime.ExceptionServices.InternalCalls.g____PInvoke|1_0(StackFrameIterator* __pThis_native, UInt32* __uExCollideClauseIdx_native, Boolean* __fUnwoundReversePInvoke_native, Boolean* __fIsExceptionIntercepted_native)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.HandleExceptionViaErrorBoundary(Exception error, ComponentState errorSourceOrNull)
at Microsoft.AspNetCore.Components.Rendering.ComponentState.SupplyCombinedParameters(ParameterView directAndCascadingParameters)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderRootComponentAsync(Int32 componentId, ParameterView initialParameters)
at Microsoft.AspNetCore.Components.Endpoints.EndpointHtmlRenderer.RenderEndpointComponent(HttpContext httpContext, Type rootComponentType, ParameterView parameters, Boolean waitForQuiescence)
at Microsoft.AspNetCore.Components.Endpoints.RazorComponentEndpointInvoker.RenderComponentCore(HttpContext context)
at Microsoft.AspNetCore.Components.Endpoints.RazorComponentEndpointInvoker.RenderComponentCore(HttpContext context)
at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.<>c.<b__10_0>d.MoveNext()
--- End of stack trace from previous location ---
at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Oqtane.Infrastructure.JwtMiddleware.Invoke(HttpContext context) in C:\Source\Projects\oqtane.build\Oqtane.Server\Infrastructure\Middleware\JwtMiddleware.cs:line 88
at Oqtane.Infrastructure.TenantMiddleware.Invoke(HttpContext context) in C:\Source\Projects\oqtane.build\Oqtane.Server\Infrastructure\Middleware\TenantMiddleware.cs:line 95
at Oqtane.Infrastructure.ExceptionMiddleware.Invoke(HttpContext context, IServiceProvider provider) in C:\Source\Projects\oqtane.build\Oqtane.Server\Infrastructure\Middleware\ExceptionMiddleware.cs:line 25

[Justincale]

Hi Shaun, as this only seems to be happening when non existent urls are being hit, i'm wondering if the upgrade to .net10 introduced some kind of global exception handler that is being triggered and writing to the log?

[sbwalker]

@Justincale there was a new NotFound() capability added in .NET 10 for Blazor however the initial Oqtane 10.0.0 release did not utilize it - it has since been added to the Dev branch for 10.0.1. I assume you are using the 10.0.0 release?

[Justincale]

I am yes. I have adjusted my notifications so I’m not getting bombarded and can wait for the next release. The amount of hacking attempts I’m getting for endpoints like wp-admin has actually been pretty eye opening.

Cheers

[sbwalker]

The HandlePageNotFound(Site site, Page page, Route route) method contains calls to NavigationManager.NavigateTo(url, true) which previously short circuited the page processing. In .NET 10 it appears that it is no longer short circuiting the page processing, which is why it is executing the GetPageResources() method (and throwing an exception). I believe this issue has already been fixed in the Dev branch, as @zyhfish implemented the new NavigationManager.NotFound() method which is new to Blazor in .NET 10.

[Justincale]

Great, thanks Shaun