gui: node shutting down after incorrect proxy IP address input #809

1. 
   nbit846 commented at 3:27 pm on March 27, 2024: none

   Issues, reports or feature requests related to the GUI should be opened directly on the GUI repo

   • I still think this issue should be opened here

   Report

   My node was running fine until I decided to change the setting under the nerwork tab, I checked the box for “Use separate SOCKS5 proxy to reach peers via Tor onion services” and on Proxy IP box i put 127.0.0.1:9150, on Port box 9150. When I tried to restart the node it wont start anymore, it gives me “Error 127.0.0.1:9150 incorrect Proxy” and it shuts down immediately. What can I do to get the node to start again? the GUI is not even starting. I just stared exploring with bitcoin nodes and Im not knowledgable at all, any help will be greatly appreciated. Im running the node on Debian Linux.

2. 
   willcl-ark commented at 3:38 pm on March 27, 2024: member

   Hi @nbit846,

   This issue tracker is supposed to be used to track technical issues related to the Bitcoin Core GUI code base.

   General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange or the #bitcoin IRC channel on the Libera Chat network.

   In your case I’d advise checking the bitcoin data directory (~/.bitcoin) while the node is not running. You should find a file named settings.json which may be persisting the erroneous setting. This can be removed and the node then restarted.

   That said, I don’t experience the same issue as you when specifying a bad port in that dialogue box, so I’m not totally convinced this is the root cause of your issue (nor that the above step will solve it). Are the any other errors printed in ~/.bitcoin/debug.log?

3. 
   nbit846 commented at 8:30 pm on March 27, 2024: none

   I didnt see any other errors printed just this: 2024-03-27T20:18:53Z Loaded 64927 addresses from peers.dat 352ms 2024-03-27T20:18:53Z init message: Loading banlist… 2024-03-27T20:18:53Z SetNetworkActive: true 2024-03-27T20:18:53Z Error: Invalid -onion address or hostname: ‘127.0.0.1:9050:9050’ 2024-03-27T20:19:06Z Shutdown: In progress… 2024-03-27T20:19:06Z scheduler thread exit 2024-03-27T20:19:06Z Flushed fee estimates to fee_estimates.dat. 2024-03-27T20:19:06Z Shutdown: done
4. 
   nbit846 commented at 8:49 pm on March 27, 2024: none

   can I just change the settings on settings.json instead of deleting it? I dont want to go to default settings, Im not sure if it will affect the fact that I had a Tor hidden service set up already.
5. 
   maflcko commented at 7:22 am on March 28, 2024: contributor

   It sounds like a bug, if the GUI settings allow to set a setting that will refuse to re-start the node.
6. maflcko added the label Bug on Mar 28, 2024
7. 
   willcl-ark commented at 8:17 am on March 28, 2024: member

   Yeah. It should not allow port to be duplicated as per this line:

   2024-03-27T20:18:53Z Error: Invalid -onion address or hostname: ‘127.0.0.1:9050:9050’

8. 
   nbit846 commented at 2:54 am on March 29, 2024: none

   I was able to start the node by deleting only the hostname on the settings.json. Thank you so much
9. willcl-ark referenced this in commit 94173eac6e on Apr 3, 2024
10. 
    pablomartin4btc commented at 2:23 am on April 4, 2024: contributor

    Shouldn’t the title of the issue be updated? Perhaps adding " - root cause: incorrect proxy IP address input" or something? It’ll be more useful navigating thru the issues list I think.
11. fanquake renamed this:
    Node shutting down immediately
    gui: node shutting down after incorrect proxy IP address input
    on Apr 4, 2024
12. willcl-ark referenced this in commit 10c5275ba4 on Apr 4, 2024
13. hebasto closed this on May 11, 2024

    ---

14. hebasto referenced this in commit 3207286680 on May 11, 2024

Contributors
nbit846 willcl-ark maflcko pablomartin4btc

Labels
Bug