Homelab Services

Current list of services hosted

Hosted on Docker unless specified.

• Cloudflared
• ddclient
• Diun
• DNSMasq (for Wireguard server)
• fail2ban (on Bare)
• Immich
• Jellyfin
• Mailrise
• MongoDB
• Nginx Proxy Manager (NPM) including web server
• Pi-Hole (x2, once on Bare once on dockerhost)
• Portainer
• Restic
• Syncthing (x2, once on TrueNAS once on dockerhost)
• Transmission
• Uptime-Kuma
• Watchtower
• Wireguard (server and client)

Programmable config

name, host, proxy, protocol
 
# Systems
router, 192.168.137.1, http://router:80, -
pihole1, 192.168.137.10, http://pihole1:80, -
proxmox, 192.168.137.11, https://proxmox:8006, WS
truenas, 192.168.137.12, http://truenas:80, WS
dockerhost, 192.168.137.13, -
 
# HTTP services on dockerhost
immich, dockerhost, http://immich_server:2283, WS
jellyfin, dockerhost, http://ct-jellyfin:8096, WS
npm, dockerhost, http://ct-npm:81, -
pihole2, dockerhost, http://ct-pihole:80, -
portainer, dockerhost, https://ct-portainer:9443, -
syncthing-dh/dockerhost-st, dockerhost, http://ct-syncthing:8384, -
transmission, dockerhost, http://ct-wireguard-client:9091, -
uptime-kuma, dockerhost, http://ct-uptime-kuma:3001, -
wg-easy/wireguard-easy, dockerhost, http://ct-wireguard-easy:51821, -
# HTTP services on truenas
restic, truenas, http://truenas:30248, -
syncthing-tn, truenas, https://truenas:20910, -
 
# Stream services
8025, dockerhost, stream://ct-mailrise:8025, TCP
22000, dockerhost, stream://ct-syncthing:22000, TCP UDP
27017, dockerhost, stream://ct-mongodb:27017, TCP
WG_PORT, dockerhost, stream://ct-wireguard-easy:WG_PORT, UDP
 
# Services without inbound access through NPM
cloudflared, dockerhost, -, -
ddclient, dockerhost, -, -
diun, dockerhost, -, -
dnsmasq-wireguard, dockerhost, -, -
wireguard-client, dockerhost, -, -
 
# Web
one137, dockerhost, http://STATIC_FILES:1, -

See Services and network layout (not public).

Recap / Steps to add a new Docker service (MongoDB example)

1. Deploy service through a new Portainer stack, and update NPM’s stack
   1. Don’t expose any ports
   2. Name the stack and container as per convention, e.g. 50-mongodb and ct-mongodb
   3. Configure volumes and networks as needed
   4. Start the stack
   5. In the NPM stack:
      1. Expose the new container’s non-web ports, if any
      2. Add the new stack’s network to NPM’s networks
      3. Restart NPM
2. Add proxied address in NPM
   1. For http(s) services:
      • Proxy host
      • container’s name as the destination (ct-transmission:9091)
      • a .one137.dev cert
      • the LAN+Wireguard access
   2. For others:
      • Stream host
      • container’s name as the destination (ct-mongo:27017)
3. Enjoy (e.g. mongosh mongodb://*:*@mongodb.one137.dev:27017)
4. Add service uptime monitoring to Uptime-Kuma