Read logs
Logs shows what your environment's containers are printing, so you can see what it is doing, or why it failed, without a shell.
Reading a log
- Open Hosting → Logs.
- Choose the tab for the container whose output you want.
- Read its recent lines in output order, with the newest at the bottom.
- Choose Refresh to fetch the latest output. Last read at shows when the latest successful container-log read finished.

Container output covers a recent window. For restarted containers, the panel includes output from the previous run when it is still available. Look for markers that identify the previous run, report a container state, or explain why output is unavailable. Export anything you need to keep. Application-file and database backups exclude logs.
Older output
Below the container logs, Retained log history reads older output the platform kept after the container logs expired. Choose a window — Last hour or Last 6 hours — and choose Read history. Nothing is read until you ask. For anything older, contact Support; recovery is not guaranteed.
One application's logs
Each application's own page shows its logs under Logs: the recent output of its own containers, and Retained log history read for that application alone. In a shared environment every application runs in one shared runtime, but each has its own container there, so its page shows only its own output. Sites that share one PHP runtime write to one log, with each line starting with the site's address; read that log on the environment's Logs page, linked from the application's page.
Auto refresh
Auto refresh starts Off. While watching the logs, choose Every 10 seconds, Every 30 seconds or Every minute to fetch fresh output automatically. You can still use Refresh for an immediate read.
Choose Off when you are done. Automatic reads pause while the browser tab is hidden; auto refresh is not background log collection or a saved history.
Export logs
Choose Export logs to download a text file containing every container entry from the latest read, not just the selected tab. The file includes the environment name and identifier, the read time, and each container's name, Pod and log lines. Its filename includes the environment name and read time so you can distinguish snapshots.
Export does not fetch again: choose Refresh first if you need a newer snapshot. The button is disabled when there are no container entries to export.
The downloaded file is your copy, not a history saved by Hosting. Logs can contain sensitive information; review the file before sharing it and keep it somewhere appropriate.
When a log is empty
An empty view usually means the application has not written anything recently, or it has restarted since it last wrote. An application that is not serving often says nothing in its own log — start with the environment's state on Overview and the failure message reported there.
Using logs with us
When you ask for help, include:
- the environment, and the application;
- roughly when the problem happened;
- an exported snapshot or a copy of the relevant log lines, or the message the page reported.
The environment's own identifier is shown on Overview → Troubleshooting; including it saves a round trip.
Next
- Work out why a deploy failed or a running application misbehaves: Troubleshoot a deploy or an application.
- Check the environment's state and retry a failed change: Your environment.
- Get files in and out with SFTP, or open a shell: SFTP & SSH access.