๐ง
MyZubster Is Expanding Toward the Tor Network โ Building an Onion Service with Our Open-Source Contributors
Docker โข Tor โข Node.js โข React โข Nginx โข Privacy โข Open Source
We're taking an exciting new step in the development of MyZubster: working toward making our ecosystem accessible through the Tor network using a .onion address.
Alongside our traditional website, we want to provide an alternative access path designed with privacy, infrastructure isolation, and reliability in mind.
And we're building it with the help of independent open-source contributors.
๐จ๐ป Recognizing Our Contributors
A special thank you to Wasim (@wasim-builds) and Nicola (N4K48) for their contributions to MyZubster's evolving infrastructure.
Wasim is developing and refining changes involving our Docker setup, backend services, frontend infrastructure, and Tor integration.
๐ Wasim's contribution โ PR #1582:
https://github.com/MyZubster-Ecosystem/myzubster/pull/1582
๐ Wasim's GitHub:
https://github.com/wasim-builds
Nicola's earlier N4K48 contribution forms an important foundation for the work now being reviewed and tested.
๐ Nicola / N4K48 โ Original PR #1457:
https://github.com/MyZubster-Ecosystem/myzubster/pull/1457
This is what makes open source valuable: contributors bringing independent ideas, improving each other's work, and helping transform experiments into reliable infrastructure.
๐ What Are We Building?
We're developing a Docker-based Tor Onion Service that would allow users to access the MyZubster frontend through Tor Browser.
The intended architecture is:
User with Tor Browser
|
Tor Network
|
.onion Address
|
Tor Onion Service
|
Internal Docker Network
|
Nginx + React
|
Node.js Backend
|
MongoDB
The idea is to provide an alternative entry point without directly exposing backend or database services.
Our goal is not simply to generate an Onion address. We want the entire access path to be reliable, maintainable, and carefully reviewed.
โ
What We've Already Tested
We've been validating PR #1582 on an isolated VPS using dedicated Docker containers and internal networking.
Here are some of the results:
Backend and APIs
โ
Node.js backend successfully built and started after a local middleware import correction.
โ
MongoDB connectivity verified.
โ
Health, Ledger, and Economics API tests passed.
โ
Seven targeted authentication and authorization tests passed.
Frontend and Nginx
โ
React production build completed successfully.
โ
Frontend Docker image built.
โ
Nginx configuration validated.
โ
Homepage returned HTTP 200.
โ
React SPA fallback worked.
โ
Nginx successfully proxied Ledger API requests to the backend.
Tor and Onion Infrastructure
โ
Tor Docker image built successfully.
โ
Tor 0.4.9.11 installed and verified.
โ
Dedicated non-root Tor user and filesystem permissions tested.
โ
Frontend reachable from the isolated Onion test container with HTTP 200.
โ
A candidate fix for Tor's Docker hostname configuration issue passed static validation.
These are actual results from our isolated test environment, not claims of a completed public launch.
๐ An Interesting Challenge We Discovered
The original Onion configuration used the Docker service hostname directly:
HiddenServicePort 80 frontend:80
During testing, Tor rejected the configuration:
Unparseable address in hidden service port configuration.
We reproduced the issue and tested a candidate solution using Docker DNS resolution.
The frontend hostname was resolved to its internal container IP before generating the Tor configuration.
The modified configuration passed validation.
But there's an important challenge:
Docker container IP addresses can change when services are recreated.
If Tor uses an address resolved only once at startup, it may later point to the wrong destination.
This is one of the areas where feedback from experienced infrastructure developers would be especially valuable.
๐ ๏ธ What We Still Need to Complete
Before a public Onion deployment, several tasks remain:
- Integrate the tested backend middleware import fix into PR #1582.
- Make Tor destination resolution resilient to Docker container restarts and IP changes.
- Improve service readiness and Tor health checks.
- Remove frontend build instructions that can conceal compilation failures.
- Test real connectivity over the Tor network in a controlled environment.
- Verify browser behavior, privacy boundaries, and end-to-end integration.
- Complete security review before any production deployment.
Our Onion Service is not publicly launched or fully validated yet.
We're documenting what works, what doesn't, and what we're learning along the way.
๐ค Calling Developers Who Want to Contribute
We're particularly interested in connecting with developers experienced in:
Tor Onion Services, Docker Compose, Linux infrastructure, Node.js, React, Nginx, service discovery, and application security.
Here's a question for the community:
How would you design a reliable Tor Onion Service behind Docker when the frontend container's IP address may change?
Would you use a local reverse proxy, a service-discovery mechanism, automatic configuration reloads, or a different architecture?
We'd love to hear about approaches you've implemented or tested.
๐ Join the MyZubster Open-Source Journey
We're building an ecosystem where contributors can experiment, review each other's ideas, and improve real infrastructure together.
Explore the project:
๐ Website: https://www.myzubster.com/
๐ป GitHub: https://github.com/MyZubster-Ecosystem/myzubster
๐ง Active contribution: https://github.com/MyZubster-Ecosystem/myzubster/pull/1582
๐งฉ Original N4K48 contribution: https://github.com/MyZubster-Ecosystem/myzubster/pull/1457
Thank you again to Wasim and Nicola for their work and willingness to contribute to the ecosystem.
We're not announcing a finished Onion deployment.
We're inviting the developer community to help us build one properly.
Because open source grows through collaboration, evidence, and shared progress.
MyZubster โ Building together, testing together, growing together.
OpenSource #Tor #Docker #Privacy #NodeJS #React #Linux #WebDevelopment