Documentation / Operate and recover
Logs and troubleshooting
Service tabs, runtime logs, resource use, build failures, and DNS issues.
Start with the right deployment
Select the project, service, and environment. The deployment page shows build output and its final status. Runtime logs show what the process does after startup. Metrics show resource use; compare it with the configured memory and CPU limits.
A successful job or build means the command completed. The actual result depends on the application: a web page at its URL, an API response, a database row, a file in a volume, or an action in an external system. Upferry does not generate an application interface for a command that has no interface.
Service tabs and loading
Open a service in the selected environment, then choose Deployments, Variables, Metrics, Logs or Settings. Cron appears when a deployed schedule is active. The selected tab loads its own content; opening another tab may briefly show a loading message while the service header and sidebar stay visible. The sidebar shows a recent one-hour CPU and memory pulse independently of the Metrics range.
Tab links keep the environment and your log search and metric range. You can copy the address to reopen the same view, and use the browser's Back and Forward buttons to revisit tabs. In Settings, the network row may finish loading separately. Switching tabs needs no deployment and does not change the running service. To return, select another tab or use Back. There is no loading setting to enable or disable.
Common failures
| Symptom | Check |
|---|---|
| Build fails | Runtime version, lockfile, service root, dependency and build commands |
| Starts and exits | Start command, required variables, stack trace and exit code |
| HTTPS returns an error | Process listens on 0.0.0.0, configured port, health check, runtime logs |
| Database connection fails | Correct environment, reference, credentials, private hostname and allowed TCP port |
| Process is killed |