Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom electrum server can't connect on iOS and new Android app #401

Open
PeteClubSeven opened this issue Aug 24, 2023 · 16 comments
Open

Custom electrum server can't connect on iOS and new Android app #401

PeteClubSeven opened this issue Aug 24, 2023 · 16 comments

Comments

@PeteClubSeven
Copy link

Hi, my Android wallet was recently upgraded and initially it remembered the custom electrum server I previously set (a Tor .onion address). However when changing it to a LAN address or changing to a different onion address the feature seems completely broken and I'm unable to get it to work again. I've tested that my server works via its IP address on the LAN as well as via Tor using BlueWallet (iOS & Android) and Sparrow (macOS).

My server:

  • Latest OpenSUSE MicroOS
  • Bitcoind v25.0.0
  • Fulcrum v1.9.1
    • Listening on 0.0.0.0, port 50001 for TCP and port 50002 for TLS with a self-signed certificate
  • Tor v0.4.7.14
    • An onion service is configured for ports 50001 and 50002

My Android:

  • Fairphone 4 running /e/OS 1.13 (Android 12 w/ microG)
  • Phoenix v2.0.2 w/ Tor enabled

My iPhone:

  • iPhone SE 2022 running iOS 16.6
  • Phoenix v1.6.3 w/ Tor enabled

The different scenarios I tried:

  • Connect directly via the LAN on port 50002
    • Android: Receive untrusted certificate warning, click "Trust certificate", notice the electrum server never connects
    • iOS: Receive untrusted certificate warning, click "Trust certificate & pin public key", click "Save", notice the Electrum server never connects
  • Connect over Tor on port 50002
    • Android: Receive error "Failed to connect: This address cannot be resolved."
    • iOS: "Checking server certificate..." is shown with an option to cancel
  • Connect directly via the LAN on port 50001
    • Android: The app crashes when trying to set the custom server
    • iOS: "Checking server certificate..." is shown with an option to cancel
  • Connect over Tor on port 50001
    • Android: Receive error "Failed to connect: This address cannot be resolved."
    • iOS: "Checking server certificate..." is shown with an option to cancel
@aeonBTC
Copy link

aeonBTC commented Aug 29, 2023

I am having the same problem on Android.

Connecting to my custom fulcrum electrum server worked fine before upgrading to the split channel migration. But now I can no longer connect to my server via onion address. Tried from my localhost address as well and both return, Failed to connect: Address cannot be resolved.

@anthony-robin
Copy link

Same problem with Phoenix Android v2.0.4 when using Umbrel Electrs app at:

@jlahtela
Copy link

I have similiar issue. I did change change to public server as my MyNode did have issues. Then I did add my node TOR address back and it now says it cannot connect.
I have tested with other wallet and it works with it, but not with new phoenix wallet, I did migrate to it.

@martinschwarz
Copy link

@t-bast did you guys remove the option to connect to an electrum server via tor without a certificate? It was working after migrating to v2 but I can't get the same settings to work again after temporarily disabling the custom electrum server.

@Scapegoat81
Copy link

Cannot connect my electric server either. I had it connected until the recent big update, now it just connects to random servers.

Pretty annoying as Phoenix is THE preferred wallet for me but as of now useless if I can’t connect my own node.

@aeonBTC
Copy link

aeonBTC commented Dec 14, 2023

Connecting to my fulcrum node over Tor is working now. The issue seems to have been fixed!

@Scapegoat81
Copy link

Scapegoat81 commented Dec 15, 2023

Still doesn’t work for me, running latest iOS

@dpad85
Copy link
Member

dpad85 commented Dec 15, 2023

Sorry I forgot to update this ticket following Android v2.0.13. The Android app should now work with an .onion address, provided you use the plain TCP port.

The iOS app is a bit behind for now, and the fix is not available there (should be next week).

@Scapegoat81
Copy link

Oh sweet, LFG 🫡🙌🏼

@PeteClubSeven
Copy link
Author

Sorry I forgot to update this ticket following Android v2.0.13. The Android app should now work with an .onion address, provided you use the plain TCP port.

The iOS app is a bit behind for now, and the fix is not available there (should be next week).

This is great to hear, can't wait for full support again!

@martinschwarz
Copy link

works for me again now. can be closed. thanks!

@digitalofficina
Copy link

i am having the same problem on Android.

Connecting to my custom umbrel electrs server worked fine before upgrading to the split channel migration. But now I can no longer connect to my server via onion address.

@ghost
Copy link

ghost commented Jan 5, 2024

I am not able to establish a working connection to my own electrum server via tor.

Using Android, Version 2.1.1 all other connections (Internet, Tor, Counterpart) work. Tor especially is working.
I am connecting to my own fulcrum servia via adress.onion:50021, which has previously worked on Phoenix Wallet and which is the correct adress for my other wallets. The logs on my fulcrum server DO NOT show that there is a new client connected. Phoenix wallet permanently remains in "connecting" mode.

@sherlock627
Copy link

sherlock627 commented Jan 20, 2024

Is there any update on this bug? I would love to use Phoenix, but not without my own node. Thank you!

@Scapegoat81
Copy link

Running iOS 17.3 & still cannot connect to Electrs.
Internet starts connected while Lightning Peer & Electrum Server stay in the Connecting status….
IMG_4747

@ake-khada
Copy link

If these kind of issues are left ganging for more than years, I guess it means au revoir.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants