Azure Blazor WASM not loading on some browsers/device dll files NS_ERROR_NET_PARTIAL_TRANSFER

Kevin Redfern 20

I am experiencing an issue with a custom domain against a Wep App on azure.

The XXXX.azurewebsites.net url works fine,

The custom domain associated with that doesn't want to load.

This is the type of error I am getting with firefox.

User's image

This error has happened before, but just went away. Last time I thought it was a dns issues or caching with service providers as in the area we did have outages.

The website itself has api's on it, and they are all functioning ok. But it will not serve the frontend, which is blazor wasm .net6

I can't seem to prove or disprove what might be the underlying issue.

Any help or pointers would be massively appreciated.

Kevin Redfern 20 Reputation points

2023-08-26T12:12:26.04+00:00

The issue has now resolved itself. So I suspect maybe an issue with azure, or some other service inbetween.

If anyone does have any suggestions what i could do next time this happens to properly identify the underlying issue/cause, again would be very helpful.
Anonymous

2023-08-28T09:07:24.38+00:00

Hi @Kevin Redfern,

The issue should related to your firefox browser. Next time when the issue occurs, please try to use other browser to test it.

Related links : What causes NS_ERROR_STORAGE_CONSTRAINT in Firefox?

Best Regards

Jason

Accepted answer

VenkateshDodda-MSFT 25,111 Reputation points Microsoft Employee Moderator

2023-08-28T09:34:41.77+00:00

@Kevin Redfern Thanks for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

Based on the information shared, I have understood that you request to your Blazor is failing and you are seeing this error NS_ERROR_NET_PARTIAL_TRANSFER message in the browser network trace and also you have mentioned that issue is self-resolved.

When I have researched about the error message all are pointing and this might be related to DNS issue. As you have mentioned that your webapp is configured with custom domain.

Could you please run the Binding & SSL configuration Detector in SSL and Domain category under Diagnose and Solve Problems of your webapp to check and eliminate whether are they any configuration issue.

As you are looking for root cause I would suggest you raise a support ticket to investigate deeper on this.

Feel free to reach back to me if you have any further questions on this.
Please sign in to rate this answer.
Kevin Redfern 20 Reputation points

2023-08-28T09:55:14.1266667+00:00

Thanks for the comments.

The issues was happening in other browser then firefox, but at times it was working in chrome, and then not.

The site is all working now, which is strange since I have not changed anything. It appeared that time resolved the issues, hence why I think/thought it might be a connection related issue.

I shall try the binding & SSL configuration.

I do have SSL but this is just via cloudfare.

And caching for this subdomain was disabled.

Kevin Redfern 20 Reputation points

2023-08-28T09:57:15.3+00:00

thanks for the comments, I shall try the SSL config.

The site wasn't working in chrome or edge. Firefox is just where I got the error messages to screen shot.

The issues has gone away by itself now, so I guess sit must be a connection issue somewhere.

Hopefully it will not happen again, but if it does I shall attempt to fault find the issue

VenkateshDodda-MSFT 25,111 Reputation points Microsoft Employee Moderator

2023-08-29T12:31:46.61+00:00

@Kevin Redfern Thanks for your response. As mentioned in my earlier response if the issue re-occur I would suggest you to run the SSL and Domain detector to eliminate whether there are any configuration/dns issues and if you didn't found any raise the support ticket accordingly to check and assist your further on this.

Please accept as Yes if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.

Kevin Redfern 20 Reputation points

2023-08-31T07:12:23.8866667+00:00

HI

The problem seemed to resolve itself when I put an SSL cert against the custom domain.

I had probably assumed that since I was using cloudfare for the cert this was good enough and duplicating them would of done more damage then actually fixing the problem.

Many thanks

VenkateshDodda-MSFT 25,111 Reputation points Microsoft Employee Moderator

2023-08-31T08:43:12.96+00:00

@Kevin Redfern Thanks for your response and sharing the solution for the benefit of community. Glad to know that your problem has been resolved
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

0 additional answers

Your answer