Durgesh Pandey , Apologies for the delayed response. Based on my understanding of your issue description, I see that you have already tried multiple things to isolate the issue, just to highlight some common causes of 404 errors, such as incorrect URL paths, misconfigured NGINX settings, and issues with PHP file handling. What app framework are you leveraging? -NGINX may show a 404 while application logging indicates a HTTP 5xx was actually returned.
Ultimately, this is due to the fact that the error_page
directive in NGINX’s default.conf
returns a non existent /50x.html
when HTTP 5xx’s are returned. Please check this - PHP configuration: Customizing NGINX’s error page handling
-Please confirm if npm run build
or yarn run build
is expected to be ran - or if the production build folder is set in a .gitignore
.
- For example, using Oryx as a deployment method - a custom deployment script may be needed - see Oryx - Configuration and
POST_BUILD_COMMAND
orPOST_BUILD_SCRIPT_PATH
I see that you have highlighted config details in the screenshot, juts to confirm - A common theme is with frameworks again - such as Laravel and Yii - where the application is served out of /public/
or /web/
- which would equate to /home/site/wwwwroot/public
or /home/site/wwwroot/web
- whereas NGINX’s default root
is /home/site/wwwroot
.
Kindly enable App Service Logging and then review application logs to fetch more info.
Please let us know, I'll follow-up with you further.