question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Email verification Problem

See original GitHub issue

My actions before raising this issue

Expected Behaviour

Fix could not login on the server error

Current Behaviour

image

Possible Solution

  • Edit base.py with
ACCOUNT_AUTHENTICATION_METHOD = 'username'
ACCOUNT_CONFIRM_EMAIL_ON_GET = True
ACCOUNT_EMAIL_REQUIRED = True
ACCOUNT_EMAIL_VERIFICATION = 'mandatory'
  • build cvat
docker-compose -f docker-compose.yml -f docker-compose.dev.yml build
docker-compose up -d

Steps to Reproduce (for bugs)

Context

Your Environment

  • Git hash commit (git log -1):
  • Docker version docker version (e.g. Docker 17.0.05):
  • Are you using Docker Swarm or Kubernetes?
  • Operating System and version (e.g. Linux, Windows, MacOS):
  • Code example or link to GitHub repo or gist to reproduce problem:
  • Other diagnostic information / logs:
    Logs from `cvat` container

Next steps

You may join our Gitter channel for community support.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
arcibiyocommented, May 13, 2022

@nmanovics When ı adjust Email verification settings like in this link https://openvinotoolkit.github.io/cvat/docs/administration/basics/installation/#email-verification

I used just this code script

ACCOUNT_AUTHENTICATION_METHOD = “username” ACCOUNT_CONFIRM_EMAIL_ON_GET = True ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = “mandatory”

Email backend settings for Django EMAIL_BACKEND = ‘django.core.mail.backends.smtp.EmailBackend’ ` Finally, ı got Could not login on the server My docker logs > Error: Request failed with log.txt status code 502. “Bad Gateway” error

0reactions
giordifungulacommented, Nov 30, 2021

What Im currently trying to do.

I am using this link to try and fix the issue of disabling self sign up on the login page.

What steps I have done

  • cd into cvat/settings
  • cp base.py base.py.backup
  • open base.py
  • added ACCOUNT_AUTHENTICATION_METHOD = ‘username’ inside base.py
  • added ACCOUNT_CONFIRM_EMAIL_ON_GET = True inside base.py
  • added ACCOUNT_EMAIL_REQUIRED = True inside base.py
  • added ACCOUNT_EMAIL_VERIFICATION = ‘mandatory’ inside base.py
  • ran docker-compose -f docker-compose.yml -f docker-compose.dev.yml -f build
  • ran docker-compose -f docker-compose.yml -f docker-compose.dev.yml -f up -d

How am I running CVAT:

  • I have an ec2 instance running version cvat:master branch changes on top of a version that I had running that had the proxy with the nginx server configured in the docker file.
  • When I run commands sudo docker-compose -f docker-compose.yml -f docker-compose.dev.yml build and sudo docker-compose -f docker-compose.yml -f docker-compose.dev.yml up -d to build the docker images
  • I’m unable to login as any users after these configs were applied to the base.py file and I build the docker images too.
  • I, however, noticed that there is now a toast saying “You are not verified”, if you try and log in as a user that is not verified, but no one is able to login.
  • See screenshots below on what the output is Screenshot 2021-11-30 at 19 56 21

Note:

  • It looks like when I reset the default base.py settings and add back the old configs it works fine, however, the problem still persists about users being able to automatically login without being verified by the admin.
  • However, I would like those configs added ACCOUNT_AUTHENTICATION_METHOD = ‘username’ inside base.py
  • added ACCOUNT_CONFIRM_EMAIL_ON_GET = True inside base.py
  • added ACCOUNT_EMAIL_REQUIRED = True inside base.py
  • added ACCOUNT_EMAIL_VERIFICATION = ‘mandatory’ inside base.py to be added to my base.py file but I would like to be able to login as any user and also only be able to login after admin verifies the user.
  • Please let me know if you can replicate this issue or if you can advise on how to get this working whilst still being able to login as any user and keep the latest configs
Read more comments on GitHub >

github_iconTop Results From Across the Web

'Google email verification' message - Google Account Help
If you received an account verification email in error, it's likely that another user accidentally entered your email while trying to recover their...
Read more >
How to troubleshoot email verification errors - Human Support
If you encounter an error message during the email verification process or are not receiving your verification email, there are a few steps ......
Read more >
Troubleshooting your email verification issues
Verification link not working. If the verification link doesn't work, clear your browser cache. Next, go to your Flodesk account and request another ......
Read more >
Email address verification issues - Atlassian Support
Troubleshoot issues with verifying your Atlassian account email address when you don't receive a verification email or can't click its links.
Read more >
I did not receive the verification email
The most common reasons that prevent you from receiving the verification email in your inbox and how to fix them.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found