Skip to content

Commit 1df9277

Browse files
committed
email troubleshooting
closes #1530
1 parent 48d1cf2 commit 1df9277

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
id: 577004ae-5fa4-4535-b34f-cd8e7f721cbb
3+
blueprint: troubleshooting
4+
title: 'Email not sending'
5+
intro: Email can be difficult to debug when it seems like you've set everything up correctly.
6+
template: page
7+
categories:
8+
- troubleshooting
9+
updated_by: 3a60f79d-8381-4def-a970-5df62f0f5d56
10+
updated_at: 1622821385
11+
---
12+
## Email Test Utility
13+
The most basic way to test that email is working is to use the Email utility in the control panel.
14+
15+
Head to Utilities > Email. In there you can see all your mail related settings. Maybe you can spot an incorrect setting.
16+
17+
On this page you can also send a test email. If you do that and see a success message but no email, here's some suggestions:
18+
19+
## Queue
20+
One thing you may want to check is that if you've configured a queue, that the queue is actually running.
21+
22+
The success message could mean that it was successfully queued, but the lack of any email is because the queued job was never executed.
23+
24+
Locally, run the queue worker:
25+
26+
```shell
27+
php artisan queue:listen
28+
```
29+
30+
Or on production, make sure you a worker configured to run the `queue:work` command.
31+
32+
## Horizon
33+
34+
If you're using Laravel Horizon, make sure that you didn't just `composer require` it, but that you also installed it using `artisan horizon:install`.

0 commit comments

Comments
 (0)