one137

Theme: 

Homelab Services

Current list of services hosted

Hosted on Docker unless specified.

Programmable config

name, host, proxy, protocol
 
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, -
 
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, http://ct-syncthing:8384, -
syncthing-tn, dockerhost, https://truenas:20910, -
transmission, dockerhost, http://ct-wireguard-client:9091, -
uptime-kuma, dockerhost, http://ct-uptime-kuma:3001, -
wireguard-easy, dockerhost, http://wireguard-easy:51821, -
immich, dockerhost, http://immich_server:2283, WS
 
mailrise, dockerhost, stream://ct-mailrise:8025, TCP
mongodb, dockerhost, stream://ct-mongodb:27017, TCP
wireguard-easy, dockerhost, stream://wireguard-easy:51820, UDP
 
cloudflared, dockerhost, -, -
ddclient, dockerhost, -, -
diun, dockerhost, -, -
dnsmasq-wireguard, dockerhost, -, -
wireguard-client, dockerhost, -, -
 
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

Backlinks