Memos and Caddy can turn a Windows computer into a private family bulletin board for grocery lists and everyday notes. Caddy provides HTTPS for Android and iPhone, while HomeGrid VPN provides a remote path to the same home LAN IP address used on Wi-Fi. This example needs neither a custom DNS server nor router port forwarding.
1. One network diagram for home and remote access
The board stays on a computer you control. Family members can use Memos for notes or shopping reminders without relying on a public-facing web server.

At home, Wi-Fi reaches the computer's LAN IP directly. Remotely, HomeGrid VPN relays traffic through Cloud Hub and Home Grid to the same address. Cloud Hub is not the Internet Exit.
- On home Wi-Fi: phone → computer LAN IP on TCP 8443 → Caddy → Memos.
- Away from home: phone → HomeGrid VPN → Cloud Hub → home Grid → the same computer LAN IP.
- Outbound Only: both the remote device and home Grid initiate VPN connections to the Cloud Hub. No IPv4 port forward or IPv6 inbound rule is needed at home.
- Cloud Hub is not Internet Exit: it relays VPN traffic; it does not host this board or store its posts.
- HTTPS: Caddy receives TLS on container port 443 (host port 8443) and proxies to Memos on container port 5230.
The implementation was tested on Windows 11 with WSL2 and Docker Desktop. The macOS notes are untested. HomeGrid VPN must have a working LAN route and appropriate LAN ACL permissions.
2. Prepare Docker Desktop
Windows: install WSL2 and Ubuntu, then enable Ubuntu under Docker Desktop → Settings → Resources → WSL Integration. If needed, run in an elevated PowerShell:
wsl --install -d Ubuntu
macOS: install Docker Desktop for Mac. WSL2 is not used. Verify from a terminal:
docker --version
docker compose version
mkdir -p ~/family-bbs/conf ~/family-bbs/downloads
cd ~/family-bbs
On Windows, run the shell commands inside WSL2 Ubuntu.
3. Complete Docker Compose file
Save the following as ~/family-bbs/compose.yml:
services:
memos:
image: neosmemo/memos:stable
container_name: family-bbs-memos
restart: unless-stopped
ports:
- "127.0.0.1:5230:5230"
volumes:
- memos_data:/var/opt/memos
networks:
- bbs
caddy:
image: caddy:2
container_name: family-bbs-caddy
restart: unless-stopped
command: ["caddy", "run", "--config", "/etc/caddy/caddyfile", "--adapter", "caddyfile"]
ports:
- "8443:443"
- "8080:8080"
volumes:
- ./conf:/etc/caddy:ro
- ./downloads:/srv/downloads:ro
- caddy_data:/data
- caddy_config:/config
depends_on:
- memos
networks:
- bbs
networks:
bbs:
volumes:
memos_data:
caddy_data:
caddy_config:
Memos and Caddy share the Compose-managed bbs network; Caddy resolves memos:5230 through Docker DNS. The named volumes persist Memos data and Caddy’s internal CA keys.
Host port 5230 is bound to 127.0.0.1 only for initial setup and troubleshooting, so it is not exposed directly to the LAN. After validating the reverse proxy and remote route, remove Memos’ ports: mapping and use HTTPS only. Run docker compose up -d after removing that mapping, then retest access.
Start Memos and create its administrator account at http://localhost:5230/:
docker compose up -d memos
4. Enable HTTPS with Caddy’s internal CA
Determine your computer’s LAN IP with ipconfig on Windows or the macOS Network settings. 192.168.xxx.xxx below deliberately masks a real address and is not valid configuration. Replace every occurrence with your own LAN IP before starting Caddy. Consider a DHCP reservation to keep that address stable.
Save this as lowercase ~/family-bbs/conf/caddyfile:
{
default_sni 192.168.xxx.xxx
skip_install_trust
}
https://192.168.xxx.xxx {
tls internal
reverse_proxy memos:5230
}
:8080 {
root * /srv/downloads
@cert path /root.crt
header @cert Content-Type application/x-x509-ca-cert
header @cert Content-Disposition "attachment; filename=root.crt"
@profile path /family-bbs.mobileconfig
header @profile Content-Type application/x-apple-aspen-config
file_server
}
tls internal lets Caddy issue and renew certificates from its internal CA. default_sni handles clients that omit SNI when connecting to an IP address. The skip_install_trust directive prevents Caddy from trying to install its CA into the container trust store. Do not expose TCP 8080 to the public internet. The HTTP service on 8080 distributes the public CA certificate and iPhone profile during onboarding; HTTPS on 8443 serves the board.
cd ~/family-bbs
docker compose config -q
docker compose up -d
docker port family-bbs-caddy
Verify that both 8443 and 8080 are published. Open https://192.168.xxx.xxx:8443/ with your actual IP; a certificate warning is expected until you trust the CA.
5. Windows and macOS firewalls
A service that responds on the computer itself may still be unreachable from another device. In the Windows test, switching the network profile to Public stopped an iPhone reaching the board; returning to Private restored access.
Windows
Inspect the active profile:
Get-NetConnectionProfile | Select-Object InterfaceAlias, NetworkCategory
For a network you trust, an elevated PowerShell can set it to Private. Replace the interface name:
Set-NetConnectionProfile -InterfaceAlias "Ethernet 2" -NetworkCategory Private
Allow only local-subnet incoming traffic to HTTPS and the temporary certificate download service:
New-NetFirewallRule -DisplayName "Family BBS HTTPS" -Direction Inbound -Protocol TCP -LocalPort 8443 -Profile Private -RemoteAddress LocalSubnet -Action Allow
New-NetFirewallRule -DisplayName "Family BBS Certificate Download" -Direction Inbound -Protocol TCP -LocalPort 8080 -Profile Private -RemoteAddress LocalSubnet -Action Allow
Do not duplicate rules that already exist. Whether LocalSubnet also matches packets arriving through the Grid depends on the actual source address and routing/NAT. Check the effective source and narrowly adjust the rule if necessary.
macOS
Open System Settings → Network → Firewall → Options. Docker Desktop’s published traffic involves com.docker.backend; confirm that relevant Docker processes may accept inbound connections.
docker compose ps
lsof -nP -iTCP:8443 -sTCP:LISTEN
lsof -nP -iTCP:8080 -sTCP:LISTEN
The macOS application firewall is primarily application-based, so allowing a Docker backend process is not the same as restricting it to these two ports. Use Docker port mappings carefully and consider pf for more granular rules. This macOS workflow has not been tested end to end.
6. Distribute the CA to Android and iPhone
Export only Caddy’s public CA certificate , not its private key:
cd ~/family-bbs
docker cp family-bbs-caddy:/data/caddy/pki/authorities/local/root.crt ./root.crt
For iPhone, generate an unsigned certificate-only configuration profile with Python’s standard library:
cd ~/family-bbs
python3 - <<'PY'
import plistlib
import ssl
import uuid
from pathlib import Path
pem = Path("root.crt").read_text()
der = ssl.PEM_cert_to_DER_cert(pem)
profile = {
"PayloadType": "Configuration",
"PayloadVersion": 1,
"PayloadIdentifier": "com.family-bbs.ca",
"PayloadUUID": str(uuid.uuid4()).upper(),
"PayloadDisplayName": "Family BBS",
"PayloadDescription": "Family BBS root CA certificate",
"PayloadOrganization": "Family BBS",
"PayloadContent": [{
"PayloadType": "com.apple.security.root",
"PayloadVersion": 1,
"PayloadIdentifier": "com.family-bbs.ca.root",
"PayloadUUID": str(uuid.uuid4()).upper(),
"PayloadDisplayName": "Family BBS CA",
"PayloadCertificateFileName": "root.cer",
"PayloadContent": der,
}],
}
Path("family-bbs.mobileconfig").write_bytes(
plistlib.dumps(profile, fmt=plistlib.FMT_XML)
)
PY
Copy the two files to the HTTP download directory:
cp root.crt family-bbs.mobileconfig downloads/
docker exec family-bbs-caddy ls -l /srv/downloads/
| Device | Download URL (replace the masked LAN IP) |
|---|---|
| Android | http://192.168.xxx.xxx:8080/root.crt |
| iPhone | http://192.168.xxx.xxx:8080/family-bbs.mobileconfig |
Android: download root.crt, find Install CA certificate in device Settings, and select the file.
iPhone: download the .mobileconfig with Safari, install it under Settings → General → VPN & Device Management , then enable full trust under Settings → General → About → Certificate Trust Settings. Installing the profile alone does not enable TLS trust.
Both Android Chrome and iPhone Safari successfully loaded Memos over HTTPS without warnings in the Windows-based test.
Secure distribution matters
Port 8080 uses HTTP and does not protect the certificate from in-transit substitution. Do not trust the file merely because it was downloaded on the home LAN. Compare the CA fingerprint with one provided through a separate trusted channel:
openssl x509 -in root.crt -noout -fingerprint -sha256
Only install a CA on devices you administer. Protect the caddy_data volume containing the CA private key, and consider disabling HTTP port 8080 after onboarding.
7. Remote access with HomeGrid VPN
Register and run a home Grid using the Grid setup guide. Keep dashboard-generated activation tokens private. Register the remote device and explicitly allow the destination LAN subnet through LAN ACL; LAN ACL does not grant access to just one TCP port.
Connect HomeGrid VPN away from home, then open the same https://192.168.xxx.xxx:8443/ URL (using your actual LAN address). The server certificate remains valid for that LAN IP; no separate VPN-IP certificate is needed.
An earlier experiment used DNAT inside the Grid container to direct traffic sent to its VPN IP on TCP 5230 toward Memos. After deleting that DNAT rule, access through the computer’s LAN IP on TCP 8443 still worked. The published configuration therefore does not prescribe a custom DNAT rule. A functioning Grid-to-LAN route, return path, LAN ACL and host firewall permissions remain necessary.
Recreation caveat: the test environment previously had a manually added connection to Docker’s default bridge network. The exact remote path after recreating all containers with only the Compose-managed bbs network has not been retested. Verify both home Wi-Fi and cellular-plus-VPN after recreation. Overlapping LAN ranges at home and at the remote site can also affect routing.
8. Operate the family board responsibly
Use separate Memos accounts and suitable post visibility; access to the VPN is not a replacement for app authentication. Keep the computer awake when the board must be available, and back up the Memos database to separate storage with a consistent backup method.
| Check | Result |
|---|---|
| Windows Docker Desktop with Memos and Caddy | Tested |
| Android and iPhone trust of Caddy CA over home LAN HTTPS | Tested |
| Home LAN-IP access after removing the Grid’s old DNAT rule | Tested |
| Full container recreation with only the new Compose network | Not yet tested |
| End-to-end macOS build | Not yet tested |
The result is a small family service hosted on your own computer. HomeGrid VPN provides a path to the home LAN without exposing the Memos web server directly to the public internet.
Originally published at https://www.homegrid-vpn.com/blog/en/family-bbs-memos-vpn/
Top comments (0)