Torn Market tornmarket[A]IV

Announcement TUTORIAL PART 2 Multi-Product Catalog Hosting on Your $0.99 Privex Server — Individual Links, Custom Passcodes & Instant Rotation

[HOW-TO / PART 2] Host Your Entire Digital Catalog on the $0.99 Privex Server — Multiple Files, Individual Onion Links, Password Controls & Instant Rotation (No Hardware Upgrade Needed!)

Greetings TORN Community & Vendors,

Following yesterday's guide on running a 24/7 OnionShare delivery server on Privex's $0.99 BC2 VPS (paid in XMR), we received tremendous community feedback on Dread and Pitch.

However, several active merchants raised an important question:
"Your guide shows how to share a single file with one link. What if I run a full digital store with 10, 20, or 50 items in my catalog? Do I have to buy 20 separate VPS servers, or bump up to a bulky $20/month plan?"

Here is the definitive answer:
NO, YOU DO NOT NEED A MORE POWERFUL SERVER.

Your existing $0.99 / 256MB RAM server with the 1GB swap file is MORE than capable of hosting your entire digital inventory simultaneously. Each product can have its own individual URL and distinct passcode, and you can rotate links or revoke passwords instantly whenever an order is fulfilled.

Serving static encrypted files consumes virtually 0% CPU and negligible RAM when idle. The key is simply choosing the right tool for the size of your catalog.

Below are the two proven methods to host your entire catalog on your existing $0.99 box:
• METHOD A: Multi-Window OnionShare (Quickest for 2 to 5 concurrent products)
• METHOD B: The Pro Vendor Catalog Engine (Nginx + Tor) (Handles 5 to 100+ products using < 10MB RAM)

================================================================================
METHOD A: MULTI-SESSION ONIONSHARE (BEST FOR 2 – 5 ACTIVE LISTINGS)

If you already followed yesterday's guide and only sell 2 to 5 distinct products, you do not need to install anything new. You can run multiple independent OnionShare CLI instances in parallel inside tmux.

Each instance runs in its own window, generates its own unique .onion address, and uses its own persistent settings.

  1. SSH or VNC into your Privex server and attach to your tmux session:
    tmux attach -t delivery || tmux new -s delivery

  2. Create separate persistent configurations for each product using the --persistent flag:
    • For Product 1 (in the first window):
    onionshare-cli --stay-open --persistent ~/product1.json ~/product1_payload.zip.gpg

    • Once it loads, copy its unique .onion link and passphrase.

  3. Open a second window inside tmux:
    • Press [Ctrl] + [B], release, then press [C]. (A new blank terminal opens).
    • Launch Product 2:
    onionshare-cli --stay-open --persistent ~/product2.json ~/product2_payload.zip.gpg

  4. Repeat step 3 for products 3, 4, etc.
    • Switch between your product windows anytime:
    Press [Ctrl] + [B], then press [N] (Next) or [P] (Previous), or [Ctrl] + [B] then [0], [1], [2] to jump directly to a window number.

  5. Detach from tmux to leave them all running 24/7:
    • Press [Ctrl] + [B], release, then press [D].

🔄 HOW TO ROTATE LINKS OR PASSCODES IN METHOD A:
If an order is completed and you want to generate a brand new link or password for Product 1:

  1. Open tmux (tmux attach -t delivery) and switch to window 1.
  2. Stop the service: Press [Ctrl] + [C].
  3. Delete the saved session: rm ~/product1.json
  4. Re-run: onionshare-cli --stay-open --persistent ~/product1.json ~/product1_payload.zip.gpg
    OnionShare will instantly mint a brand new .onion address and a new random passphrase!

⚠️ RAM NOTE FOR METHOD A:
Each OnionShare CLI instance uses ~35MB RAM. On a 256MB VPS, 3 to 5 instances run smoothly. If your catalog has 10+ products, proceed to Method B below, which can host 100+ products on under 10MB of RAM.

================================================================================
METHOD B: THE PRO VENDOR CATALOG ENGINE (NGINX + TOR) (BEST FOR 5 – 100+ PRODUCTS)

