Metamask-extension: https://eos.io/distribution/ doesn't load

[btsfav]

The latest update broke this page. won't load properly now

[tmashuang]

How so?

[btsfav]

@tmashuang oh sorry, there's no direct link.

click "get eos"

then

this brings you to the metamask friendly crowdsale page. latest MM update broke it, it does not load properly now

[danfinlay]

I click "Get EOS", but it asks me to check a lot of boxes that I don't want to legally be liable for checking, as a U.S. resident, who hasn't read their white paper, purchase agreement, or terms of service.

Could you maybe check the logs, and look for errors that could be thrown here?
https://github.com/MetaMask/faq/blob/master/LOGS.md

I suspect the network tab under the background logs may be the place to look.

[stevek-pro]

This page does not load for me either. I need to disable the plugin several times and hit reload about 30-40 times and wait approx. 1-2 hours then the page show up.

[lightrush]

Here's a log form the background: https://gist.github.com/lightrush/1c660623e681728b9c4c577f49aec4fc

[sprihodko]

Same for me
Showing this error message

Error: SyntaxError: Unexpected end of JSON input
    at Object.InvalidResponse (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/scripts/inpage.js:8237:28386)
    at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/scripts/inpage.js:8238:28122
    at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/scripts/inpage.js:168:7
    at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/scripts/inpage.js:8214:5
    at nrWrapper (https://eos.io/js/monitoring.js:1:11483)

[lightrush]

I'm not sure if this is MetaMask's fault or is some API it's talking to being uncooperative?

[Avelaskes]

Same problem!!!! what to do?

[gazarian]

anyone figure this out ?

[tmashuang]

some users have been having luck with running a local node on through their console. https://github.com/metamask/faq/blob/master/USERS.md#using-a-local-node

[Cu4rach4]

i guess is a problem with latency...or a problem on gateway...

background.js:65853 POST https://mainnet.infura.io/metamask 502 ()
RpcSource.handleRequest @ background.js:65853
next @ background.js:58483
HookedWalletSubprovider.handleRequest @ background.js:66600
next @ background.js:58483
handleRequest @ background.js:66887
next @ background.js:58483
FilterSubprovider.handleRequest @ background.js:65981
next @ background.js:58483
(anonymous) @ background.js:65631
BlockCacheStrategy.hitCheck @ background.js:65753
BlockCacheProvider._handleRequest @ background.js:65629
(anonymous) @ background.js:65593

[tmashuang]

https://consensyssupport.happyfox.com/kb/article/11-infura-connectivity-issues

[danfinlay]

Confirmed this is a problem with our Infura connection, they simply need to scale up a bit for all this new token sale traffic. In the meanwhile, the link Thomas shared contains the relevant workarounds for this issue.

https://consensyssupport.happyfox.com/kb/article/11-infura-connectivity-issues