View logs for troubleshooting
You may need to SSH into the environments to locate and view logs. To locate the SSH command to access your environments, see the following:
- Starter: For all environments, click Access Site for the environment in the Project Web Interface
- Integration: Copy the link for the SSH command per environment through the Project Web Interface
ssh -A <project ID>_stg@<project ID>.ent.magento.cloud
ssh -A <project ID>@<project ID>.ent.magento.cloud
After pushing to your environment, you can see the results of the both hooks. Logs from the build hook are redirected to the output stream of
git push, so you can observe them in the terminal or capture them (along with error messages) with
git push > build.log 2>&1.
You can review these logs via SSH into the environment. Change to the directories listed below to review the logs.
Logs from the deploy hook are located on the server in the following locations:
The value of
<project ID> depends on the project ID and whether the environment is Staging or Production. For example, with a project ID of
yw1unoukjcawe, the Staging environment user is
yw1unoukjcawe_stg and the Production environment user is
For example, on the Staging environment for project
yw1unoukjcawe, the deploy log is located at
For Production, you have a three node structure. Logs are available with specific information for that node. For example, on the Production environment for project
yw1unoukjcawe, the deploy log is located at node 1
/var/log/platform/1.yw1unoukjcawe/post_deploy.log, node 2
/var/log/platform/2.yw1unoukjcawe/post_deploy.log, and node 3
Logs for all deployments that have occurred on this environment are appended to this file. Check the timestamps on log entries to verify and locate the logs you want for a specific deployment.
The actual log output is highly verbose to allow troubleshooting. The following is a condensed example:
The deploy log contains start and stop messages for each of the two hooks:
Start deploy., and
To review other application logs in Staging or Production, you can access and review those logs in
For Staging, the project ID has
_stg at the end. For example, if you receive 500 errors in Staging and want to review the nginx logs, you can SSH to the Staging environment and locate the logs in
Remember, when viewing the logs for Production, you have three nodes to check.