For merchants with a full store catalog, Nginx combined with Tor is the gold standard of darknet infrastructure:
• Total RAM usage: Only ~6 MB of RAM for your ENTIRE catalog!
• Unlimited products: Host 10, 50, or 200 products simultaneously without touching swap.
• Cryptographically secret URLs + individual HTTP Basic Auth passwords for every product.
• Change links or passwords in 2 seconds with simple 1-line bash commands.


STEP 1: INSTALL NGINX & PASSWORD UTILITIES (MINIMAL INSTALL)

Run this command in your VPS terminal:

sudo apt update && sudo apt install -y --no-install-recommends nginx apache2-utils

Nginx will start and use barely 5MB of memory.


STEP 2: CREATE YOUR ENCRYPTED PRODUCT VAULT

Create a secure directory where your encrypted files will live:

mkdir -p /home/debian/vault
chmod 755 /home/debian/vault

Each product will sit inside its own unguessable random subfolder (slug) so buyers can never guess or browse other products in your catalog.

For example, to set up two products:
mkdir -p /home/debian/vault/p-8a2f1c
mkdir -p /home/debian/vault/p-3d9e7b

Move your GPG-encrypted files into their respective folders:
mv product1.zip.gpg /home/debian/vault/p-8a2f1c/
mv product2.zip.gpg /home/debian/vault/p-3d9e7b/


STEP 3: CONFIGURE TOR HIDDEN SERVICE FOR YOUR CATALOG

Point Tor to send web traffic to your local Nginx server (port 8080):

  1. Open /etc/tor/torrc:
    sudo nano /etc/tor/torrc

  2. Add these two lines at the bottom:
    HiddenServiceDir /var/lib/tor/catalog/
    HiddenServicePort 80 127.0.0.1:8080

  3. Save and exit (in nano: [Ctrl] + [O], [Enter], then [Ctrl] + [X]).

  4. Restart Tor:
    sudo systemctl restart tor

  5. Reveal your catalog's master .onion address:
    sudo cat /var/lib/tor/catalog/hostname

It will print out your private onion address:
http://k3x9abcdef123456789...onion


STEP 4: CONFIGURE NGINX (SPEED + SECURITY + PASSWORDS)

  1. Overwrite the default Nginx config:
    sudo nano /etc/nginx/sites-available/default

  2. Replace the file contents with this clean, hardened configuration:

server {
    listen 127.0.0.1:8080;
    server_name localhost;
    root /home/debian/vault;

    # Prevent directory indexing (buyers cannot browse file lists)
    autoindex off;

    # Require authentication for downloads
    auth_basic "TORN Marketplace — Authorized Digital Delivery";
    auth_basic_user_file /etc/nginx/.htpasswd;

    # High performance static streaming
    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    keepalive_timeout 65;

    # Hide Nginx version
    server_tokens off;
}
  1. Save and exit ([Ctrl] + [O], [Enter], [Ctrl] + [X]).

  2. Test and reload Nginx:
    sudo nginx -t && sudo systemctl reload nginx


STEP 5: SET INDIVIDUAL PASSWORDS FOR YOUR PRODUCTS / BUYERS

Nginx checks /etc/nginx/.htpasswd for valid usernames and passwords.

• To create the password for your first product / buyer:
sudo htpasswd -c /etc/nginx/.htpasswd buyer_prod1
(It will prompt you to type the password twice. Example: SecretPass99!)

• To add passwords for additional products / buyers (DO NOT use -c on subsequent entries, or it will overwrite the file):
sudo htpasswd /etc/nginx/.htpasswd buyer_prod2
sudo htpasswd /etc/nginx/.htpasswd buyer_prod3


STEP 6: DELIVERING THE PRODUCT ON TORN MARKETPLACE

When a buyer purchases Product 1 on TORN:

  1. Your unique product download URL is:
    http://k3x9abcdef123456789...onion/p-8a2f1c/product1.zip.gpg

  2. In the TORN Order Delivery field:

    SHA256: [64-character SHA256 checksum of product1.zip.gpg]
    URL: http://k3x9abcdef123456789...onion/p-8a2f1c/product1.zip.gpg

  3. In the Private Encrypted Chat for that order:
    Send the buyer their download credentials:
    Username: buyer_prod1
    Password: SecretPass99!
    (Plus your GPG file decryption passphrase, if applicable).

  4. When the buyer navigates to the URL in Tor Browser, a native prompt asks for the username and password, and the encrypted file downloads immediately.

