Upon trying to start it I get this:

Mar 04 08:09:00 beeldbox Tor[30025]: No signature found on key certificate

Thing is this was working fine yesterday

I've finally built up enough consensus weight to be used as a relay and really don't want to start over..... Again. I'm trying to transfer to a new server.

Both servers running Ubuntu 18.04. Error reproducible on both

EDIT Removed all the cached certs and that's gone. Now it gets stuck @ Bootstrapping 0% with nothing further in logs.

Mar 04 18:02:54 * Tor[25711]: Bootstrapped 0% (starting): Starting
Mar 04 18:02:54 * Tor[25711]: Starting with guard context "default" 
Mar 04 18:02:54 * Tor[25711]: Signaled readiness to systemd
Mar 04 18:02:55 * Tor[25711]: Opening Socks listener on /run/tor/socks
Mar 04 18:02:55 * Tor[25711]: Opened Socks listener on /run/tor/socks 
Mar 04 18:02:55 * Tor[25711]: Opening Control listener on /run/tor/control
Mar 04 18:02:55 * Tor[25711]: Opened Control listener on /run/tor/control
  • I don't think I'll be able to help with this, but what was the version of tor on the old server, and what's the version on the new server? Also double check that the permissions on all of the files are correct.
    – Steve
    Mar 4, 2020 at 4:45
  • @Steve both servers
    – unixandria
    Mar 4, 2020 at 11:52
  • @Steve question updated
    – unixandria
    Mar 4, 2020 at 17:04
  • I'm not sure what the problem could be, is this with the default torrc? And you don't have any incoming/outgoing firewall rules that could be interfering? I would try deleting config files, re-installing tor, and using the default torrc (with default relay settings and a new cert). If that works, you can then start introducing changes and using your old relay's cert, and see when it breaks. If no one answers on here, I recommend asking on #tor or #tor-relays on IRC, you might have to wait a while, but it's a good place to ask for these types of technical problems.
    – Steve
    Mar 4, 2020 at 17:38
  • @Steve I did try that same issue. So it not the keys
    – unixandria
    Mar 4, 2020 at 18:05

1 Answer 1


Several issues were present:

1) Firewall was too restrictive preventing connections to a necessary port (53, for local dns resolving)

2) Torrc misconfiguration. Not entirely sure which option.

3) Network interface misconfiguration, preventing connections to the IP for was set to use (server had 2 ipv4 ips and /64 block of ipv6

4) Bad cached certs

Hope my struggle helps someone else!

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .