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

Heimdall unable to connect to Bor on WebSocket #1161

Open
SimonKraus opened this issue May 10, 2024 · 1 comment
Open

Heimdall unable to connect to Bor on WebSocket #1161

SimonKraus opened this issue May 10, 2024 · 1 comment
Labels

Comments

@SimonKraus
Copy link

Heimdall is not able to connect to Bor via WebSocket.

Environment:

  • OS: Ubuntu 22.04.3 LTS
  • Install tools: Both software build from source on latest tagged release.

What happened:
Since updating Heimdall to v1.0.5 and Bor to 1.3.1 we faced a problem that Heimdall wasn't able to connect to Bor anymore and crashed on startup.
We fixed it by configuring an HTTP connection instead of WS.
The error message was:
2024/05/10 09:29:04 dial tcp 127.0.0.1:8546: connect: connection refused

What you expected to happen:
Expected to work (like before the update).

Have you tried the latest version:
yes

How to reproduce it (as minimally and precisely as possible):
Setup Heimdall and Bor and pair it through WS.

Logs (paste a small part showing an error:
2024/05/10 09:29:04 dial tcp 127.0.0.1:8546: connect: connection refused

Config (you can paste only the changes you've made):

# RPC endpoint for bor chain
bor_rpc_url = "ws://localhost:8546"

changed to:

# RPC endpoint for bor chain
bor_rpc_url = "http://localhost:8545"

Anything else we need to know:
Bor websocket is functional as other services use it through that port.

Copy link

This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the Stale label May 25, 2024
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

1 participant