Unable to send an email: 404 page not found (code 404)

[AartJansen]

Since the last update / server reboot my sent invoices report they are bouncing.
When I open the invoice it says
Unable to send an email: 404 page not found (code 404)

[AartJansen]

Ok I found the queue has 30 failed jobs, last error...

Error: Call to a member function filter() on null in /app/code/app/Models/Client.php:430
Stack trace:
#0 /app/code/app/Services/Client/ClientService.php(213): App\Models\Client->currency()
#1 /app/code/app/Jobs/Ninja/CompanySizeCheck.php(65): App\Services\Client\ClientService->getCreditBalance()
#2 /app/code/vendor/laravel/framework/src/Illuminate/Collections/Traits/EnumeratesValues.php(240): App\Jobs\Ninja\CompanySizeCheck->App\Jobs\Ninja\{closure}()
#3 /app/code/app/Jobs/Ninja/CompanySizeCheck.php(72): Illuminate\Support\LazyCollection->each()
#4 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): App\Jobs\Ninja\CompanySizeCheck->handle()
#5 /app/code/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#6 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\Container\Util::unwrapIfClosure()
#7 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(37): Illuminate\Container\BoundMethod::callBoundMethod()
#8 /app/code/vendor/laravel/framework/src/Illuminate/Container/Container.php(662): Illuminate\Container\BoundMethod::call()
#9 /app/code/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(128): Illuminate\Container\Container->call()
#10 /app/code/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(144): Illuminate\Bus\Dispatcher->Illuminate\Bus\{closure}()
#11 /app/code/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(119): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}()
#12 /app/code/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(132): Illuminate\Pipeline\Pipeline->then()
#13 /app/code/vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(124): Illuminate\Bus\Dispatcher->dispatchNow()
#14 /app/code/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(144): Illuminate\Queue\CallQueuedHandler->Illuminate\Queue\{closure}()
#15 /app/code/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(119): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}()
#16 /app/code/vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(126): Illuminate\Pipeline\Pipeline->then()
#17 /app/code/vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(70): Illuminate\Queue\CallQueuedHandler->dispatchThroughMiddleware()
#18 /app/code/vendor/laravel/framework/src/Illuminate/Queue/Jobs/Job.php(102): Illuminate\Queue\CallQueuedHandler->call()
#19 /app/code/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(439): Illuminate\Queue\Jobs\Job->fire()
#20 /app/code/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(389): Illuminate\Queue\Worker->process()
#21 /app/code/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(176): Illuminate\Queue\Worker->runJob()
#22 /app/code/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(138): Illuminate\Queue\Worker->daemon()
#23 /app/code/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(121): Illuminate\Queue\Console\WorkCommand->runWorker()
#24 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Illuminate\Queue\Console\WorkCommand->handle()
#25 /app/code/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#26 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\Container\Util::unwrapIfClosure()
#27 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(37): Illuminate\Container\BoundMethod::callBoundMethod()
#28 /app/code/vendor/laravel/framework/src/Illuminate/Container/Container.php(662): Illuminate\Container\BoundMethod::call()
#29 /app/code/vendor/laravel/framework/src/Illuminate/Console/Command.php(211): Illuminate\Container\Container->call()
#30 /app/code/vendor/symfony/console/Command/Command.php(326): Illuminate\Console\Command->execute()
#31 /app/code/vendor/laravel/framework/src/Illuminate/Console/Command.php(181): Symfony\Component\Console\Command\Command->run()
#32 /app/code/vendor/symfony/console/Application.php(1096): Illuminate\Console\Command->run()
#33 /app/code/vendor/symfony/console/Application.php(324): Symfony\Component\Console\Application->doRunCommand()
#34 /app/code/vendor/symfony/console/Application.php(175): Symfony\Component\Console\Application->doRun()
#35 /app/code/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(201): Symfony\Component\Console\Application->run()
#36 /app/code/artisan(37): Illuminate\Foundation\Console\Kernel->handle()
#37 {main}

