A garden ticketing container on App Service listens on port 3000, but the platform probes 80/8080 and marks the site unhealthy. What should the developer set?
Select an answer to reveal the explanation.
Short Explanation
App Service knocks on 80 or 8080 unless you post a different apartment number on the door. If your container listens on 3000, set WEBSITES_PORT (or the container port setting) to match. Wrong door, unhealthy site—even when the app inside is fine.
Full Explanation
For custom containers on App Service, the platform expects the app to listen on port 80 or 8080 unless you configure the listen port via WEBSITES_PORT or the equivalent container port setting. A process bound only to 3000 will fail health expectations until that setting matches. ACR DNS labels and ACI migration do not correct the App Service-to-container port mapping.