Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

email adapter error #1338

Closed
thamer898 opened this issue Apr 2, 2016 · 34 comments
Closed

email adapter error #1338

thamer898 opened this issue Apr 2, 2016 · 34 comments

Comments

@thamer898
Copy link

Hello

please find attached an error screenshot after i added an email adapter to allow user to reset password ? kindly advice
error-email-adapter

Regards

@tanmays
Copy link

tanmays commented Apr 2, 2016

Are you sure you are running parse-server v2.2.4? parse-server-simple-mailgun-adapter dependancy is provided along with the latest parse-server release.

In your packages.json file make sure its: "parse-server": "2.2.4"after that run npm install to update it.

@thamer898
Copy link
Author

okay i will try it now .

@flovilmart
Copy link
Contributor

If that doesn't work, install with npm install --save parse-server-simple-mailgun-adapter

@thamer898
Copy link
Author

Hello

after i updated my parse server to be 2.2.4 everything work in server but when i try to reset my password by enter my email , am not receive any emails in my inbox .

please advice .

Regards

@thamer898
Copy link
Author

okay now am received the email in my inbox but the link not clickable and the link start with this word "undefined" ? can you help me please ?

@flovilmart
Copy link
Contributor

did you set publicServerURL in your options?

@thamer898
Copy link
Author

no

@flovilmart
Copy link
Contributor

then that's the issue, this value should be set as a publicly accessible URL to your parse server

@thamer898
Copy link
Author

can you give me an example please ?

@thamer898
Copy link
Author

How to set the vaule @flovilmart ?

@flovilmart
Copy link
Contributor

it's in the documentation: https://github.com/ParsePlatform/parse-server#email-verification-and-password-reset

Before reporting issues, can you please make sure that you configure your system according to the documentation?

@thamer898
Copy link
Author

thank you very much i will try it now .

@flovilmart
Copy link
Contributor

Please only use the issues on github to report real issues, not configuration errors.

Thanks

@thamer898
Copy link
Author

thank you very much but when i clicked the link this error appear
"The requested document was not found on this server."

@flovilmart
Copy link
Contributor

what did you set as publicServerURL?

if serverURL is http://localhost:1337**/parse** then publicServerURL should be http://example.com/parse

@thamer898
Copy link
Author

i do exactly as you said before publicServerURL http://example.com/parse but when click the link error 404 appear when try to reset password ?

@tanmays
Copy link

tanmays commented Apr 3, 2016

@thamer898 by example.com he meant the public facing URL of you app and not literally example.com. For instance if its hosted on Heroku it will be something like: http://yourappname.herokuapp.com/parse

For testing locally use something like ngrok, then your public facing URL will be something like http://xxxxxx.ngrok.io/parse/

Install ngrok on your system, then run ngrok http 1337

@thamer898
Copy link
Author

i have a domain name but when click the link this error appear as you see in the picture .
error-404

@flovilmart
Copy link
Contributor

What is the URL?

@thamer898
Copy link
Author

localhost

@flovilmart
Copy link
Contributor

localhost is not a URL!

What is the link you receive that is not working?

@thamer898
Copy link
Author

sorry i have this domain name privatchat.chat i think the page not found on the server ?

@flovilmart
Copy link
Contributor

@thamer898 if you want us to help, you need to answer the question, what is the link that you receive in the email?

@flovilmart
Copy link
Contributor

  1. your publicServerURL should not have a trailing /, it should be https://privatechat.chat/parse
  2. second, it doesn't seem that the parse-server is deployed on that server as I'm unable to query the default classes and get the unauthorized error.

@thamer898
Copy link
Author

but i can do all the operations like insert and delete images , sign in / up users !

@tanmays
Copy link

tanmays commented Apr 3, 2016

Are you running parse-server locally or is it deployed on a server? If locally then follow the steps I gave above to configure ngrok, use it as publicServerURL and it will work.

@thamer898
Copy link
Author

i deployed parse server on a windows server 2012 , but i think the reset password html page not found so i face the 404 error ? is it right .

@tanmays
Copy link

tanmays commented Apr 3, 2016

You are facing the 404 because parse-server was not found on that URL. I'm not sure how windows server works, but if it has a static IP address you could use that too, something like http://xx.xx.xx.xx:port/parse

I think its better you ask this and any future configuration related questions over at Stackoverflow

@thamer898
Copy link
Author

okay i have ssl connection how to allow connection using https i think this the error since am using http only ?

@flovilmart
Copy link
Contributor

@thamer898 this issue is getting out of hands now, this is a deployment and configuration problem on your side, and not related at all with an issue on parse-server.

I'm locking that conversation for now as this repository is not a live support for deploying parse server.

From what I can see, your server is not correctly deployed to the domain you pointed to. As @tanmays mentions, you may find a better answer on stack overflow.

@thamer898
Copy link
Author

okay thank you do you have an account on stackoverflow ?

@flovilmart
Copy link
Contributor

yes I do, but I don't answer parse-server deployment related questions.

@thamer898
Copy link
Author

okay thank you very much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants