GoDoxy-Frontend

GoDoxy is a lightweight, high-performance reverse proxy with a Web UI that routes incoming traffic to self-hosted services behind a single wildcard domain.

  • Infrastructure
  • Network Services
  • Other
  • Productivity
  • Tools & Utilities
GoDoxy is a lightweight, high-performance reverse proxy with a Web UI that routes incoming traffic to self-hosted services behind a single wildcard domain.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

76/100 Good

Maintained
100last commit 15 days ago
Popular
724,189 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 22 days ago

GitHub stars
4,189
Open issues
11
Last commit
2026-11-06
Latest release
v0.33.0
Activity
steady

Checked 7 days ago - source: GitHub (yusing/go-proxy)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Run the setup script first Run the GoDoxy setup script before starting the frontend so it creates the needed configuration and support files. If you skip it, the app may not have the settings it needs and can fail to start. source
  • Set the Docker host in config In the GoDoxy config, set the docker provider to $DOCKER_HOST (the address or socket where your Docker daemon is listening) before starting. This tells the app where Docker is, so it can find and start containers; without it, container actions can fail. source
  • Start the container with its ID Use the Docker start API (the app's start command) and send the container's real ID. If the ID is missing or left as the example placeholder, the app can't start the right container. source
  • Configure wildcard DNS Point a wildcard DNS A/AAAA record (e.g. *.domain.com) at the machine running GoDoxy before first use, since it routes by hostname. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does GoDoxy need to run in host network mode?

Yes. It is designed to run in host network mode, and that setting should not be changed.

How do I route self-hosted apps through GoDoxy?

Point wildcard DNS records for your domain at the machine running GoDoxy. Routes can be configured with Docker labels or route files, and the proxy.aliases label is used as the subdomain unless unset.

What should I run before starting the GoDoxy frontend?

Run the GoDoxy setup script before starting the frontend. If you skip it, it may lack the configuration and support files it needs and can fail to start.

How do I tell GoDoxy where my Docker daemon is?

Set the docker provider in the GoDoxy config to $DOCKER_HOST, the address or socket where the Docker daemon is listening. Without this, container actions can fail.

Answers sourced from docs.godoxy.dev, docs.godoxy.dev, github.com

Community

Collected 49 days ago - public community threads