wireapp / wire-server

🇪🇺 Wire back-end services
https://wire.com
GNU Affero General Public License v3.0
2.62k stars 324 forks source link

Error connect to wire-server #343

Closed sd166 closed 5 years ago

sd166 commented 6 years ago

Started, when I try to authorize, I get an error. In the twillio and nexmo files are indicated the SID and API key

wirewebapp what to do? what is the problem?

and console [nginz] 192.168.186.1 - - [24/May/2018:05:37:51 -0700] "POST /login/send HTTP/1.1" 400 98 "http://192.168.186.140:8888/login/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36" "-" - 5 0.604 0.604 - - - 4028c12b125e0785f1c4af81b77dadfe [brig] D, code=400, label=invalid-phone, request=4028c12b125e0785f1c4af81b77dadfe, "Invalid mobile phone number."

neongreen commented 6 years ago

The 999 area code doesn't exist in Russia, and Twilio is smart enough to detect it. Try with a real phone number and ping us again if it doesn't work.

sd166 commented 6 years ago

@neongreen
In Russia there is a code 999 it uses Megafon. But also I use the real phone number which starts at 926 error also.

tiago-loureiro commented 6 years ago

It seems that you are trying to login (see the path is /login/send) and not register (the path should look like /register. Try using the path http://..../auth/#createaccount

Note that if you use the webapp, you are only able to create accounts using email.

sd166 commented 6 years ago

@tiago-loureiro Yes, I'm using webp. Or are there other options? How in webapp do I use registration and authorization over the phone?

The http://----/auth/ page is only available on the local computer on port 8088 which is not accessible from outside

I go to the address "http://192.168.186.140:8888/login/#register" all the same error.

When you try to go to http://192.168.186.140:8888/auth/#createaccount

wirewebapp_auth

Starting the webapp on the local computer

ubuntu_wire

neongreen commented 5 years ago

Closing because it's an old issue and webapp might have gotten better in the meantime 🙂 Please try to reproduce and if the problem still exists, open a new issue.