# Technical Issues Encountered: Password Recovery and Project Member Invitation

**URL:** <https://community.taiga.io/t/technical-issues-encountered-password-recovery-and-project-member-invitation/2257>\
**Category:** Troubleshooting\
**Created:** [December 4, 2023, 9:27pm UTC](https://community.taiga.io/t/technical-issues-encountered-password-recovery-and-project-member-invitation/2257 "2023-12-04T21:27:04Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![daniel.herrero](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/daniel.herrero/32/301_2.png) [@daniel.herrero](https://community.taiga.io/u/daniel.herrero)\
**Post date:** [December 7, 2023, 7:25am UTC](https://community.taiga.io/t/technical-issues-encountered-password-recovery-and-project-member-invitation/2257/4 "2023-12-07T07:25:41Z")

</div>

Hi @mobsternation,

If you’ve followed the default installation, as suggested in the [Taiga 30mins setup guide](https://community.taiga.io/t/taiga-30min-setup/170), it deploys both Taiga and Penpot apps when started with the ` ./launch-all.sh` command.

Each product have different configuration and docker-compose.yml files:

- **Taiga** ’s configuration file is the `.env` file, which is used by the `docker-compose.yml` file
- **Penpot** ’s configuration file is the `docker-compose.penpot.env`, and it’s used by the `docker-compose.penpot.yml` file.

So, as you’re dealing with a problem from Taiga, you shouldn’t touch or configure anything related to Penpot. Editing either `docker-compose.penpot.env` or `docker-compose.penpot.yml` woun’t have an effect in Taiga.

> **Note** : To start just Taiga (without also launching Penpot) simply execute `docker compose up -d` in the root directory.

* * *

With that cleared, could you pase here your Taiga’s configuration file, the `.env` file ?  
Have you change anything apart from the STMP settings?

According to your logs taiga-async-1 correctly executed the asynchronous task responsible of sending the invitation emails for the users to join the project.

You can probably change the `EMAIL_BACKEND` var in the `.env`file to use the **console**. This way we discard problems with the SMTP server and verify the email is really “sent” (it’ll be printed in the taiga-back logs).

```yaml
# Taiga's SMTP settings - Variables to send Taiga's emails to the users
EMAIL_BACKEND=console # use an SMTP server or display the emails in the console (either "smtp" or "console")
EMAIL_HOST=smtp.host.example.com # SMTP server address
EMAIL_PORT=587 # default SMTP port
EMAIL_HOST_USER=user # user to connect the SMTP server
EMAIL_HOST_PASSWORD=password # SMTP user's password
EMAIL_DEFAULT_FROM=changeme@example.com # default email address for the automated emails
# EMAIL_USE_TLS/EMAIL_USE_SSL are mutually exclusive (only set one of those to True)
EMAIL_USE_TLS=True # use TLS (secure) connection with the SMTP server
EMAIL_USE_SSL=False # use implicit TLS (secure) connection with the SMTP server

```

You should see the html email rendered in the logs (`docker compose logs -f `) and you can search for the invitation link there:

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/2X/0/0bb9563577e87a1cfb33891f4a423d776798a095.png)

Paste your invitation link (“[http://localhost:9000/invitation/05ef2c52-94d0-11ee-8112-0242ac140009](http://localhost:9000/invitation/05ef2c52-94d0-11ee-8112-0242ac140009)”) in a private browser and finish the user registration from there.

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/2X/2/2b6e1790eae34360360cf1a61ecaef656280c408.png)

---

_[View the full topic](https://community.taiga.io/t/technical-issues-encountered-password-recovery-and-project-member-invitation/2257)._