[bug]: Mail not send when adding members

[Sarank015]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current behavior

When I add member to the workspace, In the UI, it says mail has been sent successfully but it's not send to the corresponding mail ID.

Steps to reproduce

1. Go to Workspace Setting and go to Members tab
2. Add a new member with their email ID. It says the mail has been sent successfully, but the mail is didn't received to that corresponding mail ID.
3. What are the configurations need to be done to rectify the issue

Browser

Google Chrome

Version

Cloud

[pablohashescobar]

@Sarank015, we checked this issue in cloud and we were unable to replicate it. If you are using the self hosted version you can configure your smtp settings in the God Mode.

[Sarank015]

Hi @pablohashescobar

I have installed your open-source service "Plane" for our Param organization. Initially, it was working with an issue of sending invitation e-mails while inviting new users. In the process of fixing this issue, we upgraded/re-installed your latest version. We followed the exact steps as per your documentation and all the steps were successful. However, the page does not load and is struck as below.

Can I request you for a call to help us resolve this issue?

[pablohashescobar]

Hey @Sarank015, can you jump on to our discord we can talk there.

[mark0wka]

I have a similar issue with sending emails.

[BentHaase]

For some reason I had to use port 587 for Plane, even though every other client works just fine with 465 and my mailserver. When using port 465 I saw a connection request in my mailserver logs but nothing more than that happened, no mails were sent even though plane pretended 'everything is fine'.

Is there any way to see more in-depth worker logs?

This is what I got using docker compose logs -f when Plane was pretending everything is fine, no error and no mail was sent:

plane<someproject>exampletld-api-1          | 172.23.0.10:46666 - "GET /api/workspaces/<someproject>/projects/ HTTP/1.0" 200
plane<someproject>exampletld-proxy-1        | 172.23.0.1 - - [28/Jan/2024:19:23:33 +0000] "GET /api/workspaces/<someproject>/projects/ HTTP/1.1" 200 799 "https://plane.<someproject>.example.tld/<someproject>/settings/members" "Mozilla/5.0 (X11; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0"
plane<someproject>exampletld-proxy-1        | 172.23.0.1 - - [28/Jan/2024:19:23:33 +0000] "POST /<someproject>/settings/1/decide/?v=3&ip=1&_=1706469813306&ver=1.93.6 HTTP/1.1" 308 74 "https://plane.<someproject>.example.tld/<someproject>/settings/members" "Mozilla/5.0 (X11; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0"
plane<someproject>exampletld-proxy-1        | 172.23.0.1 - - [28/Jan/2024:19:23:33 +0000] "POST /<someproject>/settings/1/decide?v=3&ip=1&_=1706469813306&ver=1.93.6 HTTP/1.1" 404 2022 "https://plane.<someproject>.example.tld/<someproject>/settings/members" "Mozilla/5.0 (X11; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0"
plane<someproject>exampletld-worker-1       | [2024-01-28 19:23:33,372: INFO/MainProcess] Task plane.bgtasks.workspace_invitation_task.workspace_invitation[yyyyyyyy-xxxx-xxxx-xxxx-xxxxxxx] received
plane<someproject>exampletld-api-1          | 172.23.0.10:46698 - "POST /api/workspaces/<someproject>/invitations/ HTTP/1.0" 200
plane<someproject>exampletld-proxy-1        | 172.23.0.1 - - [28/Jan/2024:19:23:33 +0000] "POST /api/workspaces/<someproject>/invitations/ HTTP/1.1" 200 38 "https://plane.<someproject>.example.tld/<someproject>/settings/members" "Mozilla/5.0 (X11; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0"

[iqbalabd]

We've set up a self-hosted instance of Plane (v0.14.0) and I have set my email server in .env and it through /god-mode/.

We're using smtp.sendgrid.net and have set the ports, user and password credentials. These work fine for our other stuff, but it seems the user invitation emails are not even reaching Sendgrid from the Plane instance. We don't know the issue, so can we look into logs somewhere and try debugging things?

[mmospanenko]

yes, having the same issue, no any debug information, Celery tasks executes successfully. Will be great to add Test button for settings form

[dsmh]

We've set up a self-hosted instance of Plane (v0.14.0) and I have set my email server in .env and it through /god-mode/.

We're using smtp.sendgrid.net and have set the ports, user and password credentials. These work fine for our other stuff, but it seems the user invitation emails are not even reaching Sendgrid from the Plane instance. We don't know the issue, so can we look into logs somewhere and try debugging things?

I'm having the very same problem here.

In addition, when a user tries to log in with his email (previosly invited), the systems ask for a validation code sent to the email, but it also never arrives.

[pablohashescobar]

Hi,

Sorry for the late reply we are working on adding a test email button in the god mode for email settings which will display the error in the UI itself. In addition to that we have added another utility script to check the email connection from the shell directly.

[dsmh]

Hi,

Sorry for the late reply we are working on adding a test email button in the god mode for email settings which will display the error in the UI itself. In addition to that we have added another utility script to check the email connection from the shell directly.

Thank you much. May you please put an examble on how to run this script from the shell?

[pablohashescobar]

I am sharing the snippet here. We will update this in the docs as well.

python manage.py test_email "<email>"

[ZerNico]

@pablohashescobar I actually have the same issue but always got timed out.

It looks like the Turn SSL on toggle does not get saved. When toggling it on in god mode and refreshing it is back to disabled. Also I tried editing the test_mail script to manually include ssl, then it works.

Edit: fixed with https://github.com/makeplane/plane/pull/4161

[Lermatroid]

Hey @mmospanenko, what did you wind up having to do with cloudflare? We are having a issue where emails wont send but have our instance behind CF.

Thanks!

[pablohashescobar]

@Lermatroid, can you check by running the included test script python manage.py test_email <receiver_email>

[mmospanenko]

Sorry for confusion, I think I was missed with the thread. Doesn't work for me(