You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Heimdall is not able to connect to Bor via WebSocket.
Environment:
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):
changed to:
Anything else we need to know:
Bor websocket is functional as other services use it through that port.
The text was updated successfully, but these errors were encountered: