Elastic Email is not working in Laravel

So if this is not working the only thing that can be wrong are the credentials. I've read that elasticemail sometimes requires you to use the api key as the username, depending on how you registered. You could give that a try?

Otherwise ask support for the correct credentials ;)

@BOBBYBOUWMANN - i tried the above method but it didnt work, the API key and the password are the same in the elasticemail settings.

I used the same credentials in local environment and it was working fine without any issue.

The problem is with the production environment

i tried using some elastic mail wrappers too, but they are working in local but not in production. Can someone please help me here?

We need more information to help you! More logs and so on!

@BOBBYBOUWMANN - Sure, how can I get the logs

You can see the logs in storage/logs. If there is nothing you might even your your php-fpm logs

Looks like my .env is caching. The changes i am making to this file is not reflecting.

I tried to clear the cache using

php artisan cache:clear
php artisan config:clear
php artisan route:clear
php artisan config:cache
php artisan route:cache
php artisan optimize

then i am getting this error

   LogicException  : Unable to prepare route [api/user] for serialization. Uses Closure.

  at /var/www/laravel/vendor/laravel/framework/src/Illuminate/Routing/Route.php:917
    913|      */
    914|     public function prepareForSerialization()
    915|     {
    916|         if ($this->action['uses'] instanceof Closure) {
  > 917|             throw new LogicException("Unable to prepare route [{$this->uri}] for serialization. Uses Closure.");
    918|         }
    919|
    920|         $this->compileRoute();
    921|

  Exception trace:

  1   Illuminate\Routing\Route::prepareForSerialization()
      /var/www/laravel/vendor/laravel/framework/src/Illuminate/Foundation/Console/RouteCacheCommand.php:62

  2   Illuminate\Foundation\Console\RouteCacheCommand::handle()
      /var/www/laravel/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:29

  Please use the argument -v to see more details.

How to solve this issue?

You can ignore that error. Its when you try to cache the routes, and the default routes/api.php contains a closure.

If you don't have any API routes, just clear that file out

To check your mail config, open tinker and type

>>> config('mail')

check the values there are what you expect

If you have # in your mail provider API key or password, make sure you put quotes around the string

@SNAPEY - i did config('mail') and it matches what I intend to. And also checked the quotes around password.

The issue here is, when i trigger a mail, it is sending to mailtrap which i used for testing purpose but now i have replaced it with elastic mail credentials, but the mail is being received in mailtrap.

Well tinker shows you exactly what the application is using, after caching, and after the .env data is imported into the config/mail.php file.

It does not make sense that "Host" could be elasticmail but the mail turn up at mailtrap

i will hard code the credentials into the mail.php file and see if that works.

Email not working can have more than dozen of reasons, it's better to check the log first, either laravel or the server log may helpful to identify the root cause.

By the way, is the elasticemail_username using full email address?

In this case, i would first simply telnet to smtp port from the server and test out the credential with the server and send a message through smtp protocol.

hardcoding the email credentials in mail.php should give exactly the same outcome as you see in Tinker?

@GOUSEFEROZ - reverse back the steps you changed one by one and dd() out the credentials of each point before it hit to find out the real cause of the issue.

I came across this post: https://stackoverflow.com/a/49819941 I am on cloudways as well, it is weird, but the API key works in place of user name and password. Since I signed up for elastic email through cloudways, all what cloudways provided was API key, no other instructions. Still not sure is that how it suppose to be.