-
Notifications
You must be signed in to change notification settings - Fork 8
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
Clearer set-up documentation #26
Comments
Just a follow-up on this as I also struggled to figure out what was needed. Domain API Key In there create a new API key Endpoint https://api.mailgun.net/v3/YOUR_DOMAIN_NAME/messages But if your using EU location use: https://api.eu.mailgun.net/v3/YOUR_DOMAIN_NAME/messages Storing these all as env vars in the
Would be good if this was in the docs so it didn't waste time digging around to find this though! |
Thats great thanks Jason. Out of curiosity with the domain part did you include the 'mg' segment that Mailgun adds?
or just
|
@mattias78 I didn't, I think the Domain is just how you add the domain in Mailgun. I suppose if you've added it with a subdomain (It suggests doing this doesn't it) then you would add it in. But we don't add any subdomains on. |
Thanks for this info - I was having trouble too. Worth noting that if you're using the sandbox domain for testing, the test will only work if you add yourself as an Authorised Recipient in Mailgun |
Thanks for the instructions! Definitely worth P&T doing a quick update of the docs/readme. |
Thanks for your help everyone above, but none of that was working for me. What did work for me was:
I didn't create an API key (well, I did - but it did nothing!). Instead I used the "HTTP webhook signing key" from 'Sending > Webhooks'. Why? No idea. But it works. (Things were a lot clearer using Postmark, but a lot cheaper using Mailgun) |
Description
With the set-up instructions it would be great if it could clearly communicate:
The text was updated successfully, but these errors were encountered: