The hub is running as follow:

services:
  ...
  hub:
    ports:
      - "myportbehindreverseproxy:8080"
  ...

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.

Yes I used the wizard, which is very neat. Yeah, during the setup, all occupied ports are listed, including the one which was already occupied but nevertheless got used by one of the tcp tarpit decoys.

Now I just moved that decoys port (just did +1, I hope that doesn’t matter) from the UI which correctly changed the honeywire-compose.yml file. Now it seems to be running properly, and firedrill triggers the notifications.

I think you are right on the compose up crash upon port occupied.

It doesn’t matter if Github is more convenient, I, for example, am straight banned from it with no possibility to sign-up. Issue with arkoselabs not working from my ip/device, which is required to complete captcha for signup, and the support is non existent, see this post.

Ok, issue is clear: tcp-tarpit is trying to use an already occupied port. I was not sure how to check the containers log, your command was correct.

Yes, I was trying to deploy everything on the same machine as starter.

I found that I could change the port from the hub, under fleet management, now it seems to work.

I still don’t get why the hub stopped working though. Cpntainer log is only showing from the last start.

Hi.

hw-sensor-tcp-tarpit crashes and that stops also the hub. I don’t know how to check the logs for that container.

I can’t open issues or anything on Github (this the reminder for every foss project participant: please use an alternative to github).

Hahaha so true. At least the struggling part. I spent a lot of time before getting my things running smoothly, but hei I was a full beginner. It 's not that I don’t dare too ask, it’s just that usually I try hard to find a solution before asking and mostly get it working. But yeah, that’s many hours of setup.

Last paragraph: definitely.

If you can’t modify the compose file, you can try editing the container with Portainer. There you can change the network of gluetun qbittorrent to “container” and select gluetun.
That’s how I did it when I was running CasaOS.