Mailtrap laravel

Change in your mail.php

'username' => env('username i got from mailtrap'),
'password' => env('password i got from mailtrap'),

to

'username' => env('MAIL_USERNAME'),
'password' => env('MAIL_PASSWORD'),

The first parameter you pass to env() method is the config key, and not the default value. You could pass the default value as second parameter, likewise:

'username' => env('MAIL_USERNAME', 'your username'),
'password' => env('MAIL_PASSWORD', 'your password'),

What you have done is told your application to look for config with key in the .env file. So if your username on mailtrap was "foobar", your app was looking for config with key "foobar", instead of MAIL_USERNAME.

Hope that helps.

@toniperic I thought that could be it, however I assumed (maybe incorrectly) that @hachiman wrote pseudocode.

@mstnorris what's pseudocode? Think that's copy/pasted from his mail.php file.

It's that he's referencing "username i got from mailtrap" key from his .env file, which obviously doesn't exist, hence the authorization failed.

Pseudocode is an informal high-level description of the operating principle of a computer program or other algorithm. It uses the structural conventions of a programming language, but is intended for human reading rather than machine reading.

As in, I think he removed the sensitive parts in order to post on here, I don't think that is their actual file.

As in, I think he removed the sensitive parts in order to post on here, I don't think that is their actual file.

@mstnorris, yeah ofcourse he'd hide the credentials. I was asking what's pseudocode'ish in his post.

If you substitute the "username i got from mailtrap" with "mstnorris" (if that was the username on mailtrap), what his app was doing is looking at the .env file for config with key of "mstnorris" instead of key MAIL_USERNAME. His .env file has a key of MAIL_USERNAME, but there's no key with "mstnorris" (per se).

Put simply, it should be this:

MAIL_USERNAME=mstnorris

and what his mail.php file is after is

mstnorris=someValue

which of course doesn't work.

dont forget to restart the server after changing .env file... or the changes wont take effect

@milewski restart what server?

You don't have to restart your server for changes in .env files.. not sure where you got that from? @milewski

Restarting artisan serve did the trick for me, for some reason. shrugs

@faylite yeah works for me too. Thanks!

Same here, (restarting artisan served fixed it)...I thought .env file changes were reloaded every time without need to reset, but apparently there is some additional layer that this clears.