I recently switched to aw-server-rust by editing the config file so it starts automatically. However, now that I’m running aw-server-rust and not running aw-server, I’m seeing that aw-watcher-window and aw-watcher-afk can no longer communicate with the server. The Chrome browser extensions is still communicating fine but it’s communicating on port 5666 because I’m running it as an unpacked extensions after modifying it to work with Brave.
Are aw-watcher-window and aw-watcher-afk hardcoded to communicate on port 5600, and that’s why they are no longer working? Do I need to be running both aw-server and aw-server-rust simultaneously to fix this? The documentation mentions there being a database migration when using aw-server-rust so I wouldn’t think I should run both?
The log file for aw-watcher-window contains lots of lines like this:
2022-06-07 22:46:05 [WARNING]: Not connected to server, 12089 requests in queue (aw_client.client:467)
so it really feels like they are just trying to communicate on the wrong port.
I’m running the v0.12.0 beta on Windows 10, if it matters.