ZeroUI - ZeroTier Controller Web UI - is a web user interface for a self-hosted ZeroTier network controller.
Go to file
dec0dOS 00592d9ad4 chore: fix prettier check script 2024-05-01 14:17:23 +01:00
.github ci: small changes 2023-10-04 21:40:02 +01:00
.husky chore(package.json): better dev tools 2021-03-29 01:13:34 +03:00
backend Merge pull request #182 from aruznieto/i18n 2023-10-19 19:52:38 +01:00
docker/zero-ui chore: upgrade yarn to v4 2023-10-25 17:13:21 +01:00
docs [ImgBot] Optimize images 2023-10-07 15:09:34 +00:00
frontend chore: run prettier 2024-05-01 14:16:43 +01:00
.dockerignore chore: small changes dockerfile 2023-10-04 21:56:47 +01:00
.gitignore Merge branch 'main' into feat-rateLimiter 2023-10-15 16:44:01 +01:00
.prettierignore chore: add lint command to package.json 2021-12-19 19:10:44 +03:00
.yarnrc.yml chore: upgrade yarn to v4 2023-10-25 17:13:21 +01:00 chore(release): 1.5.8 2023-10-04 22:46:46 +01:00
LICENSE docs(license): update license copyright 2021-05-10 12:45:38 +03:00 fix: login limiter, make it opt it by default 2023-10-16 17:47:32 +01:00
docker-compose.yml Bump zerotier container to 1.10.6 2023-09-12 10:22:19 +08:00
package.json chore: fix prettier check script 2024-05-01 14:17:23 +01:00
tsconfig.json chore: update typecheck 2023-10-04 20:09:38 +01:00
yarn.lock chore: fix merge errors 2024-05-01 14:14:31 +01:00


ZeroUI - ZeroTier Controller Web UI - is a web user interface for a self-hosted ZeroTier network controller.
Explore the screenshots »

Bug Report · Feature Request · Ask a Question

Table of Contents


This project drew inspiration from ztncui and was developed to address the current limitations of self-hosted network controllers. Some of the issues in ztncui cannot be resolved due to the core architecture of the project. ZeroUI aims to resolve these issues and introduces the following features:

  • It is a lightweight Single Page Application (SPA) built with React, providing an improved user experience, and it is mobile-friendly.
  • ZeroUI is compatible with the ZeroTier Central API, allowing you to use CLI tools and custom applications designed for ZeroTier Central to manage your networks.
  • ZeroUI implements controller-specific workarounds to address certain existing issues that are not addressed in ZTNCUI.
  • ZeroUI is more feature-complete, supporting almost all network controller features, including a rule editor. Development is ongoing, so you can expect regular updates with new features and bug fixes.
  • Deploying ZeroUI is straightforward; refer to the installation section for more information.
Curious about ZeroTier?

ZeroTier is an impressive open-source project available on a wide range of platforms. It can resolve many of your complex networking issues, potentially replacing your intricate VPN setups. You can create a virtual LAN and manage all your devices effortlessly.

In essence, ZeroTier combines the capabilities of VPN and SD-WAN, simplifying network management.

Built With



Ready-to-use deployment solution:

Getting Started


The recommended way to install ZeroUI is by using Docker and Docker Compose. To install Docker and Docker Compose on your system, please follow the installation guide in the official Docker documentation.

For HTTPS setup, you will need a domain name. You can obtain one for free at


Here's a straightforward one-minute installation guide, perfect for a fresh VPS setup:

  1. Create a project directory
mkdir -p /srv/zero-ui/
cd /srv/zero-ui/
  1. Download the docker-compose.yml file


curl -L -O
  1. Replace with your domain name and set admin credentials (ZU_DEFAULT_PASSWORD) in docker-compose.yml
  2. Pull the image
docker pull dec0dos/zero-ui
  1. Run the containers
docker-compose up -d --no-build
  1. Check if everything is okay (CTRL-C to stop log preview)
docker-compose logs -f
  1. Disable your firewall for the following ports: 80/tcp, 443/tcp, and 9993/udp
  • On Ubuntu/Debian with ufw installed:
ufw allow 80/tcp
ufw allow 443/tcp
ufw allow 9993/udp
  • Or you can use iptables:
iptables -A INPUT -p tcp --dport 80 -j ACCEPT
iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p udp --dport 9993 -j ACCEPT
  1. Navigate to Now you can use your ZeroUI instance with HTTPS support and automated certificate renewal.

To disable Caddy proxy and HTTPS, remove the https-proxy from docker-compose.yml, set ZU_SECURE_HEADERS to false, and change zero-ui port expose to ports.

Advanced manual setups are also supported. Check the following environment variables as a reference:

