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

Custom RPC URL fails with uppercase HTTP #4253

Closed
epeschier opened this issue May 14, 2018 · 9 comments
Closed

Custom RPC URL fails with uppercase HTTP #4253

epeschier opened this issue May 14, 2018 · 9 comments
Labels

Comments

@epeschier
Copy link

epeschier commented May 14, 2018

Bounty: MetaMask should connect to Ganache (or any custom RPC) reliably whether the user inputs HTTP or http.


I found this bug while testing on a private network with Ganache.
If you start Ganache and copy-paste the RPC Server address "HTTP://127.0.0.1:7545" (note the uppercase HTTP) then you will get a balance of 0 in Metamask for the accounts.
Change the server address to lowercase http://127.0.0.1:7545 then it works.

@CaliosD
Copy link

CaliosD commented May 19, 2018

I've met the same problem, too. It's really interesting...=_=

@flexsurfer
Copy link

flexsurfer commented May 20, 2018

in 4.6.1 it's just connecting infinitely, and after restart MM is dead, it opens white popup, restart doesn't help , and no errors in logs :(

@bdresser
Copy link
Contributor

Connecting to HTTP://127.0.0.1:7454 also displays my mainnet balance even though I'm on a custom RPC option.

@bdresser
Copy link
Contributor

Seems like the UI updates to "Custom RPC" while actually staying on Mainnet

@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


This issue now has a funding of 0.085 ETH (42.5 USD @ $500.05/ETH) attached to it.

@gitcoinbot
Copy link

@bakaoh Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • warning (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@gitcoinbot
Copy link

gitcoinbot commented Jul 23, 2018

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


Work has been started.

These users each claimed they can complete the work by 4 months, 1 week from now.
Please review their action plans below:

1) pinkiebell has started work.

Working on it. Will turnaround today

Learn more on the Gitcoin Issue Details page.

@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


Work for 0.085 ETH (39.27 USD @ $461.95/ETH) has been submitted by:

  1. @pinkiebell

@bdresser please take a look at the submitted work:


@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


The funding of 0.085 ETH (39.91 USD @ $469.53/ETH) attached to this issue has been approved & issued to @pinkiebell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants