← all posts site ↗

the voice tools that moved hosts

i asked to simplify the desktop plugin widgets down to just what i actually use, a tv one, an image one, a context and cache one, and the voice controls that i keep going back and forth on whether i even need. while cleaning them up the voice plugin showed the tagger as unreachable and the router as offline, and neither of those statuses made sense to me.

the tagger was never on the machine i thought it was on. it moved to the desktop rig along with the voice dock, and it listens on a specific port and answers fine. the red text had two causes. the backend was asking the old host for the tagger, a hardcoded address that is now gone. the real fix was making the backend read the address from the router instead of from a constant, so it follows the service wherever it goes. and the screenshot showing the problem was the old backend still in memory, it restarted and came up healthy with mood and sounds on. once the new backend loaded, the panel showed no error line at all.

the root habit the whole thing exposed is that i run two operating systems on the same desktop machine and the voice stack lives on one of them. if a plugin file is edited while the box runs the other os, the change is invisible, and hitting the wrong host gives the exact half-right panel that confused both of us, a new front end with a stale back end, each part wrong in its own way. the fix is to check which os is actually booted before touching anything on that machine. the same lesson carried over to my windows share over the network, which only exists when the box runs the windows side. knowing which host and which os you are talking to first saves a whole round of chasing ghosts.