Read Laravel logs over SSH in LaraBench

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. The file list, parsed entry, raw line, and refresh controls stay on the same screen.

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. It is a focused log reader, not a replacement for centralized logging, retention policies, or production alerting.

Terminal approach

ssh [email protected]
cd /var/www/demo/current
tail -n 200 storage/logs/laravel.log

Narrow the output before copying it anywhere:

grep -n "payment provider timed out" storage/logs/laravel.log
grep -n "\.ERROR:" storage/logs/laravel.log | tail -n 50

Daily log channels may use filenames such as laravel-2026-07-28.log. Check config/logging.php when the expected file is missing.

LaraBench approach

• Save the SSH host, user, port, Laravel app path, and environment under Connections.
• Open Logs and choose that connection.
• Select laravel.log or the relevant daily file.
• Filter by warning, error, or another available level.
• Search for an exception class, job ID, request ID, or stable message.
• Use manual or timed refresh while reproducing the issue.

Filter the log

Start with one identifying value rather than a broad word such as "failed". Good search terms include the exception class, a queue UUID, an integration name, or a message you control in the application. Then read the surrounding entry for the stack trace and context.

Expected result

The Logs screen shows the selected 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 saved app path and the remote user's read permission for storage/logs.
• If the file is empty, check the active Laravel log channel and environment configuration.
• If entries look incomplete, open the raw line and inspect the same file manually over SSH.
• If SSH fails, run php artisan about manually with the same user and app path.

Safety notes

Logs can contain email addresses, request payloads, tokens, SQL bindings, customer IDs, and stack traces with server paths. Read the smallest useful range, redact secrets before sharing, and do not paste full production logs into an AI tool or public issue.

Related workflows

Set up the target with the SSH Tinker workflow. If the log points to a queue failure, continue with the single failed-job retry workflow.