Matt Joiner

There is a sort of integration test in a semi-formed state that could help with this once we have a better reason.

I don't quite follow. If they're not able to contact the webseed, there should be errors generated telling you why.

There's no reason TLS shouldn't work, I've had it work before with webseeding in production scenarios. I think if there's a bug it's that you're not seeing helpful log messages....

I'm not sure WebTransport is the correct config item, unfortunately there are quite a few of them due to slight variations in how http is consumed in BitTorrent that I...

Okay, as above being banned would make sense. Is it possible your http server does not implement range requests or is serving incorrect or incomplete data?

Great. It's very likely missing a "tickle" for webseed peers if reader priorities have already been set. I should be able to statically verify that.

I've not implemented this yet. https://github.com/anacrolix/torrent/issues/248.

I've pushed fixes to master that should improve webseed performance, and fix the stall that occurs if you add webseeds *after* adding the torrent (and some delay).

> I am also seeing error error running handshook conn: main read loop: decoding message: reading message length: EOF I think webseed may not used below config config.WebTransport = &http.Transport{...

> Thanks for the update, @anacrolix. I have another question based on this. > > In my public cloud environment, nodes are spread across different AZs/racks within a VPC network....