And also (I think the same error)
https://github.com/invoiceninja/invoiceninja/issues/11247

[james]

Hello @AartJansen
I was not able to reproduce this issue.
But since there is a common issue, discussion and the other of the issue said "I see the issue here. I'll get a fix in." this should get resolved in some days.

[AartJansen]

I see theres been a patch for the app, but the problem still exists and resending the invoice just adds items to the stuck queue

[joseph]

@AartJansen Where do you see the patch? https://github.com/invoiceninja/invoiceninja/issues/11247 is still Open afaict?

[AartJansen]

Sorry, I saw cloudron had a patch for invoice ninja app, and I applied it and mistakenly assumed it was for that issue. I thought it would be fairly high priority, but apparently not.

[AartJansen]

FYI still a problem for me, and the upstream issue isn't the same they make no mention of having an error in the queue, only that the queue doesn't clear.
Also they updated upstream to say it was fixed in .27

I've got my invoices and quotes working again, just have the queue error with a failed job.

[joseph]

@AartJansen can you help us reproduce this in a fresh installation? If you can outline the steps, we can debug it from there.

[AartJansen]

If you want I can turn on the ssh for support on my install to check the logs, etc ?
Basically I'm not sure why it stopped, or exactly when, it didn't become apparent until I tried sending an invoice, and it "bounced".
The upstream issue was similar but not identical.
Eventually I went to settings to specify the mail server, fixed an issue with the account I was using still having admin@cludron.local as an email address, and mail was successfully going out again. i thought this setting was blank previously, but honestly cannot recall exactly.
I also tried the command in the github issue

php artisan queue:work database --queue=scout

Seemed to run ok, but the queue is still the same

[james]

Hello @AartJansen

So you have tinkered with the mailing settings and have queue issues now?

@AartJansen said in Unable to send an email: 404 page not found (code 404):

Eventually I went to settings to specify the mail server, fixed an issue with the account I was using still having admin@cludron.local as an email address, and mail was successfully going out again. i thought this setting was blank previously, but honestly cannot recall exactly

Can you please share a screenshot of your /settings/email_settings invoice ninja settings?

[AartJansen]

[james]

Hello @AartJansen
May I ask why you are setting this to something else then the default?
And if you hit SEND TEST EMAIL does it work?

[AartJansen]

Because the default( which looked blank) stopped working, so I tried some other settings, because I needed to send invoices. otherwise I don't eat (lol).
Yes it works fine.

[james]

Hello @AartJansen
I am still unable to reproduce this issue.
Did you do any other changes? The more details the better.

[AartJansen]

Did I do any other changes to get it working, or to break it ?
It was just failing to send invoices 1 september,
When I found the 404 error, and looked at the invoice ninja github, Ifound a similar issue logged by another user at the same time.
I found the other users attempt to run a php command to trigger the queue, which appeared to work in console, but made no difference to the health report screen. Also I added SCOUT_DRIVER=null to the env file.
It wasn't until I changed the email settings to use SMTP, and corrected the default email address of the admin account, to my actual address, that sending invoices again worked for me.

[james]

Hello @AartJansen

@AartJansen said in Unable to send an email: 404 page not found (code 404):

Did I do any other changes to get it working, or to break it ?

Before 01. September, did you do any changes that might have had an impact?

@AartJansen said in Unable to send an email: 404 page not found (code 404):

It wasn't until I changed the email settings to use SMTP, and corrected the default email address of the admin account, to my actual address, that sending invoices again worked for me.

This is odd. I've tried multiple times to reproduce this issue and all default worked fine.
But, if I read this correctly, it is now working and the only issue now is the health report that still displays the errors from 01. September.
Did I get this right?

[AartJansen]

No I didn't change any settings, just have automatic updates enabled, so thought that the updates had triggered the problem.
Yes thats correct, I'm not sure what the default setting is for email, and the only issue I can find is the health report error to do with queued jobs.