I'm running a relay in my computer. Using orfox I set it as Entrance Node, but it shows WARN: Remote server sent bogus reason code 65022 I couldn't find this error in any site. Is there something wrong with my relay?

  • It would certainly seem that one of the relays in the circuit sent a bogus reason, although it may not be yours, see: 5.4. Tearing down circuits. So it could be your relay, or another relay along the circuit. If it happens to you for all circuits, it's probably your relay but we'd need more information to say for certain.
    – cacahuatl
    Feb 15, 2017 at 7:26
  • It's probably my relay. Because qhen I don't set a especific entry relay in orfox, it works.My torrc below GeoIPFile C:\Users\Rodrigo\Documents\Tor\tor-win32-\Data#\Torgeoip GeoIPv6File C:\Users\Rodrigo\Documents\Tor\tor-win32-\Data#\Tor\geoip6 ORPort 4443 DirPort 9990 #ORPort Exitpolicy reject : #AccountingMax 10 GB #AccountingStart day 00:00 #RelayBandwidthRate 500 KBytes #RelayBandwidthBurst 1 MBytes MaxMemInQueues 2048 MBytes #Log debug file C:\Users\Rodrigo\Documents\Tor\tor-win32-\Data\Tor\log.txt P.S. Its a windows 7 tor-win32-
    – Rodrigo
    Feb 15, 2017 at 8:53

1 Answer 1


I think, actually, this is a bug in the client not the relay.

The circuit is failing but the error message is possibly a problem in the client, my reasoning is that the spec states:

The payload of a RELAY_TRUNCATED or DESTROY cell contains a single octet.

Since an octet is 1 byte and 65022 > 255, this value can't be carried in a valid cell so it must be local to the client.

I think what you're seeing is this: #20307, essentially it's taking a signed integer and converting it to an unsigned short and your control port gets that bogus reason code. It's a bug in Tor, it should (?) be patched but it may be that Orbot hasn't applied and pushed the patched version yet.

  • Could it be because I'm not a guard node?
    – Rodrigo
    Feb 15, 2017 at 10:50

You must log in to answer this question.

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