# Homey Self-Hosted Server on Synology | Megathread **URL:** \ **Category:** Homey Self-Hosted Server\ **Created:** [December 5, 2025, 2:14pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-synology-megathread/146437 "2025-12-05T14:14:25Z")\ **Posts on this page:** 1\ **Showing post:** 98
**Author:** ![Mantlet](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mantlet/32/121247_2.png) [@Mantlet](https://community.homey.app/u/Mantlet)\ **Post date:** [June 18, 2026, 12:24pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-synology-megathread/146437/98 "2026-06-18T12:24:32Z")
Just as a heads up, I think this is a common cause in Synology where IPv6 routes of this type are not available to the containers. If everything else in your network is setup correctly, this fixed matter over thread for me: > [@Issue with Matter on self hosted Homey](https://community.homey.app/t/issue-with-matter-on-self-hosted-homey/147203/86): > > This guide also helped me to setup matter over thread. Since I don’t have a Mac either, I’ve looked up the WIndows Powershell equivalent of the netstat command. I have found the IPv6 routing to my Google TV 4K, that acts as my Thread Border Router with this command: Get-NetRoute -AddressFamily IPv6 | Where-Object { $\_.DestinationPrefix -like "fd\*" } The result contains something like this: DestinationPrefix : fd\_\_:::1::/64 NextHop : fe::::: ifIndex : 12 You can then paste… --- _[View the full topic](https://community.homey.app/t/homey-self-hosted-server-on-synology-megathread/146437)._