Project Used#

Read the Wiki

What Can You Gain from Running Hentai@Home?#

Just like on PT sites, by running the client according to the rules you can earn Hath, C Credits, and GP. These can be exchanged with each other and used to purchase browsing and download capacity.

Hentai@Home (H@H) Client Requirements#

Client Registration#

Go to the official page (login to your e-hentai account required):

🔗 https://e-hentai.org/hentaiathome.php

If you have never run a client before, you usually need to submit an application first. You must provide your maximum upload rate, server storage, and bandwidth details, and submit a speedtest-cli link.

Deployment#

Prepare a server with Docker installed (Asia-Pacific or China regions are recommended).

Create a directory:

1
mkdir hath-rust && cd hath-rust

1
version: '3.8'
2

3
services:
4
  hath:
5
    image: ghcr.io/james58899/hath-rust
6
    container_name: hath
7
    working_dir: /hath
8
    network_mode: host
9
    restart: unless-stopped
10
    stop_grace_period: 600s
11
    tty: true
12
    stdin_open: true
13
    volumes:
14
      - ./data:/hath/data
15
      - ./cache:/hath/cache
16
      - ./download:/hath/download
17
      - ./log:/hath/log
18
      - ./tmp:/hath/tmp
19
    command: >
20
      --port 7777
21
      --force-background-scan
22
      --enable-metrics

Startup#

Because this is the first startup and the client is not yet bound to your account, you need to perform some extra configuration. See the log output below.

1
docker compose up -d
2
docker exec -it hath hath-rust

The area highlighted in red is where you enter the ID and Key you obtained earlier.

After completing this, simply restart the container once and the project will continue to run in the background automatically.

TIP

Note: This restart will take a while because --stop-timeout 600 (600s) is configured. You can change it if you want a quicker restart.

Advanced Monitoring#

You can use Prometheus + Grafana to monitor the client, including upload/download speeds, cache usage, and more.

https://github.com/james58899/hath-rust/wiki/Monitoring

1
services:
2
  prometheus:
3
    image: prom/prometheus
4
    restart: unless-stopped
5
    ports:
6
      - "9090:9090"
7
    volumes:
8
      - type: bind
9
        source: ./prometheus.yml
10
        target: /etc/prometheus/prometheus.yml
11
      - promethous:/prometheus
12
    command:
13
      - "--config.file=/etc/prometheus/prometheus.yml"
14
      - "--storage.tsdb.path=/prometheus"
15
      - "--storage.tsdb.retention.size=30GB" # Modify to your available disk space
16
  grafana:
17
    image: grafana/grafana
18
    restart: unless-stopped
19
    ports:
20
      - "3000:3000"
21
    volumes:
22
      - grafana:/var/lib/grafana
23
    # Uncomment the following section if you want to change Grafana settings (for example, enable anonymous access).
24
    # environment:
25
    #   GF_AUTH_ANONYMOUS_ENABLED: "true"
26
    #   GF_AUTH_ANONYMOUS_HIDE_VERSION: "true"
27
volumes:
28
  # Modify this section if you want to change the storage location.
29
  promethous:
30
  grafana:

This YAML deploys Prometheus and Grafana containers, running on ports 9090 and 3000 respectively.

If you already have a monitoring stack, you don’t need to redeploy this. Just modify your existing prometheus.yml configuration.

prometheus.yml

1
global:
2
  scrape_interval: 5s # Increase this if Prometheus uses too much storage.
3
scrape_configs:
4
  - job_name: hath
5
    scheme: https
6
    tls_config:
7
      insecure_skip_verify: true # Because H@H uses dynamic hostnames, disabling certificate verification is needed.
8
    static_configs:
9
      - targets: ["202.6.204.44:7777"] # Modify to hath-rust address.
10
        labels:
11
          instance: "Hentai@Home" # The instance label is used for selection and display. It must be unique.

Dashboard example: H@H Status.json

Download and import the dashboard.

Other Notes#

1. Bandwidth management: If your home network bandwidth is limited, be sure to cap H@H upload speed to avoid affecting daily usage.
2. Long-term operation: A stable server with a dedicated IP is recommended to maintain high uptime.
3. Storage space: Use SSDs for the cache whenever possible to ensure speed and endurance.
4. Security: If you expose a public port, pay attention to firewall rules and port security.