RocketChat / RocketChat/Rocket.Chat

Mail not working. Nobody can login

Open
#30,950 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

Users dont recieve emails even when i have configured SMTP in admin panel. Test mail also dosnt work. They make accounts without need for confirmation.

I freshly hosted instance based on your guide deploy-with-docker-and-docker-compose
And used sample yml + custom .env

Originally i tried to do it based on : Self-hosting Rocket.Chat With Docker

And i have set up container for nginx reverse proxy but it wasnt working so i disabled it and and used treafik as you suggested in guide.

I dont know what might be the case - logs are not showing anything regarding mails.

Maybe my custom .env rules:

LETSENCRYPT_EMAIL=admin@domain.
LETSENCRYPT_HOST=chat.domain.
VIRTUAL_HOST=chat.domain.
Accounts_UseDNSDomainCheck=false

i added them based on guide for nginx reverse proxy

Maybe i need to use nginx but yml should be in same folder as rocket chat because i terafik is.

But I really dont know. Its my 1st time using docker. Maybe its irrelevant.

Server Setup Information:

Server Setup Information
Version of Rocket.Chat Server: 6.4.5
Operating System: Ubuntu 23.04
Deployment Method: docker
Number of Running Instances: 1
DB Replicaset Oplog: Enabled
NodeJS Version: 14.21.3 - x64
MongoDB Version: 5.0.22
Proxy: traefik/
Firewalls involved:

Client Setup Information
  • Desktop App or Browser Version: every client
  • Operating System: windows, android
Additional context

How to Use Nginx Reverse Proxy With Multiple Docker Apps.

i did it before setting rocket chat and nginx configuration has some setting while treafik.yml is empty did i miss something in rocket.chat.docs?

Today nobody can login including admin. I disabled 2FA and still asks for code we cant recieve. Looks like rocket settings dont save at all.

Relevant logs:
rocketchat-rocketchat-1  | {"level":50,"time":"2023-11-12T21:55:40.298Z","pid":1,"hostname":"d64d7d4e8462","name":"System","msg":"An error occured registering with token. 'Couldn't register with token.  Please make sure token is valid or hasn't already been used'"}
rocketchat-rocketchat-1  | Error: Greeting never received
rocketchat-rocketchat-1  |     at SMTPConnection._formatError (/app/bundle/programs/server/npm/node_modules/meteor/email/node_modules/nodemailer/lib/smtp-connection/index.js:784:19)
rocketchat-rocketchat-1  |     at SMTPConnection._onError (/app/bundle/programs/server/npm/node_modules/meteor/email/node_modules/nodemailer/lib/smtp-connection/index.js:770:20)
rocketchat-rocketchat-1  |     at Timeout.<anonymous> (/app/bundle/programs/server/npm/node_modules/meteor/email/node_modules/nodemailer/lib/smtp-connection/index.js:704:22)
rocketchat-rocketchat-1  |     at listOnTimeout (internal/timers.js:557:17)
rocketchat-rocketchat-1  |     at processTimers (internal/timers.js:500:7) {
rocketchat-rocketchat-1  |   code: 'ETIMEDOUT',
rocketchat-rocketchat-1  |   command: 'CONN'
rocketchat-rocketchat-1  | }
rocketchat-rocketchat-1  | {"level":40,"time":"2023-11-13T21:16:16.113Z","pid":1,"hostname":"d64d7d4e8462","name":"DeprecationWarning","section":"API","msg":"The parameter \"query\" in the endpoint \"/api/v1/custom-user-status.list\" is deprecated and will be removed on version 7.0.0"}
rocketchat-rocketchat-1  | {"level":40,"time":"2023-11-13T21:32:03.296Z","pid":1,"hostname":"d64d7d4e8462","name":"DeprecationWarning","section":"API","msg":"The parameter \"fields\" in the endpoint \"/api/v1/users.list\" is deprecated and will be removed on version 7.0.0"}
rocketchat-rocketchat-1  | Error: Greeting never received
rocketchat-rocketchat-1  |     at SMTPConnection._formatError (/app/bundle/programs/server/npm/node_modules/meteor/email/node_modules/nodemailer/lib/smtp-connection/index.js:784:19)
rocketchat-rocketchat-1  |     at SMTPConnection._onError (/app/bundle/programs/server/npm/node_modules/meteor/email/node_modules/nodemailer/lib/smtp-connection/index.js:770:20)
rocketchat-rocketchat-1  |     at Timeout.<anonymous> (/app/bundle/programs/server/npm/node_modules/meteor/email/node_modules/nodemailer/lib/smtp-connection/index.js:704:22)
rocketchat-rocketchat-1  |     at listOnTimeout (internal/timers.js:557:17)
rocketchat-rocketchat-1  |     at processTimers (internal/timers.js:500:7) {
rocketchat-rocketchat-1  |   code: 'ETIMEDOUT',
rocketchat-rocketchat-1  |   command: 'CONN'
rocketchat-rocketchat-1  | }
rocketchat-rocketchat-1  | {"level":40,"time":"2023-11-13T21:16:16.113Z","pid":1,"hostname":"d64d7d4e8462","name":"DeprecationWarning","section":"API","msg":"The parameter \"query\" in the endpoint \"/api/v1/custom-user-status.list\" is deprecated and will be removed on version 7.0.0"}
rocketchat-rocketchat-1  | {"level":40,"time":"2023-11-13T21:32:03.296Z","pid":1,"hostname":"d64d7d4e8462","name":"DeprecationWarning","section":"API","msg":"The parameter \"fields\" in the endpoint \"/api/v1/users.list\" is deprecated and will be removed on version 7.0.0"}
rocketchat-rocketchat-1  | Error: You have not provided a mail URL. You can provide it by using the environment variable MAIL_URL or your settings. You can read more about it here: https://docs.meteor.com/api/email.html.
rocketchat-rocketchat-1  |     at packages/email/email.js:310:11
rocketchat-rocketchat-1  |     at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the custom .env, docker-compose.yml, and traefik.yml deployment configuration, then review the reported SMTP errors, especially “Greeting never received” and the missing MAIL_URL message. Verify the mail settings and container connectivity to determine why test mail and account recovery fail; done means SMTP test mail, login, and recovery codes work.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, nginx
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.