Skip to content

CppBridge connection always fails with ECONNREFUSED #746

Description

@mberemand

Any time the Python code tries to invoke something from the compiled C++ code, it always fails with ECONNREFUSED. I'm at a loss for why this is. I built using the instructions outlined in linux.md, having cloned and manually built libbtc and libwebsockets as recommended.

-INFO  - 2025-12-23 - 16:00:41.058: (../../cppForSwig/BridgeAPI/CppBridge.cpp:840) connecting to ArmoryDB
[2025/12/23 16:00:41:0675] N: lws_create_context: LWS: 4.5.99-v4.5.0-12-g5acb375a, NET CLI SRV H1 H2 WS SS-JSON-POL ConMon IPv6-absent
[2025/12/23 16:00:41:0677] N: [wsicli|0|WS/h1/default/127.0.0.1]: lws_client_connect_check: getsockopt fd 16 says ECONNREFUSED
-ERROR - 2025-12-23 - 16:00:41.067: (../../cppForSwig/WebSocketClient.cpp:359) lws client connection error
-ERROR - 2025-12-23 - 16:00:41.067: (../../cppForSwig/WebSocketClient.cpp:362)    error message: conn fail: ECONNREFUSED
-INFO  - 2025-12-23 - 16:00:41.067: (../../cppForSwig/WebSocketClient.cpp:338) lws client cleaned up
(WARNING) CppBridge.py:330 - unknown reply referenceId: 2

I've started with the dev branch and merged in PartySensei's pending contributions from his fork, making other small changes as I run into Python runtime errors. I'm trying to get it to work just enough to export the root keys of an old wallet.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions