{"id":2209,"date":"2024-09-02T11:38:48","date_gmt":"2024-09-02T11:38:48","guid":{"rendered":"https:\/\/www.devopssupport.in\/blog\/?p=2209"},"modified":"2024-09-14T07:35:49","modified_gmt":"2024-09-14T07:35:49","slug":"fixing-the-symfony-mailer-transportexception-connection-timeout-error","status":"publish","type":"post","link":"https:\/\/www.devopssupport.in\/blog\/fixing-the-symfony-mailer-transportexception-connection-timeout-error\/","title":{"rendered":"Laravel SMTP Mailer TransportException: Connection Timeout Error"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

While working on a project that involved sending emails through Amazon SES (Simple Email Service) using Symfony, I encountered a frustrating error. It looked something like this:<\/p>\n\n\n\n

Root Cause<\/strong><\/h3>\n\n\n\n

After reviewing the configuration, I realized that the error was due to a typo in my .env<\/code> file where the MAIL_PORT<\/code> was incorrectly set. I had mistakenly set MAIL_PORT=<\/code>111 instead of the correct value MAIL_PORT=111<\/code>. Port 222 is typically used for SMTP submission, while port 111 is incorrect, leading to the connection failure.<\/p>\n\n\n\n

The Solution<\/strong><\/h3>\n\n\n\n

To resolve this issue, I corrected the MAIL_PORT<\/code> <\/strong>in my .<\/code>env<\/code> <\/strong>file<\/p>\n\n\n\n

After making this change, the connection to the SMTP server was successfully established, and the emails were sent without any issues.<\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

More topics on Bug fixing:<\/strong><\/p>\n\n\n\n

\n
MySQL Error #1932: “Table Doesn’t Exist in Engine”<\/a><\/blockquote>