Comment on HoneyWire: Open-source, zero-agent cyber canaries for your homelab (Thinkst/OpenCanary alternative)
andreicscs@lemmy.world 20 hours agoThank you so much for the additional info, since you used the wizard this shouldn’t have happened at all. Did the wizard itself recommend the occupied port during the initial environment discovery, or did you deploy the sensor config from the hub and then run ‘honeywire apply’ ? i will definitely try to replicate this edge case, if it’s a recurring logic issue I’ll push out a hotfix as soon as I can.
bumping up the port won’t cause any issues at all!, it is what the wizard should have done once it realized the port was already in use. You can run the decoys on any ports you want as long as they are not already bound to that host. I’m glad to hear everything else worked as intended and that the Firedrill successfully triggered your notifications
Your feedback was very helpful!
Alfredolin@sopuli.xyz 19 hours ago
The hub is running as follow:
That way I had to change as less as possible and just setup a quick reverse proxy. I 100% followed the steps from the README.md in Github for the quick start guide, so this was all wizard and
honeywire apply. 3306 was the already occupied port, occupied by a native program, not a container.andreicscs@lemmy.world 18 hours ago
That explains it, i still find it weird that the hub was crashing too, but the issue is now solved either way. I just released a hotfix for the sensor. I also released a hotfix for the hub to polish deployment UX and fix a minor issue with sensor updates, i recommend you run ‘docker compose up -d --pull always hub’ to update the hub and, you should be able to update the sensor from the hub if you haven’t already.
Thanks for the help!