Account verification email not being sent

[pesfahanian]

Hi!
I cloned the GitHub repo, and followed the instructions in the README carefully.
Migrations worked and python manage.py runserver runs ok.
When I try to sing up for a new account, I get this on the terminal:

System check identified no issues (0 silenced).
March 20, 2021 - 09:40:24
Django version 3.0.8, using settings 'auth_system.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
[20/Mar/2021 09:40:30] "GET / HTTP/1.1" 200 2365
[20/Mar/2021 09:40:30] "GET /static/js/2.304b9161.chunk.js HTTP/1.1" 304 0
[20/Mar/2021 09:40:30] "GET /static/js/main.a93af782.chunk.js HTTP/1.1" 304 0
[20/Mar/2021 09:40:30] "GET /favicon.ico HTTP/1.1" 200 2365
[20/Mar/2021 09:40:30] "GET /manifest.json HTTP/1.1" 200 2365
[20/Mar/2021 09:40:32] "GET /favicon.ico HTTP/1.1" 200 2365
Unauthorized: /auth/users/
[20/Mar/2021 09:41:16] "OPTIONS /auth/users/ HTTP/1.1" 401 58

Moreover, I am not getting any account verification email on the email address I used for sign up.
Appreciate the help!

[ayaachi-jha]

I would suggest checking the spam folder once.

[revenge47]

did you manage to fix this issue? the spam folder doesnt have the email

[Kirats2]

the bug is that if there is a capital letter in the email, you will not receive the letter

[revenge47]

thanks. also realized that you have to use the 'email' name variable. I was using 'Email Address'

[Shaishav0507]

When I'm trying to Sign Up getting this but not email.
On searching on net it seems 200 Http code is for success.
Any idea how to rectify the mistake

[linkedweb]

The success status code for Djoser's signup endpoint is a 201 I'm not sure what's causing it to not work in your case as I'd need to see more of your code, could be a number of different things If you have your code on a github repository you can always send over a link and I can check it out

…

On Sat, 12 Feb 2022 at 03:27, Shaishav Rastogi ***@***.***> wrote: [image: image] <https://user-images.githubusercontent.com/77338581/153703663-be90db45-8479-44bf-bee0-0b4b485fcb7e.png> When I'm trying to Sign Up getting this but not email. On searching on net it seems 200 Http code is for success. Any idea how to rectify the mistake — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASCZNTGG5D2KD7NXG5JRYJDU2YKXHANCNFSM4ZQITKIA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Shaishav0507]

This is the link for Backend : https://github.com/Shaishav0507/Project/tree/main/backend
This is the link for Frontend: https://github.com/Shaishav0507/Frontend/tree/main

Where as API endpoints on Postman are working completely fine.

Please help me out in this. It would mean a lot.
Thanks you so much.

[linkedweb]

Also another thing to add, it you run your project on say 127.0.0.1:8000 instead of localhost:8000, you will also need to add this into your CORS_ALLOWED_ORIGINS setting so you can make requests from 127.0.0.1:8000 to localhost:8000 as these domains differ

…

On Mon, 14 Feb 2022 at 09:28, Bryan Dunn ***@***.***> wrote: So I ran your code, except I updated the EMAIL_HOST_USER and EMAIL_HOST_PASSWORD to be one of my gmail accounts, and everything worked perfectly with the code you sent me. The user got created, and the activation email got sent. This means there's nothing I can really help with since what you sent me works. Also I added in django cors headers so that I could run the frontend on localhost:3000 and make requests to the backend on localhost:8000, I think this would be good for you to do to make development a bit easier. You would just do a "pip install django-cors-headers", add "corsheaders" into your INSTALLED_APPS, place 'corsheaders.middleware.CorsMiddleware' in your MIDDLEWARE setting above the CommonMiddleware, and somewhere in the settings file: CORS_ALLOWED_ORIGINS = [ 'http://localhost:3000', ] This will make development much easier On Sun, 13 Feb 2022 at 22:34, Shaishav Rastogi ***@***.***> wrote: > This is the link for Backend : > https://github.com/Shaishav0507/Project/tree/main/backend > This is the link for Frontend: > https://github.com/Shaishav0507/Frontend/tree/main > > Please help me out in this. It would mean a lot. > Thanks you so much. > > — > Reply to this email directly, view it on GitHub > <#1 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ASCZNTCWZUU3FIFTYP7J2ALU3BZ33ANCNFSM4ZQITKIA> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you commented.Message ID: > ***@***.***> >

[linkedweb]

So I ran your code, except I updated the EMAIL_HOST_USER and EMAIL_HOST_PASSWORD to be one of my gmail accounts, and everything worked perfectly with the code you sent me. The user got created, and the activation email got sent. This means there's nothing I can really help with since what you sent me works. Also I added in django cors headers so that I could run the frontend on localhost:3000 and make requests to the backend on localhost:8000, I think this would be good for you to do to make development a bit easier. You would just do a "pip install django-cors-headers", add "corsheaders" into your INSTALLED_APPS, place 'corsheaders.middleware.CorsMiddleware' in your MIDDLEWARE setting above the CommonMiddleware, and somewhere in the settings file: CORS_ALLOWED_ORIGINS = [ 'http://localhost:3000', ] This will make development much easier

…

On Sun, 13 Feb 2022 at 22:34, Shaishav Rastogi ***@***.***> wrote: This is the link for Backend : https://github.com/Shaishav0507/Project/tree/main/backend This is the link for Frontend: https://github.com/Shaishav0507/Frontend/tree/main Please help me out in this. It would mean a lot. Thanks you so much. — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASCZNTCWZUU3FIFTYP7J2ALU3BZ33ANCNFSM4ZQITKIA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[Shaishav0507]

Thank you so much.
Now I'm able to receive email
But how to activate over their only or should I use postman to activate it.
Last help Please

[Shaishav0507]

Getting this when I'm clicking on activate email

[Shaishav0507]

Not able to activate.
Made the changes what you told me do so.
But still not able to activate it.

[Shaishav0507]

Gives this error on web

[linkedweb]

The code you sent me works, however I also reorganized the folder structure which I think the folder structure in your case is probably causing the issue of not finding the build folder which is the template. You had a backend folder, and inside of that had an Auth folder, and inside that had your Auth project folder, accounts app, and Estimate app. What I did was take the 3 folders out of the Auth folder and placed them in the backend folder. So I have one backend folder, and inside of there have the Auth project folder, accounts app folder, Estimate app folder, the virtual environment folder, manage.py file, and then have the build folder get placed inside of the backend folder. Inside of the TEMPLATES setting DIRS option, you have os.path.join(BASE_DIR, 'build'), and with your current folder structure when your build folder is inside the backend folder it won't find it as that's not the current working directory. So by changing the folder structure of your backend or having the build folder get placed in backend/Auth with your current folder structure, your backend should find the template and your code will work. So really the only thing going wrong is the folder structure, in terms of your code everything works.

…

On Tue, 15 Feb 2022 at 04:10, Shaishav Rastogi ***@***.***> wrote: [image: image] <https://user-images.githubusercontent.com/77338581/154029568-82bf1632-9469-4d3c-930a-eff6f2527049.png> Gives this error on web — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASCZNTGZJJGKWTEASV7UQE3U3IKANANCNFSM4ZQITKIA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[Shaishav0507]

Thank you so much
Everything working now
Thank you so much.