---
title: 'Read Laravel logs over SSH in LaraBench'
description: 'Open a Laravel log over SSH in LaraBench, then filter entries by file, level, or message without keeping a separate terminal session open.'
canonical_url: 'https://larabench.com/laravel-tinker-workflows/read-laravel-logs-over-ssh'
md_url: 'https://larabench.com/laravel-tinker-workflows/read-laravel-logs-over-ssh.md'
last_updated: '2026-07-28'
---
# Read Laravel logs over SSH in LaraBench

> Open a Laravel log over SSH in LaraBench, then filter entries by file, level, or message without keeping a separate terminal session open.

## Direct Answer

In a terminal, connect over SSH and read a bounded section of `storage/logs/laravel.log`. In LaraBench, open Logs for the saved SSH connection, select the file, and filter entries by level or message.

## When To Use This

Use this after a failed request, queue job, scheduled task, or Tinker run when you need to inspect one Laravel log.

## Terminal Approach

```bash
ssh deploy@demo.example.com
cd /var/www/demo/current
tail -n 200 storage/logs/laravel.log
grep -n "payment provider timed out" storage/logs/laravel.log
```

## LaraBench Approach

Save the SSH target, open Logs, select `laravel.log` or a daily file, filter by level, and search for an exception class, job ID, request ID, or stable message.

## Filter The Log

Start with one identifying value rather than a broad word. Good search terms include an exception class, queue UUID, integration name, or a message controlled by the application.

## Expected Result

The Logs screen shows the filename, connection, entry count, level, timestamp, channel, message, and raw log line. Refresh reloads the file through the saved SSH connection.

## Troubleshooting

- If no files appear, confirm the app path and read permission for `storage/logs`.
- If the file is empty, check the active Laravel log channel.
- If SSH fails, run `php artisan about` manually with the same user and app path.

## Safety Notes

Logs can contain email addresses, payloads, tokens, SQL bindings, customer IDs, and server paths. Read the smallest useful range and redact secrets before sharing.

## Related Sources

- [Laravel logging documentation](https://laravel.com/docs/13.x/logging)
- [LaraBench SSH setup docs](https://larabench.com/docs/setup-guides/ssh)
- [LaraBench Log Viewer docs](https://larabench.com/docs/advanced-usage/log-viewer)

## Related Workflows

- [Run Laravel Tinker over SSH](https://larabench.com/laravel-tinker-workflows/run-laravel-tinker-over-ssh)
- [Debug a failed Laravel job with LaraBench MCP](https://larabench.com/laravel-tinker-workflows/debug-laravel-job-with-mcp)

## Canonical Page

- [HTML page](https://larabench.com/laravel-tinker-workflows/read-laravel-logs-over-ssh)
- [Markdown mirror](https://larabench.com/laravel-tinker-workflows/read-laravel-logs-over-ssh.md)

## Glossary

- [Laravel workflow glossary](https://larabench.com/docs/reference/glossary)

## Sitemap

See the full [sitemap](https://larabench.com/sitemap.md) for all public pages.