Github pages are perfectly running and i got no errors on workflow actions on deploying on azure,
but iam getting blank page on url provided by azure.
Please help to deploy my site on azure (static web app service) with already deployed github pages
it would be great help....
Update the basehref in index.html or you can delete that line from index.html
Related
The image attached shows the error I get when deploying my NextJS App APIs to Netlify. Locally, they all work well
On Netlify, I forgot to add the API key to my environment variable. Immediately after adding it, everything worked smoothly
I have vuejs app which is working fine on aws but if I deploy on shared hosting then website works fine but if refresh on a page then it throws 404 error.
I used: createWebHistory in router index file
I also used createWebHashHistory too but refresh page will not work. It throws the below error
The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.
If I go to home page and switch menus then it works properly.
Please advise
Thanks
I had previously created a website for my band on thescratch.ie using create-react-app and hosted this using S3 and Cloudfront. I recently replaced the react site using Shopify instead and thescratch.ie domain now points to Shopify.
For new users to the site, everything works fine but old users continue to see a broken cached version of the react website, not a Shopify site. I had assumed that the cache would eventually expire for these users, but it's been like this for a couple of months now.
Looking at the Chrome dev tools network panel I notice a couple of things:
Almost everything is being served from cache - the index.html and main.js return a 200 and have a size of (service worker)
Images return a 404
The manifest.json returns a 404
I'm wondering if there's a way to expire the service worker cache? Is it possible to do this by hosting a new manifest.json file on Shopify?
Thanks in advance.
I ran into the same issue in a combination of CRA & Gatsby.
Found this Gatsby plugin which helped me.
The underlying article maybe also can help you.
tl;dr in my understanding you need to place a service-worker.js in the root directory containing the code to unregister the old service worker.
I'm developing a .net 5.0 blazor wasm application. When I run the app form visual studio using IIS Express and navigate to https://localhost:5001/docs/simple.pdf, the file is served in browser.
However the same does not work after deploying the blazor wasm app to IIS. I'm not getting any error instead my Not Found Route template screen gets loaded.
Here is the screen prints:
wwwroot of blazor wasm app:
IISExpress loading the document:
IIS virtual directory path:
IIS not loading the document and display NotFound Route template:
I also noticed none of the files in wwwroot is not directly accessible in browser in IIS. Please assist on what I'm missing.
Blazor WebAssembly is not involved in serving your files.
This is something to configure in IIS.
This seems to be an issue with service-worker.published.js file coming with blazor wasm pwa template. This has been reported in dotnet/aspnetcore repo.
Please follow the issue in github for more updates.
I was able to reproduce your issue. Here is how I think you can fix it.
Navigate to the Server project inside your solution.
Open the file Startup.cs. Navigate to the Configure method and add this line of code:
app.UseStaticFiles();
Publish your project and recopy to IIS.
In the default Visual Studio template, this code will be there. But depending on how you created your solution, maybe you missed it.
I have deployed an MVC 4 website on Azure over the last half an hour or so and I am having a few problems with the website.
One page is meant to be pulling information out of the database and displaying it. The content is in Sql Azure, but nothing is still coming out.
The user logins, and can go into a dashboard to add content to the system.
This are the two problems I am finding but a 404 error displays.
MVC routing issue?
Check you don't have something strange in Global.asax.cs
Are you using Forms based authentication?
Are you using additional libraries / components like ELMAH that could be causing the issue?
Have you configured a custom domain i.e. mydomain.com?
Also refer to section 'View failed request tracing logs' in the Troubleshooting Windows Azure Web Sites in Visual Studio