Sam-R
commented
4 years ago Connection could not be established with host 127.0.0.1 :stream_socket_client(): unable to connect to 127.0.0.1:1025 (Connection refused)Do you know what is the reason of this error?
This error is generated when your (presumably) PHP docker container tries to connect to the SMTP server defined in your .env file and that connection fails due to the defined port/service not being open for communication.
A simpler version: your setup is trying to send an email to something that doesn't accept email.
In this case it's your local machine (127.0.0.1). This matches with what you had in your .env file MAIL_HOST=127.0.0.1. I would suggest that this is wrong, unless you're running your own SMTP server on your host machine (which I wouldn't reccomend for development).
Think of your environment a like this:
+-----+ +---------+ +-------+
| | | | | |
| PHP | | MailHog | | MySQL |
| | | | | |
+-----+ +---------+ +-------+
Docker Network
+---------------------------+
Host Machine
+---------------------------+
Host NetworkAnything on the "Docker Network" should be able to talk to anything else on the docker network by container name.
Docker network containers can talk to the host machine (127.0.0.1), but the host machine can't talk to docker containers without their ports being exposed (done by -P or the ports: heading in docker-compose.yml).
In your case your docker container is trying to talk to the host (127.0.0.1), not another container. Because of this you can't catch mail with Mailhog.
If you change your .env for PHP/Larvel to talk to the name of the Mailhog container, it should work.
A caveat to this is that Docker can run multiple named networks. You'll see in my docker-compose file I've named the network laravel and every container is within this network.
If your configuration has the Mailhog container outside of the named Docker network the rest of the containers are in, it could affect communication because the two networks can't talk to eachother (based on my understanding).
Docker Network
+-----------------------------+
|Docker "Laravel" Network |
+------+ +--------+ +---------+
|| | | || | |
|| PHP | | MySQL || | MailHog |
|| | | || | :-( |
|------+ +--------| +---------+
+-----------------------------+
+-----------------------------------------------------+
Host Machine
So, only it can works if the reference is "mailhog"? and it is impossible that works if it is apply another name?
No matter what you name your container for "mailhog" it should still work. I think you only need to change it in three places:
[docker-compose.yml]
# Mailhug (Optional, mail-catcher)
development-mail-catcher-service: # <---- I've renamed the "mailhog" container
image: mailhog/mailhog
networks:
- laravel
ports:
- 8025:8025Since docker-compose creates the container, it has to know what it calls it.
[Dockerfile.app]
# Setup msmtp for PHP mail() command (Replaces abandoned ssmtp package in Debian)
RUN echo '\n\
host development-mail-catcher-service\n\ # <---- I've renamed the "mailhog" container
port 1025\n\
from php-dev@example.com\n' \
>> /etc/msmtprc
RUN echo 'sendmail_path = /usr/bin/msmtp -t' >> /usr/local/etc/php/php.ini
I've built this image with a different SMTP package - see: https://github.com/mailhog/MailHog#sendmail
The idea is this catches all mail send by PHP's mail() function. You can delete this section from the Dockerfile.app if you want, it is not required if your .env is setup for Laravel.
[.env]
MAIL_MAILER=smtp
MAIL_HOST=development-mail-catcher-service # <---- I've renamed the "mailhog" container
MAIL_PORT=1025
MAIL_FROM_ADDRESS=test@example.com
MAIL_FROM_NAME="${APP_NAME}"Since your PHP/Laravel application needs to know how to send emails to the container you need the MAIL_HOST to match.
I hope this helps you in some way. I am still learning Docker myself, so I may have mistakes in my setup or explanation.
zacktagnan
Hi Sam:
We were talking about how to configure the "docker-compose.yml" and the Laravel ".env" file on the chat of the Erika Heidi dockercon session (about "How to Create PHP Development Environments with Docker Compose") ... Maybe you remember our conversastion.
So, I download your repo and try it and the sending emails process works fine. No like mine. The configuration of my "docker-compose.yml" and ".env" is similar to yours, but, when I launch the process to send and email, I have this message error on the browser:
Do you know what is the reason of this error? I had the
MAIL_HOST=127.0.0.1but, after heard your advice, I changed it to the name of my Mailhog service name. But even with that, I also don't fix the error, even if I follow your suggestions and put the same MAIL environment variables on the ".env" file. The error I receive is the same.On the other hand, I realize that you name the MailHog service like "mailhog", the same reference for MAIL_HOST, and another inside the Dockerfile:
[docker-compose.yml]
[Dockerfile.app]
[.env]
MAIL_HOST=mailhogBut, if the name of the services in the "docker-compose.yml" is a random personal choice, that is, that it is possible to put the name that you want to each service, then, if I replace "mailhog" with "mailhog_server" in the 3 references mentioned above, why the email sending process fails showing this error message?:
...even if rebuild the "php" service image with this command when I up the services:
docker-compose up -d --build
Where can a reference to the previous term persist (which, supposedly, would no longer have to exist after the change mentioned in each of the 3 files), even after a reconstruction of the "php" service?
So, only it can works if the reference is "mailhog"? and it is impossible that works if it is apply another name? Why?
And, another more question ... Is it necessary to put the Mailhog lines on the Dockerfile so that there can be a communication between the PHP application and the MailHog server and therefore the emails are sent? If you don't put this lines on the Dockerfile, the email sending process doesn't work? Where did you get the idea of putting that MailHog reference into the Dockerfile? I have not seen anything like it in the MailHog documentation and much less, they say it is necessary.
I would appreciate receiving a response from you ... Best regards.