Quote from: ETFbitcoin on Today at 12:08:16 PM

The debug.log seems to be incomplete since it doesn't log any connection problem (e.g. cannot connect to proxy or to other node). You should check your system log and see message which generated by Tor.

Quote from: NotATether on Today at 11:25:31 AM

If you can, check if you have any peers - maybe there are no Tor v3 peers for your node, although I would be baffled if that is indeed the case.

debug.log file state peers.dat has 57414 addresses, so IMO it's very unlikely. Although OP can add node which use .onion link from https://github.com/bitcoin/bitcoin/blob/master/contrib/seeds/nodes_main.txt#L781-L792

Does not mean that it can reach those nodes.

OP, can you check https://bitnodes.io to see if it sees your node.
Bitnodes is NOT A PERFECT test. But if it sees it and you are not updating it's probably on your side since it can be seen.
If bitnodes does not see it, then it could be it just does not see it. Other nodes might.

And, since you were experimenting with the OS, when did you notice that it stopped working vs what were some of the last changes you made?

-Dave