# Sidekiq TCP Error solved by using port 587 (not 25)

**URL:** <https://meta.discourse.org/t/sidekiq-tcp-error-solved-by-using-port-587-not-25/245275>\
**Category:** Self-hosting\
**Created:** [November 11, 2022, 4:38am UTC](https://meta.discourse.org/t/sidekiq-tcp-error-solved-by-using-port-587-not-25/245275 "2022-11-11T04:38:32Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![spectre](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/spectre/32/274073_2.png) [@spectre](https://meta.discourse.org/u/spectre)\
**Post date:** [November 13, 2022, 9:58pm UTC](https://meta.discourse.org/t/sidekiq-tcp-error-solved-by-using-port-587-not-25/245275/12 "2022-11-13T21:58:08Z")

</div>

I had this response from mailersend support;

> It seems like you’re using port 25 _**“[smtp.mailersend.net:25](http://smtp.mailersend.net:25)”**_ hence the error, at the time we only support 587 with TLS encryption.

Port **25** was default port on the setup credentials. But changed it right away to **587** and things are super smooth now 🥳

Problem SOLVED

---

_[View the full topic](https://meta.discourse.org/t/sidekiq-tcp-error-solved-by-using-port-587-not-25/245275)._
