DEL_ONION shutdown when trying to set up in Whonix #7864
Replies: 2 comments
-
The above issue seems to be resolved after I enabled ADD_ONION in onion-grater. However, I am now getting new errors.
As well as:
|
Beta Was this translation helpful? Give feedback.
-
I seem to have managed to fix this and now I have LND running in a Whonix Workstation. I have Bitcoind running in another Whonix Workstation. The error messages were somewhat less than ideal and most of my issues were due to the fact that Tor Control errors were not very apparent. There is absolutely no error reporting if ADD_ONION does not work as expected atleast with logging set to debug. When no onion service was created, LND shuts down due to error with DEL_ONION such as the errors I've shown above. Shutdowns and DEL_ONION errors were due to onion-grater filtering out ADD_ONION. This happened in two instances. When creating the regular onion service on port 9735 and then the watchtower service on port 9911. After I added onion-grater profiles and required firewall configurations in Whonix, everything seems to work well. |
Beta Was this translation helpful? Give feedback.
-
I have a Whonix Workstation running LND. It shuts down due to the following error:
[ERR] TORC: DEL_ONION got error: undefined response code: 510, err: unexpected code
This happens on the first run of LND a short while after I have started it. As far as I understand, at that point no Onion service has been started yet.
Error 510 is related to onion-grater which filters Tor Control commands. I have added an onion-grater profile that allows DEL_ONION with a non-empty Service ID. My question is, what is the purpose of DEL_ONION when no Onion service has been created in the first place and moreover, why does it crash entire LND when this happens?
UPDATE:
Having changed onion-grater to allow DEL_ONION with an empty Service ID, it now crashes with DEL_ONION error
DEL_ONION got error: invalid arguments: unexpected code
Beta Was this translation helpful? Give feedback.
All reactions