# Ziti-router: no network interface found for 0.0.0.0

**URL:** <https://openziti.discourse.group/t/ziti-router-no-network-interface-found-for-0-0-0-0/4370>\
**Category:** Ziti Overlay\
**Created:** [April 15, 2025, 4:00pm UTC](https://openziti.discourse.group/t/ziti-router-no-network-interface-found-for-0-0-0-0/4370 "2025-04-15T16:00:28Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![qrkourier](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/qrkourier/32/52_2.png) [@qrkourier](https://openziti.discourse.group/u/qrkourier)\
**Post date:** [April 15, 2025, 11:42pm UTC](https://openziti.discourse.group/t/ziti-router-no-network-interface-found-for-0-0-0-0/4370/8 "2025-04-15T23:42:50Z")

</div>

You'll be unable to manage shares and accesses or access the web console if the zrok controller isn't available.

An array of zrok controllers will behave as a single zrok instance if they share a PostgreSQL data source, which provides table locking.

You may scale out the zrok public frontends at will, optionally cloning a shared public frontend zrok environment since they always have the same authorizations.

The oauth frontend scales with the public frontend.

This PostgreSQL-specific locking configuration may be relevant if you're enforcing limits: [Configuring Limits | zrok](https://docs.zrok.io/docs/guides/self-hosting/metrics-and-limits/configuring-limits/#experimental-limits-locking)

---

_[View the full topic](https://openziti.discourse.group/t/ziti-router-no-network-interface-found-for-0-0-0-0/4370)._
