Author

Topic: Connection issue with my local full node (Read 50 times)

sr. member
Activity: 406
Merit: 443
March 05, 2024, 08:12:47 PM
#3
Since you mentioned the full node and port 8333, I assume that you are talking about bitcoin core full node and not Electrum Personal server because 8333 is exposed by the full node connection, not by EPS.

  • Make sure you are using Electrum Personal Server and that it is running using CLI
Code:
netstat -a
    Make sure port 50002 is open. [/li]
  • Delete cached cert file
  • Check the settings of the config.ini file for Electrum Personal Server and bitcon.conf for Bitcoin Core
  • Use local IP and port number 50002.

These steps should solve your problem, if not, paste the logs here.
legendary
Activity: 3206
Merit: 2904
Block halving is coming.
March 05, 2024, 02:13:57 PM
#2
Do you have an Electrum server installed?
If you're running a full node, using the local IP and port alone will not work. Make sure to install the Electrum server to use it as your local/personal server and you should be able to use it in your Electrum wallet if you set up the server properly.

Here's two of them including the guide Electrum Personal server and ElectrumX server
newbie
Activity: 1
Merit: 0
March 05, 2024, 01:14:22 PM
#1
I just installed 4.5.3 from Android playstore.
First thing it asked was to customise server, which I did since my full node has fully synced since last evening after a year's gap which took a week+ to update.
Next was to import a private key from an old JaXX wallet that has since been discontinued and I had some 10$ worth of bitcoin  for testing. This import was not properly confirmed since the connections status was Red.
I've went and checked the sellect automatic connection and it works with random nodes, but I still want to connect to my own.
Once the sync happened automatically, I got notified of the imported key and the amount, which is fine.
Now after trying to update the value it always returns to the initial one (private network IP).
After checking and unchecking and modifying it seems the value changes but the connection status is still Red.

I've tried connecting with/without the 8333 port, and with both public and private IP, none have worked. I also noticed a ":s" appended at the end of the server and can't seem to understand why and if that's the issue, since it works with standard/automatic adresses.
Any help is appreciated!
Jump to: