HelloZeroNet / HelloZeroNet/ZeroNet

TIP: How to host ZeroNet in a private IP container

Ouverte
#103 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
JavaScript
Étoiles
18.8k
Forks
2.3k
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

Not an issue, but I wasn't sure where to post this tip:

And, yes, I am aware that you may then want to protect your ZeroNet install(!)

Here is a typical configuration:
- Host machine runs haproxy
- ZeroNet in a Docker or OpenVZ container

1-Make the main UI available to the world:

In the container: `python zeronet.py --ui_ip 0.0.0.0`

On the host, you need to configure this container's IP in haproxy -- for instance, edit haproxy.conf:

```
frontend http_in
acl host_zeronet hdr(host) -i zeronet.example.com
use_backend be_zeronet if host_zeronet

backend be_zeronet
balance lastconn
option httpclose
server pub_zeronet :43110 cookie pub_zeronet check
```

Restart haproxy.

2-Make the file server available:

I would recommend using NAT to avoid any surprise. In /etc/../iptables:

nat:

```
# we will nat incoming packets on port 15441
-A PREROUTING -i eth0 -p tcp -m tcp --dport 15441 -j DNAT --to-destination :15441
-A PREROUTING -i eth0 -p udp -m udp --dport 15441 -j DNAT --to-destination :15441
```

filter:

```
# host forwards incoming container packets
-A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s /24 -i -j ACCEPT
# host accepts incoming container packets to its own services
-A INPUT -s /24 -i -j ACCEPT
```

Cleanup your iptables configuration then `iptable-restore < etc/../iptable`

And you're good to go! (in theory)

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.