# Sidekiq TCP-fout opgelost door poort 587 te gebruiken (niet 25)

**URL:** <https://meta.discourse.org/t/sidekiq-tcp-error-solved-by-using-port-587-not-25/245275>\
**Category:** Self-hosting\
**Created:** [11 november 2022 om 04:38 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:** 7

<div class="post-metadata">

**Author:** ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)\
**Post date:** [12 november 2022 om 10:50 UTC](https://meta.discourse.org/t/sidekiq-tcp-error-solved-by-using-port-587-not-25/245275/7 "2022-11-12T10:50:05Z")

</div>

UFW is just a frontend for iptables that is just a fronend for packet controlling.

Using directly iptables gives more flexibility than UFW but it needs ipatables-persistent. But using iptables vs. UFW there is no bigger differences except two:

- with iptable order matters
- with iptable syntax matters

I would even say that mentioning of iptables is not enough when no one knows what you have there.

There is one small detail too. Docker just doesn’t care what you have done with iptables of VPS. Docker kind of bypasses it.

There is just one thing I don’t get: why are you using port 22?

---

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