docs: Uptime Kuma cleanup - fix stale IPs and remove duplicates
This commit is contained in:
@@ -5,6 +5,14 @@
|
|||||||
---
|
---
|
||||||
## 2026-05-05
|
## 2026-05-05
|
||||||
|
|
||||||
|
### Uptime Kuma Cleanup
|
||||||
|
- **[MONITORING]** Updated 3 monitors with stale 192.168.31.x IPs to current 192.168.10.x addresses
|
||||||
|
- MikroTik Router: 192.168.31.1 → 192.168.10.1
|
||||||
|
- Unraid Server: 192.168.31.2 → 192.168.10.20
|
||||||
|
- Switch Ping: 192.168.31.9 → 192.168.10.3 (CSS326)
|
||||||
|
- **[MONITORING]** Deleted 7 duplicate monitors (MikroTik AdGuard Home ×3, MikroTik Tailscale ×2, MikroTik DNS ×2)
|
||||||
|
- **[MONITORING]** Final state: 27 clean monitors, no legacy 192.168.31.x references remaining
|
||||||
|
|
||||||
### Kasm Workspaces Fix
|
### Kasm Workspaces Fix
|
||||||
- **[KASM]** Fixed session connection failure when accessing via Traefik reverse proxy
|
- **[KASM]** Fixed session connection failure when accessing via Traefik reverse proxy
|
||||||
- **[KASM]** Changed zone `proxy_port` from 6333 to 443 in kasm_db — browser WebSocket now routes through Traefik instead of trying unreachable port 6333
|
- **[KASM]** Changed zone `proxy_port` from 6333 to 443 in kasm_db — browser WebSocket now routes through Traefik instead of trying unreachable port 6333
|
||||||
|
|||||||
Reference in New Issue
Block a user