Skip to main content
Both servers and sites have a Logs tab. It tails a file on the machine and follows it as it grows; pause to read back through what has already arrived.

​
What is offered

The list is built from what Shipways knows is installed rather than from a fixed set, so a machine with two PHP versions offers both and one with no database offers no database log. On a server:
  • Nginx access and error
  • One PHP-FPM log per installed version
  • The database engine’s log, if there is one
  • Redis
  • SSH auth — where a machine being hammered on port 22 shows up first
  • Unattended upgrades
  • One log per daemon
On a site:
  • Nginx access and error, for that site’s own vhost
  • The application log
  • One log per daemon belonging to the site

​
The application log

Read from the site’s shared/storage/logs, not from the current release. That is on purpose: shared storage survives a deployment, so the file you are reading is the one the application has been writing to all along rather than one that started empty at the last deploy.

​
Permission

Reading logs needs permission to change the server or site, not merely to view it. A log carries a good deal more than the pages around it — request paths, parameters, stack traces with values in them — so it sits behind the higher bar.