Hey, people!
I don’t know what’s wrong. My productivity-Docker-installation won’t send e-mails.
I configured smtp via env-file. I run tcpdump on the docker-host filtering by destination port 465. But there are no outgoing packages.
So weird!
Any suggestions? I already set up env-file from queue=database to sync, but this didn’t help at all. And putting smtp-data into the webapp itself will be quitted by resetting the settings to blanc again.
Help, please!
hillel
January 23, 2024, 8:33pm
2
Hi,
Have you seen the info here:
The leading free source available online invoicing app for freelancers & businesses. Invoice, accept payments, track expenses, & time-tasks
Hi, hillel,
yes, I did. I use my own mail-server. I let tcpdump run and cannot recognize any traffic outcomming from the Docker-machine when I try to send those e-mails. It’s weird.
hillel
January 23, 2024, 8:50pm
4
Here are some things to check using the Flutter app:
Are there any errors in the system log on the dashboard
Is the queue setting correct in the health check dialog
I suggest testing with a different email server to see if it helps.
Flutter-app says (translated):
“E-Mail > Error
E-Mail sent to …”
But no further description of the failure.
I’ve disabled queue after reading a forum’s entry where the failure of sending e-mails was gone after. I can reactivate it (setting it to “database”).
hillel
January 23, 2024, 8:59pm
6
That’s a bug which will be corrected in the next release.
As a workaround you can check the system logs table in the database to find the error.
Wow, that’s weird!
At first I used to setup my public mail-server-domain as smtp-server in env-file. That failed because of a refused connection – which is very unusual.
But however. Then I put in the IP-addres of the server. And here Invoice Ninja trys to resolve (!!!) the “address”. Never expected that!
I try something else.
Well, now I put a domain-name into env-file and added the server-name and address in docker-compose.yml. At least IN sent some package out. But I guess nothing to the server.
But there’s some code within the laravel.log-file:
#0 /var/www/app/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php(255): Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, ‘Attempt to read…’, ‘/var/www/app/ap…’, 145)
#1 /var/www/app/app/Services/Email/Email.php(145): Illuminate\Foundation\Bootstrap\HandleExceptions->Illuminate\Foundation\Bootstrap\{closure}(2, ‘Attempt to read…’, ‘/var/www/app/ap…’, 145)
#2 /var/www/app/app/Services/Email/Email.php(103): App\Services\Email\Email->initModels()
#3 /var/www/app/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): App\Services\Email\Email->handle()
#4 /var/www/app/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#5 /var/www/app/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\Container\Util::unwrapIfClosure(Object(Closure))
#6 /var/www/app/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(35): Illuminate\Container\BoundMethod::callBoundMethod(Object(Illuminate\Foundation\Application), Array, Object(Closure))
#7 /var/www/app/vendor/laravel/framework/src/Illuminate/Container/Container.php(662): Illuminate\Container\BoundMethod::call(Object(Illuminate\Foundation\Application), Array, Array, NULL)
#8 /var/www/app/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(128): Illuminate\Container\Container->call(Array)
#9 /var/www/app/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(144): Illuminate\Bus\Dispatcher->Illuminate\Bus\{closure}(Object(App\Services\Email\Email))
#10 /var/www/app/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(119): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(App\Services\Email\Email))
#11 /var/www/app/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(132): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#12 /var/www/app/vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(123): Illuminate\Bus\Dispatcher->dispatchNow(Object(App\Services\Email\Email), false)
#13 /var/www/app/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(144): Illuminate\Queue\CallQueuedHandler->Illuminate\Queue\{closure}(Object(App\Services\Email\Email))
#14 /var/www/app/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(119): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(App\Services\Email\Email))
#15 /var/www/app/vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(122): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#16 /var/www/app/vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(70): Illuminate\Queue\CallQueuedHandler->dispatchThroughMiddleware(Object(Illuminate\Queue\Jobs\DatabaseJob), Object(App\Services\Email\Email))
#17 /var/www/app/vendor/laravel/framework/src/Illuminate/Queue/Jobs/Job.php(102): Illuminate\Queue\CallQueuedHandler->call(Object(Illuminate\Queue\Jobs\DatabaseJob), Array)
#18 /var/www/app/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(439): Illuminate\Queue\Jobs\Job->fire()
#19 /var/www/app/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(389): Illuminate\Queue\Worker->process(‘database’, Object(Illuminate\Queue\Jobs\DatabaseJob), Object(Illuminate\Queue\WorkerOptions))
#20 /var/www/app/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(176): Illuminate\Queue\Worker->runJob(Object(Illuminate\Queue\Jobs\DatabaseJob), ‘database’, Object(Illuminate\Queue\WorkerOptions))
#21 /var/www/app/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(137): Illuminate\Queue\Worker->daemon(‘database’, ‘default’, Object(Illuminate\Queue\WorkerOptions))
Oh damn it! Ashes on my head!
Seems that I added some faulty login-data so my mail-server set the docker-machine on ban. Now IN was upset about the wrong hostname so the ssl-certificate was not accepted.
D’oh …
EDIT: Works now
hillel
January 23, 2024, 10:04pm
10
Glad to hear it, thanks for the update!
Thank you that you always assist, even if the failure is more like pebcac …