Monerodocs author here. I actually had the very same issue you described.

These two things combined should help:

• Use add-priority-node instead of add-peer for all peers.
• Pick onion nodes that are up-to-date and reliably online from these rankings: https://xmrguide.org/remote_nodes and https://monero.fail/ instead of static documentation.

Obviously, one can also remove the tx-proxy=tor,127.0.0.1:9050,16 option to broadcast wallet-originating transactions over clearnet. But that is what we wanted to avoid with this setup in the first place. For non-anonymous open nodes it's probably better to not be considered the "originating" node.

PS I am updating the docs to reflect this.

Monerodocs author here. I actually had the very same issue you described.

These two things combined should help:

• For each add-peer config entry add similar add-priority-node entry. This is a workaround to force monerod to reconnect with these peers after they drop (which is very common on Tor).
• Pick onion nodes that are actually online and working from these fine rankings: https://xmrguide.org/remote_nodes and https://monero.fail/ instead of static documentation example.

Obviously, one could also remove the tx-proxy=tor,127.0.0.1:9050,16 option to broadcast wallet-originating transactions over clearnet. But that is what we wanted to avoid with this setup in the first place. For non-anonymous open nodes it's probably better to not be considered the "originating" node.

PS I've updated the docs to reflect this.

Monerodocs author here. I actually have the very same issue you described. In the past it only happened occasionally. Now it seems prevalent.

It's like all the onion nodes are somehow flawed or not available to route the transactions.

Unfortunately, I am not aware of any good solution.

Obviously, one can simply remove tx-proxy=tor,127.0.0.1:9050,16 to broadcast wallet-originating transactions over clearnet. But that is what we wanted to avoid with this setup in the first place. For non-anonymous open nodes it's probably better to not be considered the "originating" node.

Monerodocs author here. I actually had the very same issue you described.

These two things combined should help:

• Use add-priority-node instead of add-peer for all peers.
• Pick onion nodes that are up-to-date and reliably online from these rankings: https://xmrguide.org/remote_nodes and https://monero.fail/ instead of static documentation.

Obviously, one can also remove the tx-proxy=tor,127.0.0.1:9050,16 option to broadcast wallet-originating transactions over clearnet. But that is what we wanted to avoid with this setup in the first place. For non-anonymous open nodes it's probably better to not be considered the "originating" node.

PS I am updating the docs to reflect this.