| 2026-10-25 |
Minecraft stream mapping corrected to .160 and verified live; stale .218 mapping removed
...
Live verification 2026-10-25: the stale "minecraft → tcp://192.168.1.218" mapping in this doc was wrong; the live nginx stream config points at 192.168.1.160 and works end-to-end.
|
| 2026-10-21 |
internal-proxy-vps: 2026-10-21 disk_high 90.3% cleanup executed (journal cap 200M, apt cache, old kernel, old nginx .gz), df 93%→76%, services healthy
...
Reaction session rei on GHard event 1ed8c8fd (disk_high / 90.3%, server id 33 internal-proxy). SSH triage: /var 2.3G (journal 768M, nginx logs 505M), apt cache 179M, old kernel 4.15.0-213. Cleanup: journal vacuum 768M→104M, apt-get clean, purge linux-image-4.15.0-213-generic + /lib/modules, 20 old nginx .gz removed. Persistent journald cap /etc/systemd/journald.conf.d/rei-disk-cap.conf (SystemMaxUse=200M, MaxRetentionSec=14day). Result: df 93%→76% (1.7G free), inodes 21%. Services verified: nginx active HTTPS 200, navi.service health 200, navi-postgres healthy, openvpn@client masked (pre-existing).
|
| 2026-10-19 |
external-vps: entrypoint 51.83.131.93 (OVH) verified; s-host 194.61.53.43 unreachable; 19 Oct path degradation documented
...
external-vps.md: entrypoint 51.83.131.93 (OVH) verified via DNS ×3 and TCP probes; s-host 194.61.53.43 unreachable (16/16 FAIL); 2026-10-19 path degradation section added (SYN drops home LAN → OVH, 12/16 FAIL, clean ICMP, clean internal path 16/16). Source: rei triage of nextcloud flapping storm 19 Oct.
|
| 2026-10-17 |
internal-proxy-vps: LAN .183 закреплён netplan-статикой в госте (01-netcfg.yaml), DHCP-резервация pfSense не нужна по дизайну владельца
...
Владелец подтвердил дизайн: pfSense не выдаёт адреса из серверного диапазона, статика на стороне серверов. Проверено по SSH: netplan 01-netcfg.yaml на .183 уже статический (настроен утром), cloud-init в VM отсутствует; DHCP-резервация Kea не нужна.
|
LAN address .226 → .183 after 2026-10-16/17 blackout; added blackout recovery section; nginx upstreams for synapse/tgclientmcp restored to .172/.171
...
После блэкаута 2026-10-16/17 VM ovpn_reserv получила DHCP-адрес 192.168.1.183 вместо .226 (проверено SSH: enp1s0=192.168.1.183/24, enp7s0=192.168.105.181/24); зависимые конфиги обновлены, gnsynapse/tgclient_mcp возвращены на .172/.171 по просьбе владельца
|
| 2026-10-16 |
internal-proxy: добавлен второй эпизод disk_high 2026-10-16 (17:49→18:31 UTC, +1.07 GB temp nginx, самоосвобождение) — 3-й эпизод класса proxy_buffering; last_reviewed 2026-10-16
...
Реакция на GHard event f18217dc (disk_recovered #852, 18:31 UTC): второй эпизод disk_high за вечер на internal-proxy, идентичная сигнатура буферизации nginx (jellyfin vhost без proxy_buffering off) — класс инцидента подтверждён, документирую для истории триажа.
|
internal-proxy-vps: резолюция disk_high 2026-10-16 (fd закрыт, 77%, SSH-верификация)
...
Резолюция disk_recovered #850 (17:30 UTC): fd закрыт при завершении стрима jellyfin-androidtv, −1.07 GB → 77.0%. SSH-верификация 17:35 UTC: df 5.2G/7.1G (78%), deleted-but-open fd у nginx отсутствует, /var/lib/nginx/proxy 4.0M. Прогноз триажа 16:28 UTC выполнен. Открытые пункты (очистка ~2.1–2.3 GB, proxy_buffering off в jellyfin/cloud/transmission) — ждут решения владельца.
|
Добавлен раздел 2026-10-16: disk_high 91.8% — повтор прецедента 10-11, корень = jellyfin vhost без proxy_buffering off
...
Инцидент disk_high 2026-10-16 на internal-proxy: повтор прецедента 2026-10-11 (nginx deleted-but-open temp 1 GiB), корень установлен — vhost jellyfin.gnexus.space без proxy_buffering off (6 из 17 сайтов без директивы). Источник: триаж rei по SSH 16:27–16:28 UTC, read-only.
|
| 2026-10-12 |
Add doc for navi host (192.168.1.168): local ollama embeddings service, two-unit layout, crash-loop fix 2026-10-12
...
Fix applied on 2026-10-12: stock ollama.service crash-looped since boot (port conflict with ollama-embed.service); stopped and disabled. Documented so hive instances referencing 192.168.1.168:11434 know the unit layout.
|
| 2026-10-11 |
internal-proxy-vps: триаж ложных container_removed/added 2026-10-11 (артефакт пере-детекта агента при пике нагрузки)
...
Триаж Synapse-события c341573c (container_added navi-postgres, server 33): docker inspect StartedAt=2026-10-08T11:25:01Z, RestartCount=0 — контейнер не пересоздавался; hard-monitor PID 521 без рестарта; CPU-пик агента 12→60% в 17:59:08–18:00:38 + разрыв docker-стрима 17:59:55 → пере-детект. Рост диска / 72→87% — deleted-but-open 1GiB nginx proxy temp (Modify 18:00:45). Сервисы здоровы.
|
| 2026-10-08 |
internal-proxy: фикс опечаток предыдущего коммита (CN bugtrail, дубль SSH access)
...
Правка собственного коммита e1d0b4b: убран задвоенный SSH access-буллет, восстановлен CN=bugtrail.gnexus.space в строке сертификата bugtrail.
|
internal-proxy: ребут 2026-10-08 (чистый ACPI shutdown 11:24:20 UTC), recreate navi-postgres — следствие, сервисы восстановлены; побочные наблюдения и открытый вопрос по инициатору (gntodo 455)
...
Расследование Synapse-события container_removed navi-postgres (server_id 33): установлена причина (ребут VM, чистый ACPI shutdown), проверено восстановление сервисов; факты durable.
|
internal-proxy-vps: add GHard panel id 33 and Navi Postgres Container section (navi-postgres, pgvector/pgvector:pg16, compose path, recreate 2026-10-08)
...
SSH-верификация 2026-10-08: панельный id 33 = internal-proxy (VM ovpn_reserv, 192.168.1.226 / 192.168.105.181). Контейнер navi-postgres (pgvector/pgvector:pg16) жив и healthy; compose /home/ubuntu/navi-1/deploy/docker-compose.yml (проект deploy, сервис postgres); recreate 2026-10-08T11:25Z, образ pgvector использовался и до него (container created 2026-09-09).
|
| 2026-10-05 |
tgclientmcp.gnexus.space: проксирование + LE-сертификат на .226
...
nginx site tgclientmcp.gnexus.space created on internal-proxy-vps (.226): :80 + :443, LE cert until 2027-01-03, upstream http://192.168.1.171:8710, SSE settings on /mcp-protocol/. Confirmed hpanel (.176:8000) and synapse (.172:8013) mappings. tgclientmcp.md updated: public URL, third deploy fix (FastMCP DNS-rebinding protection disabled).
|
| 2026-09-21 |
Добавлен сайт tasks.gnexus.space (upstream 192.168.1.179:8135) и отдельный certbot-сертификат (до 2026-12-20)
...
Деплой gntodo: новый сайт tasks.gnexus.space (upstream 192.168.1.179:8135) и отдельный LE-сертификат на internal-proxy-vps. Обнаружено при деплое GNexus Tasks 2026-09-21.
|
| 2026-09-20 |
Add GNtranscribe telegram bot (doc + inventory + host doc update)
...
GNtranscribe (@gntranscribe_bot) deployed 2026-09-20 on VM tg_bots (192.168.1.254) by navi rei: /home/ubuntu/bots/GNtranscribe, systemd gntranscribe.service (enabled, Restart=always), python-telegram-bot 21.10. Forwards voice/audio/video to whisper-server on bserv-host (192.168.1.130:8008), asyncio queue max 20, single worker, optional chat_id whitelist via ALLOWED_CHAT_IDS, commands /start /help /id /status. Verified: getMe ok, direct whisper transcription test passed, two service restarts passed. Bot token stored in gnexus-creds secret "GNtranscribe token" (881b7fa9-1775-4058-b256-04aa5737e62d).
|
| 2026-09-18 |
Add bugtrail.gnexus.space proxy mapping with dedicated LE cert; refresh internal-proxy-vps doc and nginx proxy inventory
...
Issued dedicated Let's Encrypt certificate for bugtrail.gnexus.space on the internal proxy VPS (192.168.1.226), added HTTPS :443 server block to the bugtrail nginx site (proxy to 192.168.1.177:80), verified healthz/panel/git.gnexus.space. Documented the new mapping plus previously undocumented enabled sites (creds, fuckjira, transcribe-demo, vmk-marginator).
|
| 2026-09-16 |
Document navi.service (Navi Proxy, port 8099) on ovpn_reserv
...
Verified via SSH on 2026-09-16: VM ovpn_reserv (192.168.1.226) runs navi.service (systemd, user ubuntu, WorkingDirectory /home/ubuntu/navi-1, ExecStart .venv/bin/navi-server) listening on 0.0.0.0:8099 with /health endpoint. Config at /home/ubuntu/navi-1/.env (OLLAMA_API_KEY, OLLAMA_HOST=https://ollama.com). No ollama_backends.json exists. SSH access as user ubuntu (root denied). No secrets stored.
|
Document VM tg_bots (192.168.1.254) navi melody instance and Ollama key rotation
...
New doc 10-systems/servers/tgbots-vm-navi-melody.md: VM tg_bots (192.168.1.254, hostname tgbots) runs mardisbot.service and navi.service (navi instance melody, port 8099, WorkingDirectory /home/ubuntu/navi-1). Ollama API key rotated 2026-09-16 in /home/ubuntu/navi-1/.env; ollama_backends.json not present on this instance; backup .env.bak-ollama-20260916 created; service restarted and verified active with /health HTTP 200.
|
Add service-host (192.168.1.176) doc and inventory: navi zoe instance + GHard panel
...
Rotated Ollama API key on navi zoe instance (192.168.1.176): updated OLLAMA_API_KEY in /home/ubuntu/navi-1/.env, restarted navi.service (active). No ollama_backends.json exists on the host. Documented host and service in gnexus-book (no secret values stored).
|
| 2026-09-04 |
Fix dead action aliases in API examples; add live-alias warning
...
Live recon 2026-09-04 confirmed the example aliases master_room_lamp_switcher and hallway2_lamp_switcher are dead (not registered by code, return null). Replaced with live aliases master_toggle and hall2_toggle; added a warning pointing to the verified live action list.
|
smart-home-server: add GAuth fix verification status (cross-context state validation confirmed)
...
Verification status appended to the GAuth OAuth State/PKCE Storage section: cross-context state validation confirmed via two-cookie-jar flow emulation on 2026-09-04.
|
Document file-based GAuth OAuth state/PKCE stores applied on 2026-09-04
...
Applied the file-based OAuth state/PKCE store fix on shome (2026-09-04); storage locations, wiring, and rollback backups are durable operational facts for future auth debugging.
|
smart-home-server: задокументирован SSH-пользователь shome, зафиксирован часовой пояс Europe/Kyiv после фикса
...
Live SSH diagnostics on 2026-09-04: host timezone was Etc/UTC (local time lagged 3h behind Kyiv), NTP was healthy. Fixed via timedatectl set-timezone Europe/Kyiv; /etc/timezone and /etc/localtime verified. SSH username shome discovered (was undocumented) and added to hosts inventory. Doc updated with Access & Time section.
|
| 2026-05-14 |
Add API usage instructions for triggering ControlScripts actions to smart-to-home-server.md with frontmatter.
...
Adding API usage instructions for triggering actions, as discovered during troubleshooting. I included the frontmatter to avoid validation errors.
|
| 2026-05-10 |
Document smart home server platform
Eugene Sukhodolskiy
committed
on 10 May
|
Seed smart home and 3D printer knowledge
Eugene Sukhodolskiy
committed
on 10 May
|
| 2026-05-09 |
Document home LAN topology and discovery observations
Eugene Sukhodolskiy
committed
on 9 May
|
Document public VPN and internal proxy route
Eugene Sukhodolskiy
committed
on 9 May
|