Password reset not working for Discourse 2.6.0.beta2

Hi all!

I use Discourse 2.6.0.beta2 Docker installation behind a Nginx proxy. Unfortunatelly users cannot reset their passwords. An email with a link is comming, but the link seems to be broken no matter how fast you will try to use it. There is a sad face :frowning: and a “Something went wrong” message when you click the reset password link from the email.

In the administration panel (https://mysite/logs/)I cannot see any logs reletad to that event. And what is also strange a docker container does not log anything as well:

This is the output of

dokcer logs app


run-parts: executing /etc/runit/1.d/00-ensure-links
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
Started runsvdir, PID is 39
chgrp: invalid group: ‘syslog’
ok: run: redis: (pid 52) 0s
ok: run: postgres: (pid 50) 0s
rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted.
rsyslogd: activation of module imklog failed [v8.1901.0 try https://www.rsyslog.com/e/2145 ]
supervisor pid: 55 unicorn pid: 78
(55) Reopening logs

my app.yml



## this is the all-in-one, standalone Discourse Docker container template
##
## After making changes to this file, you MUST rebuild
## /var/discourse/launcher rebuild app
##
## BE *VERY* CAREFUL WHEN EDITING!
## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT!
## visit http://www.yamllint.com/ to validate this file as needed

templates:
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/web.template.yml"
  - "templates/web.ratelimited.template.yml"
## Uncomment these two lines if you wish to add Lets Encrypt (https)
#  - "templates/web.ssl.template.yml"
#  - "templates/web.letsencrypt.ssl.template.yml"

## which TCP/IP ports should this container expose?
## If you want Discourse to share a port with another webserver like Apache or nginx,
## see https://meta.discourse.org/t/17247 for details
expose:
#  - 3040
  - "127.0.0.1:3040:80"

params:
  db_default_text_search_config: "pg_catalog.english"
  upload_size: 20m

  ## Set db_shared_buffers to a max of 25% of the total memory.
  ## will be set automatically by bootstrap based on detected RAM, or you can override
  db_shared_buffers: "128MB"

  ## can improve sorting performance, but adds memory usage per-connection
  #db_work_mem: "40MB"

  ## Which Git revision should this container use? (default: tests-passed)
  #version: tests-passed

env:
  LANG: en_US.UTF-8
  # DISCOURSE_DEFAULT_LOCALE: en

  ## How many concurrent web requests are supported? Depends on memory and CPU cores.
  ## will be set automatically by bootstrap based on detected CPUs, or you can override
  UNICORN_WORKERS: 2

  ## TODO: The domain name this Discourse instance will respond to
  ## Required. Discourse will not work with a bare IP number.
  VIRTUAL_HOST: $$$$$$$$$$$$$$$$$$$$$$
  VIRTUAL_PORT: 80
  LETSENCRYPT_HOST: $$$$$$$$$$$$$$$$$$$$$44
  LETSENCRYPT_EMAIL: $$$$$$$$$$$$$$$$$$$4
  DISCOURSE_HOSTNAME: $$$$$$$$$$$$$$$$$

  ## Uncomment if you want the container to be started with the same
  ## hostname (-h option) as specified above (default "$hostname-$config")
  #DOCKER_USE_HOSTNAME: true

  ## TODO: List of comma delimited emails that will be made admin and developer
  ## on initial signup example 'user1@example.com,user2@example.com'
  DISCOURSE_DEVELOPER_EMAILS: '$$$$$$$$$$$'

  ## TODO: The SMTP mail server used to validate new accounts and send notifications
  # SMTP ADDRESS, username, and password are required
  # WARNING the char '#' in SMTP password can cause problems!
  DISCOURSE_SMTP_ADDRESS: $$$$$$$$$$$$$$$
  DISCOURSE_SMTP_PORT: $$$$$$$$$$$$
  DISCOURSE_SMTP_USER_NAME: $$$$$$$$$$$$$$$$$$$
  DISCOURSE_SMTP_PASSWORD: "$$$$$$$$$$$$$$$$"
  #DISCOURSE_SMTP_ENABLE_START_TLS: true           # (optional, default true)

  ## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate
 # LETSENCRYPT_ACCOUNT_EMAIL: $$$$$$$$$$$$$$$

  ## The http or https CDN address for this Discourse instance (configured to pull)
  ## see https://meta.discourse.org/t/14857 for details
  #DISCOURSE_CDN_URL: https://discourse-cdn.example.com

## The Docker container is stateless; all data is stored in /shared
volumes:
  - volume:
      host: /var/discourse/shared/standalone
      guest: /shared
  - volume:
      host: /var/discourse/shared/standalone/log/var-log
      guest: /var/log

## Plugins go here
## see https://meta.discourse.org/t/19157 for details
hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - git clone https://github.com/discourse/docker_manager.git
#          - git clone https://github.com/discourse/discourse-chat-integration.git

## Any custom commands to run after building
run:
  - replace:
      filename: /etc/nginx/conf.d/discourse.conf
      from: "types {"
      to: |
        set_real_ip_from 172.18.0.0/24;
        real_ip_header X-Forwarded-For;
        real_ip_recursive on;
        types {

docker_args:
  - "--network=nginx-proxy"
1 Like

Are you receiving the correct link? It should look something like this: https://forum.example.com/u/password-reset/6a34c2454cf11a6707a23591e6c417ba

2 Likes

Hi Gerhard, thank you for your answear.

The link seems to be OK. There is “users” instead of “u” in my link.

https://forum.example.com/users/password-reset/23e410a2c11e576c38b1df68f112f88d

3 Likes

Hi,
I tested on two of my instances. Same error.
It looks like the generated link is wrong.
If I change:
users -> u
it works :slight_smile:

2 Likes

I can confirm that a workoround proposed by @napcok works. However I would not call it a solution. Maybe you can advice me how to solve this problem?

https://github.com/discourse/discourse/search?q="users%2Fpassword-reset"&unscoped_q="users%2Fpassword-reset"

Looks like it affects only Polish and Turkish languages.

2 Likes

I send pull request with fix for this.
https://github.com/discourse/discourse/pull/10527

I think it should be done there:
https://translate.discourse.org/translate/f3230e7607a36bb0a2f97fd90605a44e/248/en-tr/24#q=Şimdi+bir+parola+seçmek+için+şu+bağlantıya+tıklayın%3A
and there:
https://translate.discourse.org/translate/f3230e7607a36bb0a2f97fd90605a44e/248/en-pl/24#q=Kliknij+na+poniższy+link+by+wybrać+nowe+hasło

As I don’t know Turkisk, Polish or Crowdin, I will refrain from trying anything :sweat_smile:

1 Like

Edited both in Crowdin.
Closed my pull request on Github.

2 Likes

Thanks! I updated the translations in the discourse repo. They should land in the tests-passed branch really soon.

https://github.com/discourse/discourse/commit/6c3b1eb9b95f57c80bd9b7a0f47c5ca8e2edd7e9

3 Likes

Thanks! Updated both forums, all works good :slight_smile:

2 Likes