firod does not get a tor .onion address

[krilson]

Describe the issue

Firod does not get an .onion address successfully.

firo/debug.log 2025-03-18 08:52:19 tor: Connected to Tor version 0.4.8.14 2025-03-18 08:52:19 tor: Supported authentication method: COOKIE 2025-03-18 08:52:19 tor: Supported authentication method: SAFECOOKIE 2025-03-18 08:52:19 tor: Using SAFECOOKIE authentication, reading cookie authentication from /run/tor/control.authcookie 2025-03-18 08:52:19 tor: SAFECOOKIE authentication challenge successful 2025-03-18 08:52:19 tor: AUTHCHALLENGE ServerHash xxxxxxxxxxxxxxxxxxxxxxxxxxx ServerNonce xxxxxxxxxxxx 2025-03-18 08:52:19 tor: Authentication successful 2025-03-18 08:52:19 tor: Add onion failed; error code 513

On tor side, the log shows no error, only: tor[7571]: Mar 18 09:52:19.000 [notice] New control connection opened from 127.0.0.1.

Local setup

Debian 12 Tor version 0.4.8.14 firo-0.14.14.0

Any extra information that might be useful in the debugging process.

On same machine, bitcoind and litecoind get a .onion address normally, e.g. they do not get the "Add onion failed; error code 513" error.

[justanwar]

What are the Bitcoin and Litecoin versions?

[ghost]

What are the Bitcoin and Litecoin versions?

LTC: LitecoinCore:0.21.4 BTC: Satoshi:27.0.0

[Nishiji-eng]

What changes to your torrc (tor config file) did you make?

[ghost]

What changes to your torrc (tor config file) did you make?

Sorry for the late reply, I didn't make any changes in torrc, this is the setup I have that works normally with bitcoin/litecoin:

SOCKSPort 9050
Log notice stdout
ControlPort 9051
CookieAuthentication 1
CookieAuthFileGroupReadable 1

Btw, its still the same on the latest version, 0.14.14.1 tor: Add onion failed; error code 513