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

When loading my wallet I get "Error: Failed to connect to a federation" #1295

Open
inna-btc opened this issue Sep 4, 2024 · 5 comments
Open
Labels

Comments

@inna-btc
Copy link

inna-btc commented Sep 4, 2024

Restoring the seed on a clean machine results in the same problem. What can I do in the situation?

@TonyGiorgio
Copy link
Collaborator

Submit logs

@inna-btc
Copy link
Author

inna-btc commented Sep 4, 2024

There are a hundreds if these in Chrome console logs:

Connection to 'wss://bravo.mainnet-25-madeira.dev.fedibtc.com/' failed:
(anonymous) @ mutiny_wasm.js:5397
Show 1 more frame
Show lessUnderstand this error
mutiny_wasm.js:5404 WebSocket is already in CLOSING or CLOSED state.
(anonymous) @ mutiny_wasm.js:5404
Show 1 more frame
Show lessUnderstand this error
mutiny_wasm.js:5397 WebSocket connection to 'wss://alpha.mainnet-25-madeira.dev.fedibtc.com/' failed:
(anonymous) @ mutiny_wasm.js:5397
Show 1 more frame
Show lessUnderstand this error
mutiny_wasm.js:5397 WebSocket connection to 'wss://charlie.mainnet-25-madeira.dev.fedibtc.com/' failed:
(anonymous) @ mutiny_wasm.js:5397
Show 1 more frame
Show lessUnderstand this error
mutiny_wasm.js:5404 WebSocket is already in CLOSING or CLOSED state.
(anonymous) @ mutiny_wasm.js:5404
Show 1 more frame
Show lessUnderstand this error
mutiny_wasm.js:5404 WebSocket is already in CLOSING or CLOSED state.
(anonymous) @ mutiny_wasm.js:5404
Show 1 more frame
Show lessUnderstand this error
mutiny_wasm.js:5397 WebSocket connection to 'wss://delta.mainnet-25-madeira.dev.fedibtc.com/' failed:
(anonymous) @ mutiny_wasm.js:5397
Show 1 more frame

But in the debug logs, it doesn't look too bad, ending with

2024-09-04 17:34:33.836 7528 DEBUG [mutiny_core::node:923] Persisting monitor for output: OutPoint { txid: 0xd..., index: 0 }
2024-09-04 17:34:34.013 7528 INFO [mutiny_core::nodemanager:1241] We are synced!
2024-09-04 17:34:34.013 7528 TRACE [mutiny_core::nodemanager:1247] finished calling sync
2024-09-04 17:34:34.320 7528 DEBUG [mutiny_core::node:944] notified channel monitor updated: OutPoint { txid: 0x..., index: 0 }

In the beginning of the debug log, there is
2024-08-15 22:16:50.268 9dba ERROR [mutiny_core::federation:293] Could not open federation client: Federation rpc error {general => Received errors from 2 peers: peer-0: Rpc error: The background task closed WebSocket connection failed; restart required, peer-1: Rpc error: The background task closed WebSocket connection failed; restart required), 0 => Rpc error: The background task closed WebSocket connection failed; restart required)1 => Rpc error: The background task closed WebSocket connection failed; restart required), }

Do you want the entire debug log file? I'm a bit cautious on posting it here.

@marksftw
Copy link

marksftw commented Sep 6, 2024

It's trying to connect the Madeira federation. Is that one offline?

@inna-btc
Copy link
Author

inna-btc commented Sep 6, 2024

Yes, I think so. I don't remember connecting to it though, I think I have connected to some other federation. Is this a hack?

@inna-btc
Copy link
Author

Is there a resolution? I don't have any funds in the federation, but I did have lightning channel open.

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

No branches or pull requests

4 participants
@inna-btc @TonyGiorgio @marksftw and others