Connection to smtp host fails
Posted: Thu May 09, 2024 6:46 pm
Version of script: 3.4.3
Hello,
We moved our Hesk installation to a different hosting company today but the send mail is failing when click the Test SMTP Connection button with this error:
======================
2024-05-09 18:36:51 Connection: opening to xxxxxxx.com:587, timeout=20, options=array()
2024-05-09 18:36:53 Connection failed. Error #2: stream_socket_client(): unable to connect to xxxxxxxx.com:587 (Connection refused) [/home/xxxxxx/domains/xxxxxxxx.support/public_html/vendor/phpmailer/phpmailer/src/SMTP.php line 397]
2024-05-09 18:36:53 SMTP ERROR: Failed to connect to server: Connection refused (111)
=========================
The settings on the smtp host have NOT been changed, we use TLS for encryption.
The ONLY thing that has changed is the IP address of the new hosting account where Hesk has been moved to.
We did not change the smtp username or password.
There is NO block for the new ip address in the UFW firewall on the smtp host, but for good measure we still added an allow rule for the new ip, but this made no difference.
What is causing this??
Hello,
We moved our Hesk installation to a different hosting company today but the send mail is failing when click the Test SMTP Connection button with this error:
======================
2024-05-09 18:36:51 Connection: opening to xxxxxxx.com:587, timeout=20, options=array()
2024-05-09 18:36:53 Connection failed. Error #2: stream_socket_client(): unable to connect to xxxxxxxx.com:587 (Connection refused) [/home/xxxxxx/domains/xxxxxxxx.support/public_html/vendor/phpmailer/phpmailer/src/SMTP.php line 397]
2024-05-09 18:36:53 SMTP ERROR: Failed to connect to server: Connection refused (111)
=========================
The settings on the smtp host have NOT been changed, we use TLS for encryption.
The ONLY thing that has changed is the IP address of the new hosting account where Hesk has been moved to.
We did not change the smtp username or password.
There is NO block for the new ip address in the UFW firewall on the smtp host, but for good measure we still added an allow rule for the new ip, but this made no difference.
What is causing this??