The endpoint you've tried to access does not exist. Check your URL. about mailgun

[Bogardo]

On what event are you receiving this error? This exception is thrown in the mailgun-php package.

[jeffersonsetiawan]

I think it's because of how to get config variable in mailgun.

here is the snippet:
$this->from = Config::get('mailgun::from'); (Line 66)

I can solve it by changing Config::get('mailgun::from') to Config::get('mailgun.from')
(Laravel 4 use . instead of ::) @nu1ww.

Notes: change all :: to . in vendor/bogardo/mailgun/src/Bogardo/Mailgun/Mailgun.php

I know it is bad practice to changing file in vendor, but It works.

[danbovey]

As far as I can tell, support for Laravel 4.2 is broken in this package because of this issue.

So I've forked this repo and reset it back to the last commit where the package supported Laravel 4.x and changed all of the config keys to use . as a separator.

If @Bogardo can accept the pull request my fork into the develop branch (if I'm right in thinking that's the branch for legacy Laravel stuff). Or potentially if :: is used on a Laravel version I don't know about, merge it into a new branch called 4.2.

Thanks!

[Bogardo]

I'm pretty sure Laravel 4.2 uses a :: for accessing a package configuration file.
See https://laravel.com/docs/4.2/packages#package-configuration

Or am I missing something?

[danbovey]

Ahhhh OK forgive me not understanding package config completely. As the artisan command is broken in older versions of this because it's not tagged properly (I think this is fixed in latest), I didn't know where to put it. I was getting the same thing as #53, and didn't think to check the README history.

I've fixed it for myself now by moving the config to app/config/packages/bogardo/mailgun/config.php instead of app/config/mailgun.php as the README states.

[Bogardo]

Please make sure you are using the correct version of this package for your version of Laravel.
If you are on Laravel 4.2, use version 3.1.* of this package.

[danbovey]

Yep using 3.1.7. It's just me and everybody else in this issue misinterpreting the new README file. So you can probably close this.