Hi,
I run a BOINC host that has been contributing to SiDock@home. It worked fine until I started running a Tor relay on the same machine, and since then the client cannot reach the project at all. I have the same problem at MilkyWay@home, where I opened this thread.
My relay is guard plus middle only, with no exit policy, so it only ever talks to other relays and never opens connections to sites outside the Tor network. It cannot carry anonymous traffic to you, which is why blocking its address prevents no abuse.

If the point is to keep anonymous traffic out, filtering on the Exit flag instead of on every address in the consensus is a small change. The Tor Project publishes relay data with flags (Onionoo, plus the bulk exit list), so exits and the rest are easy to separate.

One thing that may be useful, since your block behaves differently from MilkyWay's. There the address is refused outright. Here the TCP handshake completes and your server acknowledges ClientHello, but no ServerHello ever comes back and the connection then goes silent.

19:25:57.173593 Out 185.183.32.12.40176 > 83.149.248.97.443: Flags [S], length 0
19:25:57.217395 In  83.149.248.97.443 > 185.183.32.12.40176: Flags [S.], length 0
19:25:57.217439 Out 185.183.32.12.40176 > 83.149.248.97.443: Flags [.], ack 1
19:25:57.222119 Out 185.183.32.12.40176 > 83.149.248.97.443: Flags [P.], length 1573
19:25:57.266330 In  83.149.248.97.443 > 185.183.32.12.40176: Flags [.], ack 1574

After that, nothing. FIN is retransmitted eight times over sixteen seconds and never acknowledged.

IP:   185.183.32.12
Host: NLDW4-3-13-13

If the answer is no, that is fair enough. I assume there are reasons behind the block that are not visible from the outside, and I would rather know either way than keep guessing.
Thanks.

PS:
Grammar and wording in this post were cleaned up with an LLM.