etherflow icon indicating copy to clipboard operation
etherflow copied to clipboard
Published 2 years ago • verified publisher icon abunsen

Connecting over HTTP broken (The issue formerly known as: Connecting with IP & Port nodes)

Open Getty4170 opened this issue 5 years ago • 3 comments

Etherflow doesn't accept connections when including a port. For example http://172.16.254.1:8545/

Since many nodes are used in this format, it would be great if EtherFlow supported it.

Getty4170 avatar Nov 17 '20 22:11 Getty4170

@Getty4170 appreciate this submission! Will tag you in the PR.

abunsen avatar Nov 20 '20 14:11 abunsen

Just looked at this more, it looks like it's actually mixed content error and we are actually sending to the port: Screen Shot 2020-11-20 at 9 28 58 AM

abunsen avatar Nov 20 '20 14:11 abunsen

If anyone else is facing the mix-content error, then there are 2 ways by which you could solve this issue.

  1. Use a local version of etherflow by deploying the repository on your local computer.
  2. Use services like ngrok.io or Cloudflare Tunnel to get a kind of HTTPS proxy for your HTTP nodes.

The second option here is easier to set up and could be quickly implemented.

Cause of this issue

  • On a HTTPS website, you cannot make calls to HTTP endpoints

Why would the above options work?

  • In 1st option, you are taking off the etherflow from HTTPS to HTTP version
  • In 2nd option, you are moving in the Blockchain Node from HTTP to HTTPS version

ashutoshpw avatar Aug 23 '22 10:08 ashutoshpw