Topic: Appimage parameters to connect to our node (Read 238 times)
Great! Thanks for coming back to tell us what you did to fix it, hopefully it can help others in a similar position if they come across this thread!
Thanks all, found the issue and posting it here in case someone else have the same problem.
I just needed to remove that portion "-p socks5:localhost:9050"
So the correct command line is simply:
"./electrum-4.0.0b1-x86_64.AppImage -1 -s mynodeaddress.onion:50001:t"
I just needed to remove that portion "-p socks5:localhost:9050"
So the correct command line is simply:
"./electrum-4.0.0b1-x86_64.AppImage -1 -s mynodeaddress.onion:50001:t"
Do you have access to your tor node, can you try running netstat - rn to check the port's open (the one you're trying to make the first hop to).
You could also try proxying to 9150 instead of 9050 (port wise) mine switched - probably due to another process or that port being closed - but as a 2 second task it might be worth a try...
You could also try proxying to 9150 instead of 9050 (port wise) mine switched - probably due to another process or that port being closed - but as a 2 second task it might be worth a try...
Hi,
What is the command to launch an Linux Appimage of Electrum 4 to connect directly to my our node (on Tor) ?
Here's what I've tried which used to work but not anymore (i.e.: the network connection remains "red" and doesnt turn "blue):
"./electrum-4.0.0b0-x86_64.AppImage -1 -s mynodeaddress.onion:50001:t -p socks5:localhost:9050"
Thanks
What is the command to launch an Linux Appimage of Electrum 4 to connect directly to my our node (on Tor) ?
Here's what I've tried which used to work but not anymore (i.e.: the network connection remains "red" and doesnt turn "blue):
"./electrum-4.0.0b0-x86_64.AppImage -1 -s mynodeaddress.onion:50001:t -p socks5:localhost:9050"
Thanks
Jump to: