# Waarschuwing: Kon server TCP-luisterende socket niet maken \*:6379: bind: Adres al in gebruik

**URL:** https://meta.discourse.org/t/warning-could-not-create-server-tcp-listening-socket-bind-address-already-in-use/261100
**Category:** Self-hosting
**Created:** [9 april 2023 om 15:29 UTC](https://meta.discourse.org/t/warning-could-not-create-server-tcp-listening-socket-bind-address-already-in-use/261100 "2023-04-09T15:29:43Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [9 april 2023 om 20:21 UTC](https://meta.discourse.org/t/warning-could-not-create-server-tcp-listening-socket-bind-address-already-in-use/261100/4 "2023-04-09T20:21:41Z")

</div>

Possibly the MTU in the docker container? See

> [@Issue when installing new Discourse instance](https://meta.discourse.org/t/issue-when-installing-new-discourse-instance/259617/7):
>
> You can try lowering the MTU of the Docker interface:

---

_[View the full topic](https://meta.discourse.org/t/warning-could-not-create-server-tcp-listening-socket-bind-address-already-in-use/261100)._