Project Doctor & logs

When a Laravel project behaves unexpectedly, start with Project Doctor and Logs instead of making many changes at once.

1. Select the project you want to inspect.
2. Open Project Doctor.
3. Run or refresh its checks.
4. Read failures and warnings separately from successful checks.

A failed check is a clue about what needs attention. A passed check does not mean every part of the Laravel application has been tested.

Open Logs to view Laravel log entries. Look for the first meaningful exception or warning near the time the problem occurred. Keep the surrounding lines; the last stack-trace line often isn't the root cause.

1. Record the failing action and approximate time.
2. Confirm the active project and runtime.
3. Read the relevant log.
4. Make one change at a time, then retry.

Privacy: Logs can contain file paths, request data or secrets. Remove these details before sharing diagnostics publicly.

For failures involving .test addresses, see Local domains & HTTPS and Troubleshooting.