Runtime Logs
Debugging and monitoring your application's standard output.
Mapherix captures build/start output and application runtime output. Open the Runtime Logs tab to inspect startup progress, framework messages, request logs, warnings, and errors.
Logs are the first place to check when a deploy fails, a public URL returns an error, or the app starts but does not respond. They show dependency installation, build scripts, the start command, framework boot messages, and runtime crashes.
Log Features
- Timezone Selection: You can adjust the timestamps to match your local timezone using the dropdown in the top right.
- Color Coding: Standard outputs are plain text, while errors (stderr) are highlighted in red, allowing you to spot crashes quickly.
- Refresh: Use the refresh button to fetch the latest runtime output for the service.
Common issues to check
- Wrong port: The app listens on one port, but the service is configured for another.
- Localhost binding: The app listens on
127.0.0.1instead of0.0.0.0. - Missing dependency: The build command did not install everything required by the start command.
- Missing secret: The app expects an environment variable that has not been added.
- Database mismatch: The app expects PostgreSQL, MySQL, or MongoDB settings that do not match the selected database.
Build Logs vs Runtime Logs
If the service does not become Running, check the build command, start command, listening port, and runtime logs. For Flask and FastAPI apps, bind to all interfaces with
0.0.0.0 when possible.