# QUIC Misconfigured on Synology

**URL:** <https://forum.storj.io/t/quic-misconfigured-on-synology/17690>\
**Category:** troubleshooting\
**Tags:** quic-udp, synology-nas\
**Created:** [March 11, 2022, 4:21pm UTC](https://forum.storj.io/t/quic-misconfigured-on-synology/17690 "2022-03-11T16:21:53Z")\
**Posts on this page:** 1\
**Showing post:** 46

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [July 15, 2025, 3:50pm UTC](https://forum.storj.io/t/quic-misconfigured-on-synology/17690/46 "2025-07-15T15:50:14Z")

</div>

> [@xavidpr4](#):
>
> What do you mean by bind it to an interface address explicitly 😘, not 0.0.0.0?

> [@\[Workaround\] QUIC misconfigured](https://forum.storj.io/t/workaround-quic-misconfigured/30006):
>
> Continuing the discussion from [Binding to a specific interface to stabilize QUIC connectivity](https://forum.storj.io/t/binding-to-a-specific-interface-to-stabilize-quic-connectivity/23601): Evidently, two things need to be true for QUIC to work: As indicated in the linked post, the interface address must be explicitly included in the server.address; e.g.: server.address: 10.0.17.120:28967 The port advertised in contact.external-address and forwarded to the node must be the same. I.e. if you advertise port 28967 in contact.external-address: icecream.example.com:28967 you shall als…

Confirm you implemented all three recommendations and still see issues.

---

_[View the full topic](https://forum.storj.io/t/quic-misconfigured-on-synology/17690)._