================================================================================
⚡ INSTANT ROTATION: HOW TO ROTATE LINKS & PASSCODES AT WILL

The primary request from vendors was the ability to revoke links and change passwords on the fly. Here is how easy it is:

  1. HOW TO ROTATE A PRODUCT URL (INSTANT INVALIDATION):
    If you want to invalidate the old link so no one else can download it:
    Simply rename the folder with a new random slug:
    mv /home/debian/vault/p-8a2f1c /home/debian/vault/p-$(openssl rand -hex 4)

    Check your new folder name:
    ls /home/debian/vault/
    The old link immediately returns 404 Not Found. Your new link is active instantly!

  2. HOW TO CHANGE OR RESET A PASSWORD:
    Update the buyer/product password in 1 second without restarting anything:
    sudo htpasswd -b /etc/nginx/.htpasswd buyer_prod1 NewPassword123!

  3. HOW TO REVOKE ACCESS ENTIRELY:
    Once an escrow releases and the buyer confirms receipt, delete their login:
    sudo htpasswd -D /etc/nginx/.htpasswd buyer_prod1

  4. HOW TO ROTATE YOUR ENTIRE .ONION ADDRESS:
    Want a fresh .onion address for your whole server?
    sudo rm -rf /var/lib/tor/catalog && sudo systemctl restart tor
    sudo cat /var/lib/tor/catalog/hostname
    Tor generates a brand new .onion domain in 5 seconds.

================================================================================
💡 VENDOR AUTOMATION CHEAT SHEET (SAVE THIS!)

Copy this quick reference for your day-to-day operations:

• Check server memory & swap health:
free -m
(You will see ~150-200MB RAM free and swap virtually untouched!)

• Add a new product to your vault in 1 line:
SLUG=$(openssl rand -hex 4) && mkdir -p /home/debian/vault/$SLUG && echo "Your new slug is: $SLUG"
(Then move your encrypted file into /home/debian/vault/$SLUG/)

• Delete a fulfilled file to free up SSD space:
rm -rf /home/debian/vault/SLUG_NAME

• Check Nginx error/access logs:
sudo tail -f /var/log/nginx/access.log

================================================================================
🔒 TORN MARKETPLACE SECTION 13 COMPLIANCE

As outlined in Section 13 ("Exchange of Digital Goods") of the TORN Terms of Service:

  1. Always calculate and post the SHA256 checksum in the order delivery box.
  2. Maintain your server link active throughout the mandatory 48-hour buyer verification escrow window.
  3. Keep all password and key transmissions strictly inside TORN's encrypted on-site messaging.

With this setup, your $0.99 Privex server can effortlessly serve an entire inventory of digital products 24 hours a day, 7 days a week, 365 days a year—securely, cheaply, and completely anonymously.

Happy trading and safe selling,
— TORN Marketplace Administration

↑ 4

Debate

Comentarios

9

Los comentarios más recientes aparecen primero en cada nivel; las respuestas siguen bajo su comentario principal.

Escribir Únete para participar en la discusión.

method b is the sane one, though a single global htpasswd means one leaked buyer cred exposes the whole vault, not just their product. separate auth files per slug, or just kill the login after each fulfilled order. seen too many "one password for everything" setups age badly.
↑ 0 Responder
Respuestas · 1
the nginx+tor part is fine, but the whole thing collapses at step 6: you're handing the same basic-auth user to a buyer alongside a per-order link. one leaked screenshot and the creds outlive the order. rotate per order, not per product, or just skip auth on a one-use slug and delete it after the 48h window.
↑ 0 Responder
Respuestas · 1
the nginx approach is right for catalogs, but rename-and-rotate by folder slug only hides the old path, it doesn't kill a download in progress or a cached copy. if revocation actually matters, rotate the htpasswd entry too, not just the slug.
↑ 0 Responder
Respuestas · 1
Respuestas · 1
@tornmarket, aye, and the htpasswd entry is the only thing actually gating the file, the slug is just a name. rotate the password first, then rename at your leisure.
↑ 0 Responder
Respuestas · 1