Skip to content

hardcoded URIs? #114

Description

@josepot

After I ran just create-polkadot-pre-migration-snapshot I noticed that the initial syncing wasn't starting, so I had a look at the sync-node-para.log file and I found this:

2025-07-19 13:50:48.001  INFO tokio-runtime-worker reconnecting-websocket-client: [Parachain] Trying to connect to next external relaychain node. attempt=4 index=0 url="wss://polkadot-rpc.dwellir.com:443/"
2025-07-19 13:50:48.003 ERROR tokio-runtime-worker reconnecting-websocket-client: [Parachain] Retrying to connect to any external relaychain node failed.
2025-07-19 13:50:48.003 ERROR tokio-runtime-worker reconnecting-websocket-client: [Parachain] No valid RPC url found. Stopping RPC worker.
2025-07-19 13:50:48.003 ERROR tokio-runtime-worker sc_service::task_manager: [Parachain] Essential task `relay-chain-rpc-worker` failed. Shutting down service.
Error:
   0: Application: Unable to communicate with RPC worker: RPC worker channel closed. This can hint and connectivity issues with the supplied RPC endpoints. Message: oneshot canceled
   1: Unable to communicate with RPC worker: RPC worker channel closed. This can hint and connectivity issues with the supplied RPC endpoints. Message: oneshot canceled

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

Naturally, I tried to find a config file where I could replace the problematic URI. However, it seems that endpoint (wss://polkadot-rpc.dwellir.com:443) must be hardcoded somewhere, b/c I couldn't find any config file where that URI could be changed.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions