Hello people,
I just did a fresh install of Taiga on my Docker host and after a few issues I managed to get it to work but no matter what, the email is not working.
Following the email configurations from the docs Install Taiga in Production I put the email configs in the env settings of Portainer.
Any idea?
Thanks in advance
Hi @adispy
According to your screenshot, you are using console as EMAIL_BACKNED so emails are being printed through the console (along with the rest of the logs).
Change it to smtp if you want to send via smtp server.
I hope this can help
Best regards
I have tired both, smtp and console and still not working. This was the last try when I captured the screen.
Are there any logs somewhere? If so, in which of the taiga containers?
Anyone?
I looked out on the internet but can’t find any valid answer and looks like there are a lot of email issues.
Do I need a SMTP agent installed on the docker host?
Hi @adispy
Taiga use the command email libs from python (specifically the implementation offered by Django) so it is something that is highly proven so errors are usually related to finding the appropriate values for configuration parameters.
Something that would be great is to have a command in taiga to test the SMTP connection with the server. But there isn’t. There is a command to send emails that is used to test all the emails in the application. But you need to load the sample data first.
docker compose exec taiga-back python manage.py sample_data
docker compose exec taiga-back python manage.py test_emails my_email@email.com
The first command creates example users and projects on the platform and the second sends an example of each email to the indicated email address. This way you can prove that the sending is done correctly.
There is another option, using the python shell.
docker compose exec taiga-back python manage.py shell
And type
from django.core.mail import send_mail
send_mail("subject", "body", "from@email.com", ["to@email.com"])
These two methods should show you the connection error traces on the screen.
On the other hand, to see the logs of the email sending in the platform you should review the taiga-back and taiga-async service (the emails are sent from an asynchronous task soemtimes).
This is an example error after an invitation has been sent:
I hope this info can help you.
Best regards
Hi David,
Thank you for your patience, but where can I get that sample_data file because I am getting the following error message:
no configuration file provided: not found
Thanks,
sample_data is not a file, is a command
docker compose exec taiga-back python manage.py sample_data
Execute the comand python manage.py sample_data inside the container taiga-back (the command takes a few minutes)
Tried it, but still does not work. It cannot find python and trying to install it does’n work either.
Also, in the Docker host I browse to the volume of taiga-back and still not working, same error as posted previous.
I run the command outside de containers (from the taiga-docker directory).
But I don’t understant why you have taiga-back code inside /srv/taiga/back. It should be in /taiga-back
(I’m so sorry, but it’s difficult for me to indicate the steps you need to follow if you use an environment other than the one described in the documentation. I don’t use Portainer nor have I tried installing taiga there)
