From 9a960a74be4a7e2ee5394490107056a443d98024 Mon Sep 17 00:00:00 2001 From: dcstephenson Date: Fri, 24 Jul 2026 11:47:23 -0500 Subject: [PATCH] Update docs for migration to 192.168.16.137, fix SSH command, note switch status - Host moved from decommissioned 192.168.16.130 VM to 192.168.16.137 - Step 1 command was missing the "ip" prefix (ip http secure-server) - Only :4500/:4512 confirmed working as of 2026-07-24; other 18 switches are online but haven't had HTTPS enabled yet Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01Bp1HutYUh9fmTFgwB4qBLz --- README.md | 34 ++++++++++++++++++++-------------- docker-compose.yml | 7 ++++++- 2 files changed, 26 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index b46d1f1..962bdbf 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ running firmware 1.01.02.0005 (TLS 1.0 only) via a stunnel proxy. ``` Browser (TLS 1.2/1.3) ↓ -stunnel container on 192.168.16.130 +stunnel container on 192.168.16.137 ↓ Switch (TLS 1.0) on 10.214.0.x ``` @@ -22,38 +22,44 @@ SSH into each switch and run: ``` enable configure -http secure-server +ip http secure-server save configuration ``` -> wwtp-gate-sw01 (10.214.0.112) is already done and confirmed working. +> wwtp-gate-sw01 (10.214.0.112) and wwtp-offc-sw01 (10.214.0.100) are confirmed +> working. As of 2026-07-24, the other 18 switches all respond to ping but +> refuse port 443 outright — meaning `http secure-server` has not been enabled +> on them yet. Run Step 1 on each before expecting its port to work. --- -### Step 2 — Build the Docker image on the Portainer host +### Step 2 — Build the Docker image on the target host -Copy the three files (Dockerfile, stunnel.conf, docker-compose.yml) -to the same directory on your Portainer host, then build: +Clone this repo to the target host (currently `/opt/stunnel` on +192.168.16.137), then build: ```bash -cd /path/to/stunnel-wwtp +cd /opt/stunnel docker build -t stunnel-wwtp:latest . ``` --- -### Step 3 — Deploy via Portainer +### Step 3 — Deploy -1. Open Portainer → **Stacks** → **Add Stack** -2. Name it: `stunnel-wwtp` -3. Paste the contents of `docker-compose.yml` into the editor -4. Click **Deploy the stack** +```bash +cd /opt/stunnel +docker compose up -d +``` + +(Can also be deployed via Portainer → Stacks → Add Stack, pasting +`docker-compose.yml`, if a Portainer instance is available.) --- ### Step 4 — Access a switch in your browser -Use: `https://192.168.16.130:` +Use: `https://192.168.16.137:` | Port | Switch | Location | |-------|-----------------|-----------------| @@ -98,7 +104,7 @@ Use: `https://192.168.16.130:` **Test a specific switch from the host CLI:** ```bash -curl -k https://192.168.16.130:4512 # should return HTML from gate switch +curl -k https://192.168.16.137:4512 # should return HTML from gate switch ``` --- diff --git a/docker-compose.yml b/docker-compose.yml index c3c18c0..9434ba7 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -25,8 +25,13 @@ # :4518 → 10.214.0.118 wwtp-bst-sw01 Beast # :4519 → 10.214.0.119 wwtp-ecb3-sw02 Elec Ctrl Bldg 3 # -# Browser usage: https://192.168.16.130: +# Browser usage: https://192.168.16.137: # Accept the self-signed cert warning in your browser +# +# Only :4500 (wwtp-offc-sw01) and :4512 (wwtp-gate-sw01) are confirmed +# working as of 2026-07-24. The other 18 switches are online (ping OK) +# but refuse port 443 outright — they need `http secure-server` enabled +# via SSH first (see README.md Step 1). # ============================================================ version: "3.8"