@Joe H , From your issue description, I understand you are experiencing a 404 error when trying to access pages other than hostingstart.html on your B1 App Service running Linux.
Just to clarify, is there any sub status code associated with the response code e.g. 404.1 or 404.2
- What is your application framework/language? Check that the static assets returning a 404/missing are in /public
- Review if the URL/page is only related to static content.
- This could be due to a few reasons, kindly try the following steps to isolate the issue ( if you haven’t done already so):
1.It sounds like there might be an issue with the routing configuration of your App Service. You can try checking the routing rules to ensure that they are correctly configured to route traffic to the appropriate pages.
- Please review the application code or configuration for the specific route that matches the URL
2.You may leverage App Service diagnostics from Azure Portal
- Navigate to your App Service app in the Azure Portal.
- In the left navigation, click on
Diagnose and solve problems
- Review - “Configuration and Management and “Availability and Performance” options.
3.You may also check the logs to see if there are any errors or issues that might be causing the 404 errors. To do this, you may enable logging in your App Service and then view the logs in the Azure portal. Here is a link to the Azure documentation on how to enable logging for your App Service.
----- 4.If it’s Node/js framework:
If the application is a SPA (Single Page Application), you may add
--spa argument to PM2 as follows and review process.json
file for the directory path.
pm2 serve /home/site/wwwroot/build --no-daemon –spa
Checkout this doc -to serve the built content : Running Production Build Nodejs Apps on App Service Linux
- Kindly let us know, I'll be more than happy to assist you further.