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

Beacon tries to reach https://goerli.infura.io over port 80, failing #1766

Closed
yorickdowne opened this issue Sep 28, 2020 · 1 comment
Closed
Assignees

Comments

@yorickdowne
Copy link

  • Nimbus beacon node v0.5.0 (da3102c)
  • Dockerized environment, buster-slim
  • Remote goerli.infura.io accessed via https://
  • beacon_node configured for testnet spadina

Beacon will fail to establish connection with infura. Logs show that it tries to reach it via 80, although URL is https://

The same failure is not observed when configuring testnet medalla.

beacon_1            | DBG 2020-09-27 15:29:54.016+00:00 Launching beacon node                      topics="beacnde" tid=1 file=beacon_node.nim:1195 version="0.5.0 (da3102c0)" bls_backend=BLST cmdParams="@[\"--data-dir=/var/lib/nimbus\", \"--non-interactive\", \"--log-file=/var/lib/nimbus/beacon_node.log\", \"--network=spadina\", \"--web3-url=https://goerli.infura.io/v3/USERID\", \"--graffiti=eth2-docker\", \"--log-level=debug\", \"--metrics\", \"--metrics-port=8008\", \"--metrics-address=0.0.0.0\"]" config="(logLevel: \"debug\", logFile: Some(/var/lib/nimbus/beacon_node.log), eth2Network: Some(\"spadina\"), dataDir: /var/lib/nimbus, validatorsDirFlag: None[InputDir], secretsDirFlag: None[InputDir], walletsDirFlag: None[InputDir], web3Url: \"https://goerli.infura.io/v3/USERID\", depositContractAddress: Some(0x48b597f4b53c21b48ad95c7256b49d1779bd5890), depositContractDeployedAt: Some(\"3384340\"), nonInteractive: true, cmd: noCommand, bootstrapNodes: @[\"# teku (@rolfyone)\", \"enr:-KG4QA-EcFfXQsL2dcneG8vp8HTWLrpwHQ5HhfyIytfpeKOISzROy2kYSsf_v-BZKnIx5XHDjqJ-ttz0hoz6qJA7tasEhGV0aDKQxKgkDQAAAAL__________4JpZIJ2NIJpcIQDFt-UiXNlY3AyNTZrMaECkR4C5DVO_9rB48eHTY4kdyOHsguTEDlvb7Ce0_mvghSDdGNwgiMog3VkcIIjKA\", \"\"], bootstrapNodesFile: , libp2pAddress: 0.0.0.0, tcpPort: 9000, udpPort: 9000, maxPeers: 79, nat: \"any\", validators: ..., stateSnapshot: None[InputFile], stateSnapshotContents: ..., runtimePreset: (GENESIS_FORK_VERSION: 00000002, GENESIS_DELAY: 172800, MIN_GENESIS_ACTIVE_VALIDATOR_COUNT: 1024, MIN_GENESIS_TIME: 1601380800, ETH1_FOLLOW_DISTANCE: 1024), nodeName: \"\", graffiti: Some(eth2-docker), verifyFinalization: false, stopAtEpoch: 0, metricsEnabled: true, metricsAddress: 0.0.0.0, metricsPort: 8008, statusBarEnabled: true, statusBarContents: \"peers: $connected_peers;finalized: $finalized_root:$finalized_epoch;head: $head_root:$head_epoch:$head_epoch_slot;time: $epoch:$epoch_slot ($slot);sync: $sync_status|\", rpcEnabled: false, rpcPort: 9090, rpcAddress: 127.0.0.1, inProcessValidators: true, discv5Enabled: true, dumpEnabled: false)"
beacon_1            | INF 2020-09-27 15:29:54.019+00:00 Starting metrics HTTP server               topics="beacnde" tid=1 file=beacon_node.nim:1217 address=0.0.0.0 port=8008
beacon_1            | DBG 2020-09-27 15:29:55.003+00:00 Message sent to RPC server                 topics="JSONRPC-HTTP-CLIENT" tid=1 file=httpclient.nim:188 address=3.214.190.171:80 msg_len=84
beacon_1            | DBG 2020-09-27 15:29:55.038+00:00 Server returns error                       topics="JSONRPC-HTTP-CLIENT" tid=1 file=httpclient.nim:47 httpcode=400 httpreason="Bad Request" address=3.214.190.171:80
beacon_1            | libbacktrace error: no debugging symbols available. Compile with '--debugger:native'.
beacon_1            | Traceback (most recent call last, using override)
beacon_1            | Error: unhandled exception: Empty response from server [ValueError]
beacon_1            | eth2-spad-devel_beacon_1 exited with code 1
@stefantalpalaru stefantalpalaru transferred this issue from status-im/nimbus-eth1 Sep 28, 2020
@zah zah self-assigned this Oct 20, 2020
@zah zah added this to the November 2020 milestone Nov 10, 2020
@zah
Copy link
Contributor

zah commented Nov 13, 2020

Since the HTTPS endpoints of Infura are not currently supported, we are now automatically rewriting such URLs to their WebSocket counterparts (i.e. wss://). Thus, it's no longer possible to reproduce this issue. The lack of support for HTTP(S) web3 providers will be tracked here:

status-im/nim-web3#18

@zah zah closed this as completed Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants