I have found the problem and fixed in for next bugfix release. Thanks a lot for reporting this. It was indeed an initialization problem: this private tracker blacklists the default port but torrents from watched directories were added before the new port was set.
I have found the problem and fixed in for next bugfix release. Thanks a lot for reporting this. It was indeed an initialization problem: this private tracker blacklists the default port but torrents from watched directories were added before the new port was set.