This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 12%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIC%3C/text%3E%3C/svg%3E)
Hi
When I create a blazor wasm hosted web application I can publish the project successfully.
then in the Server\bin\Release\net5.0\publish folder I can run the project server .exe and using https://localhost:5001 I can test the web application and access the default weather service page - which the client app uses to obtain sample records from the server api.
However, when I host the published server project on my hosting provider - I can access the client app but any service method calls to - for example the weather sample data results in a 404 error?
What must I configure / setup to allow my web application (blazor wasm hosted) to work on a deployed hosting provider?
dotnet.5.0.5.js:1 GET https://amoebaservices.co.za/WeatherForecast 404
Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: net_http_message_not_success_statuscode, 404, Not Found
System.Net.Http.HttpRequestException: net_http_message_not_success_statuscode, 404, Not Found
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
My best guess is you forgot to deploy all the files and folder in the wwwroot directory. The Fetch data example makes an HTTP GET to /sample-data/weather.json.
Hi
I deployed everything from the \bin\Release\net5.0\publish\ folder
I even zipped the entire folder - copied that to the hosting server - and then unzipped it there to make sure no file is missing.
Hi
I managed to get the simple Blazor website up and running successfully.
It turned out to be that the IIS application pool had not been granted adequate permissions to the folder which hosts the website.
I actually had to change to a different services provider - who managed to diagnose the issue and after granting the required permissions the web application worked.