Name Default value Description
NODE_ENV unset You could learn more here
LISTEN_ADDRESS Express server listen address
ZU_SERVE_FRONTEND true You could disable frontend serving and use ZeroUI instance as REST API for your ZeroTier controller
ZU_SECURE_HEADERS true Enables helmet
ZU_CONTROLLER_ENDPOINT http://localhost:9993/ ZeroTier controller API endpoint
ZU_CONTROLLER_TOKEN from /var/lib/zerotier-one/authtoken.secret ZeroTier controller API token
ZU_DEFAULT_USERNAME unset (docker-compose.yml: admin) Default username that will be set on the first run
ZU_DEFAULT_PASSWORD unset (docker-compose.yml: zero-ui) Default password that will be set on the first run
ZU_DATAPATH data/db.json ZeroUI data storage path
ZU_DISABLE_AUTH false If set to true, automatically log in all users. This is useful if ZeroUI is protected by an authentication proxy. Note that when this value is changed, the localStorage of instances of logged-in panels should be cleared
ZU_LAST_SEEN_FETCH true Enables Last Seen feature
ZU_LAST_SEEN_SCHEDULE */5 * * * * Last Seen cron-like schedule
ZU_LOGIN_LIMIT false Enable rate limiter for /login endpoint
ZU_LOGIN_LIMIT_WINDOW 30 The duration of the IP ban in minutes
ZU_LOGIN_LIMIT_ATTEMPTS 50 Login attemps before ban

ZeroUI could be deployed as a regular nodejs web application, but it requires a ZeroTier controller that is installed with the zerotier-one package. For more info about the network controller, you could read here.

For Ansible Role, please refer to the zero-ui-ansible repository.

Controller Setup Tips (Outside Docker)

If you are using an existing controller on the host, you may need to allow connections from the Docker container. There are two ways to do this:

  1. Allow controller management from any IP address:
echo "{\"settings\": {\"portMappingEnabled\": true,\"softwareUpdate\": \"disable\",\"allowManagementFrom\": [\"\"]}}" > /var/lib/zerotier-one/local.conf

Warning: Don't forget to block connections to 9993/TCP from the WAN. Directly exposing the controller API to the WAN is not recommended; it should be proxified via the ZeroUI backend.

  1. Add network_mode: "host" to zero-ui in docker-compose.yml.

For more information, please refer to this discussion.


After installation, log in with the credentials declared with ZU_DEFAULT_USERNAME and ZU_DEFAULT_PASSWORD.

Currently, some main ZeroTier Central features are missing. Refer to the roadmap for more information.

For screenshots, please refer to the screenshots section.


To get the latest version, simply run

docker-compose pull && docker-compose up -d --no-build

in the folder where docker-compose.yml is located. Backups may not be necessary since most of your data is usually saved at the controller level, but it's still a good idea to consider them as a precautionary measure.


You should regularly back up the zerotier-one and data folders in your ZeroUI installation directory. You can do this manually before upgrading using the following commands:

tar cvf backup-ui.tar data/
tar cvf backup-zt.tar zerotier-one/


For a list of proposed features (and known issues), see the open issues.

GitHub issues open

When creating bug reports, please ensure they are:

  • Reproducible. Include steps to reproduce the problem.
  • Specific. Provide as much detail as possible, including version, environment, etc.
  • Unique. Avoid duplicating existing open issues.
  • Scoped to a Single Bug. Report one bug per issue.


Firstly, thank you for considering contributing! Contributions are what make the open-source community thrive. Any contributions you make will benefit everyone, and they are highly appreciated.

To contribute:

  1. Fork the project.
  2. Create your feature branch (git checkout -b feat/amazing_feature).
  3. Commit your changes (git commit -m 'feat: add amazing_feature').
  4. Push to the branch (git push origin feat/amazing_feature).
  5. Open a Pull Request

ZeroUI uses conventional commits, so please follow the guidelines. You can use yarn commit to open a Text-Based User Interface (TUI) that follows conventional commits guidelines.

Development Environment

To set up a development environment, follow these steps:

  1. Clone the repo
git clone
cd zero-ui
  1. Install packages
yarn install
  1. Start the development server
yarn dev
  1. Navigate to http://localhost:3000

You will also need to install the ZeroTier controller. On Linux, installing the zerotier-one package is sufficient, but other platforms may require some adjustments. First, you should obtain the controller token. On macOS, you can find it using the following command:

sudo cat "/Library/Application Support/ZeroTier/One/authtoken.secret"

Afterward, you can start the ZeroUI development environment:

ZU_CONTROLLER_TOKEN=TOKEN_FROM_authtoken.secret yarn dev

For other platforms, please refer to the ZeroTier manual.


If you need assistance or have questions, reach out through GitHub Discussions.


ZeroUI follows best practices for security, but complete security cannot be guaranteed. ZeroUI is provided "as is" without any warranty. Use at your own risk.

For enterprise support and a more reliable and scalable solution, please consider using ZeroTier Central.

For more information and to report security issues, please refer to our security documentation.

ZeroUI is not affiliated with, associated with, or endorsed by ZeroTier Central or ZeroTier, Inc.


License: GPL v3

See LICENSE for more information.