Isssue while deploying taiga using docker on localhost

Troubleshooting
1
  1. When i am setting taiga on localhost it is not sending email invite to the members it says Everything is ok if member is already registered on taiga they will get the email directly and it shows pending also in front of their email. Below is the email configuration which I have done

Email Configuration of taiga is :-
version: “3.5”

x-environment:
&default-back-environment

These environment variables will be used by taiga-back and taiga-async.

Database settings

POSTGRES_DB: “taiga”
POSTGRES_USER: “${POSTGRES_USER}”
POSTGRES_PASSWORD: “${POSTGRES_PASSWORD}”
POSTGRES_HOST: “taiga-db”

Taiga settings

TAIGA_SECRET_KEY: “${SECRET_KEY}”
TAIGA_SITES_SCHEME: “${TAIGA_SCHEME}”
TAIGA_SITES_DOMAIN: “${TAIGA_DOMAIN}”
TAIGA_SUBPATH: “${SUBPATH}”

Email settings.

EMAIL_BACKEND: “django.core.mail.backends.${EMAIL_BACKEND}.EmailBackend”
DEFAULT_FROM_EMAIL: “xxxx”
EMAIL_USE_TLS: “False”
EMAIL_USE_SSL: “True”
EMAIL_HOST: “smtpout.secureserver.net”
EMAIL_PORT: “465”
EMAIL_HOST_USER: “xxxxxxx”
EMAIL_HOST_PASSWORD: “xxxxxxx”

Rabbitmq settings

RABBITMQ_USER: “${RABBITMQ_USER}”
RABBITMQ_PASS: “${RABBITMQ_PASS}”

Telemetry settings

ENABLE_TELEMETRY: “${ENABLE_TELEMETRY}”

…your customizations go here

  1. when i am using curl command to test emails it shows everything ok but not sends the emails to the recipent
    command :-curl --url ‘smtps://smtpout.secureserver.net:465’ --mail-from ‘xxxx’ --mail-rcpt ‘xxxx’ -T - --ssl-reqd --user ‘xxxxxx:xxxxxx’ -v

Output :-

  • Connected to smtpout.secureserver.net (xx.xxx.xx.x) port 465 (#0)
  • CAfile: /etc/ssl/certs/ca-certificates.crt
  • CApath: /etc/ssl/certs
  • TLSv1.0 (OUT), TLS header, Certificate Status (22):
    } [5 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
    } [512 bytes data]
  • TLSv1.2 (IN), TLS header, Certificate Status (22):
    { [5 bytes data]
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
    { [89 bytes data]
  • TLSv1.2 (IN), TLS header, Certificate Status (22):
    { [5 bytes data]
  • TLSv1.2 (IN), TLS handshake, Certificate (11):
    { [9379 bytes data]
  • TLSv1.2 (IN), TLS header, Certificate Status (22):
    { [5 bytes data]
  • TLSv1.2 (IN), TLS handshake, Server key exchange (12):
    { [333 bytes data]
  • TLSv1.2 (IN), TLS header, Certificate Status (22):
    { [5 bytes data]
  • TLSv1.2 (IN), TLS handshake, Server finished (14):
    { [4 bytes data]
  • TLSv1.2 (OUT), TLS header, Certificate Status (22):
    } [5 bytes data]
  • TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
    } [70 bytes data]
  • TLSv1.2 (OUT), TLS header, Finished (20):
    } [5 bytes data]
  • TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
    } [1 bytes data]
  • TLSv1.2 (OUT), TLS header, Certificate Status (22):
    } [5 bytes data]
  • TLSv1.2 (OUT), TLS handshake, Finished (20):
    } [16 bytes data]
    0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0* TLSv1.2 (IN), TLS header, Finished (20):{ [5 bytes data]
  • TLSv1.2 (IN), TLS header, Certificate Status (22):
    { [5 bytes data]
  • TLSv1.2 (IN), TLS handshake, Finished (20):
    { [16 bytes data]
  • SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
  • Server certificate:
  • subject: CN=smtpout.secureserver.net
  • start date: Feb 27 16:49:39 2023 GMT
  • expire date: Mar 30 16:49:39 2024 GMT
  • subjectAltName: host “smtpout.secureserver.net” matched cert’s “smtpout.secureserver.net”
  • issuer: C=US; ST=Arizona; L=Scottsdale; O=Starfield Technologies, Inc.; OU=Repository; CN=Starfield Secure Certificate Authority - G2
  • SSL certificate verify ok.
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
    { [5 bytes data]
    < 220 sxb1plsmtpa01-06.prod.sxb1.secureserver.net :SMTPAUTH: xxxxx : ESMTP server sxb1plsmtpa01-06.prod.sxb1.secureserver.net ready
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
    } [5 bytes data]

EHLO DESKTOP-F0OONSP
0 0 0 0 0 0 0 0 --:–:-- 0:00:01 --:–:-- 0* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
< 250-sxb1plsmtpa01-06.prod.sxb1.secureserver.net hello [xxx.xxx.xx.xxx], secureserver.net
< 250-HELP
< 250-AUTH LOGIN PLAIN
< 250-SIZE 30000000
< 250-PIPELINING
< 250-8BITMIME
< 250 OK

  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
    } [5 bytes data]

AUTH PLAIN

  • TLSv1.2 (IN), TLS header, Supplemental data (23):
    { [5 bytes data]
    < 334
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
    } [5 bytes data]

AHRlY2gtb3BzQGludGVyZXh0ZWNoLmluAEludGVyZXh0VGVjaE9wc0AwNDA3MjAyMw==
0 0 0 0 0 0 0 0 --:–:-- 0:00:02 --:–:-- 0* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
< 235 … authentication succeeded :: xxxxx
0 0 0 0 0 0 0 0 --:–:-- 0:00:03 --:–:-- 0* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
MAIL FROM:

  • TLSv1.2 (IN), TLS header, Supplemental data (23):
    { [5 bytes data]
    < 250 sender ok
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
    } [5 bytes data]

RCPT TO:
0 0 0 0 0 0 0 0 --:–:-- 0:00:04 --:–:-- 0* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
< 250 recipient ok

  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
    } [5 bytes data]

DATA

  • TLSv1.2 (IN), TLS header, Supplemental data (23):
    { [5 bytes data]
    < 354 OK

It says ok but invite is not being send

  1. smtp :-
    There is no smtp error as i have smtp connected to the wordpress. Which is working fine and emails are working correctly

  2. Any Proxy settings to be done?

2

Hi @Rutuja_Nar

Welcome to our community!

I’m checking with EMAIL_BACKEND=console on localhost and emails on Taiga works fine.
The other option following the documentation is EMAIL_BACKEND=smtp

It seems like a problem in your custom configuration but I don’t know what it would be.

I hope someone from the community can help you.

Regards.

3

even after using smtp it still shows email pending only