-
Notifications
You must be signed in to change notification settings - Fork 1
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
checking the PM2 logs gives me this #2
Comments
Alright, I fixed this by adding the CORS module to the app, now it seems to be running. But the mailgun.myurl.com/api/submit/:mail Does just return me an error page of my main website. Do you have any idea how to fix this? Sorry for bothering. I'm still pretty new to all this stuff |
@jaapbakker88 have you configured your config file with the correct mailgun parameters? You can try using your sandbox credentials locally. |
Hi Jaappakker, Have you added the correct credentials for Mailgunner for accessing the API? Regards James Murphy Founder, Devangst Enterprises Ltd On Wed, 17 Aug 2016 at 14:54, jaapbakker88 notifications@github.com wrote:
|
@jaapbakker88 just remembered. When you're hosting mailgunner you also need to make sure you can send and receive mail to the Mailgun API. Make sure you've added the CNAME etc. records. See: https://documentation.mailgun.com/quickstart-sending.html |
I'll try setting up everything from scratch again. Does the mailgun domain have to be the same one as the one I'm hosting the script? Eg. Mailgun domain: mg.example.com and domain where I'm hosting and sending from: somethingelse.nl Jaap Bakker On za 27 aug. 2016 at 21:52 James Murphy <
a, pre, code, a:link, body { word-wrap: break-word !important; } https://github.com/jaapbakker88 See: — You are receiving this because you were mentioned. Reply to this email directly, |
Realised I didn't answer the last question. No the domain can be different. There's no cross-domain restrictions as far as I know. Not from the local server anyway. |
I'm on Ubuntu 14.04
NPM 2.15
Node 4.4.7
The text was updated successfully, but these errors were encountered: