[solved] Authenticate Users with MetaMask using Python and Django

#1

Hello guys.

in this topic at the end of that when i want to start the application, every time i get an “authentication error”.
i searched about this problem and seems it backs to connecting metamask to a local domain. is it true?
if it’s true, so how could we solve this problem with the local domain?

#2

Can you give more info about that error? It is an error in MetaMask or in another place?

#3

this is a step-by-step screenshot after running the

1 (2)
1 (2)1939×620 43.3 KB
2 (2)
2 (2)1940×628 49.7 KB
3 (2)
3 (2)1929×394 28.6 KB
application with code on the Github repository.

#4

you have to change the domain that is set when the message is requested from authentication api. The domain has to march to domain that is accessed in the browser

#5

once i used the local IP and once I used my self-made local domain. every time I got a different error and got screenshot for you

127.0.0.11000web3_authmoralis_auth
127.0.0.11000web3_authmoralis_auth3181×710 284 KB
mylocaldomain.com
mylocaldomain.com1709×1359 309 KB
.

#6

try to use ngrok as a proxy and then use the domain with the subdomain obtained from ngrok
you don’t have to put there the complete path in the domain field, only the domain, like

4asiasdfhaiuhf.com

or a subdomain like

asdf.23432asdfasdf.com
#7

ngrok
ngrok2735×1354 314 KB

with the ngrok got this error and couldn’t go forward.

#8

remove that / from the end of the domain, maybe ngrok was not configured right, it should redirect all the request to your local server

you can use the application with that warning and fix it later, that is only an warning added recently by metamask extension to check that domain field that it matches with the domain from the browser

#9

even without / I have again the same error :frowning: . Now it does not even get to the metamask warning message. Even before, I was not really worried about the metamask warning message. It’s just that the code does not go through. I was getting “Authentication Error” at the end. That is what I am trying to resolve.

#10

was was causing the authentication error? was there any error message?

you have to sign that message faster than that timeout of 100 seconds

#11

yes I did even more faster than this.

#12

what was the error that you got in that case?

#13

nothing
nothing2774×1272 263 KB

after that red one in the terminal, nothing goes forward and no error appears to me.

#14

something doesn’t seem to work as expected here, it looks like /we3_auth/request_message returns a 403 status code

what happens when you try it without ngrok and you get that warning in metamask if you complete the authentication?

#15

Screenshot 2023-04-02 194100
Screenshot 2023-04-02 1941001683×1359 278 KB
3 (2)
3 (2)1929×394 28.6 KB

These two screenshots are related to when I used mylocaldomain.com as the domain.
and after I signed that warning, I got “authentication error”.

#16

you are running it with a debugger?

#17

I am using Visual Studio, and adding Breakpoint() and continue to debug. I am running the entire package using the terminal (command line) -> run server, just like instructions in the tutorial

#18

can you try without using the breakpoints to see what happens?

there is another step where it has to validate the signature at the end, between when the message is generated and and the signature is validate it has to take less than 100 seconds

#19

09090
090902850×1178 243 KB

yeah, I got you but the old authentication error still appears.

#20

it is a message expired error there, meaning that it took more than 100 seconds from the beginning when the message was requested from auth api until the signature was validated with the second request to auth api

1 Like