joal: The port used by Joal is not seen as open by trackers

Hi @anthonyraymond,

Thanks for this great project. I observed that Joal will ‘seed’ on port 49152 however when I open that port in my router, no tracker can see it as open. I’ve also tried portchecker.co, canyouseeme.org and others.

Using Joal via Docker with the following docker run command:

docker run -d \
  --name joal \
  --network=host \
  --restart unless-stopped \
  -e TZ=Europe/Bucharest \
  -v /private/path/to/data:/data \
  anthonyraymond/joal:latest \
  --joal-conf="/data" \
  --spring.main.web-environment=true \
  --server.port="6688" \
  --joal.ui.path.prefix="prefix" \
  --joal.ui.secret-token="token"

Yes, I know how to open ports as the qBitTorrent (Wireguard + others) port is open and it’s visible by the above websites and trackers.

Any help? Some trackers will block any seeding attempts if the port is closed as uploading torrents IRL can’t be done on closed ports. Thank you

About this issue

Original URL
State: open
Created a year ago
Comments: 16 (7 by maintainers)

Most upvoted comments

Hi, may I know what port joal uses from 49152-65534 range? Or is there a default one? Need to know what port to open. Thanks.

It uses the first port in that range it’s able to bind to. Assuming no other program is using port 49152, it will be used. If it’s already in use, then it’ll try 49153 and so on until 65534.

laur89 on May 29, 2023

@rursache i know, i’ve red through the entire post, but i’ve provided extra details to keep here for future possible improvements.

I’ve not enabled sponsorship for now. I’m in the midle of rewriting the whole project in another language. Adding some high requesting feature along the way. When the new version gets released / stable, i’ll provide some retribution options. For now, even if JOAL works perfectly and the overall experience is totally safe for users, the code base has grown from an original poorly designed structure. I won’t feel conformtable making money out of this.

anthonyraymond on Feb 6, 2023

@anthonyraymond is this because we’re not really accepting any connections in ConnectionHandler?

Do you know what sort of I/O should happen between trackers and clients?

At any rate, started work on it here: https://github.com/anthonyraymond/joal/pull/187/files#diff-bc97f2cf481a4672f69346e371cb240ae51f309844399bda90a17072987b527dR79-R99

laur89 on Feb 3, 2023

@datsoy i have no idea what you’re talking about. just open port 49152 and you’re done.

rursache on May 28, 2023

@datsoy its 49152 as i said in my initial post.

rursache on May 28, 2023

Should be drop-in. If not, it’s a bug.

laur89 on Feb 3, 2023

Check out corresponding branch & build the image: docker build .

laur89 on Feb 3, 2023