You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
Minimal steps to reproduce
Follow example of using FastAPI on Azure Functions
Any log messages given by the failure
Container logs:
2022-11-07T05:03:23.905498754Z Starting OpenBSD Secure Shell server: sshd.
2022-11-07T05:03:25.784337592Z Hosting environment: Production
2022-11-07T05:03:25.784372792Z Content root path: /azure-functions-host
2022-11-07T05:03:25.784378492Z Now listening on: http://[::]:80
2022-11-07T05:03:25.784381892Z Application started. Press Ctrl+C to shut down.
Service log:
2022-11-07T05:01:48.563Z INFO - Initiating warmup request to container <name>-dtest_0_975e4ee4 for site <name>-dtest
2022-11-07T05:02:07.615Z ERROR - Container <name>-dtest_0_975e4ee4 for site <name>-dtest has exited, failing site start
2022-11-07T05:02:07.627Z ERROR - Container <name>-dtest_0_975e4ee4 didn't respond to HTTP pings on port: 80, failing site start. See container logs for debugging.
Expected/desired behavior
Service would start and would be accessible. It works just fine locally.
OS and Version?
Linux Container with non-consumption App Service Plan
Versions
4.0.4829 local, latest deployed
Mention any other details that might be useful
Once I adjusted the routePrefix to be "api" again it started working, had to re-write a bunch of code to be at a different base URL.
The text was updated successfully, but these errors were encountered:
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Any log messages given by the failure
Container logs:
Service log:
Expected/desired behavior
OS and Version?
Versions
Mention any other details that might be useful
Once I adjusted the routePrefix to be
"api"
again it started working, had to re-write a bunch of code to be at a different base URL.The text was updated successfully, but these errors were encountered: