-
Notifications
You must be signed in to change notification settings - Fork 70
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
Unable to issue OpenCerts (Ledger - Production) #588
Comments
Thanks, will investigate this |
Hi, can we check if there is any update? Can our user proceed to issue the OpenCerts? |
Hi yvonneyong, I investigated and it looks like Ledger Nano support is a bit patchy with our site, and also if your wallet firmware is outdated it might cause issues as well. Fortunately there is an alternative Metamask workflow now that was not originally supported back when we developed admin-website. Metamask can also act as a proxy to interact with the Ledger Nano, simply use "Add Hardware Wallet" inside Metamask to add your Ledger Nano. You may follow the instructions here or here to connect your Ledger Nano to Metamask. After adding the Ledger Nano to Metamask, you can follow the below to issue a certificate:
|
The user initially had difficulties but managed to connect after a few tries, but encountered further errors. |
Are we the only ones encountering this issue? |
we haven't received any other reports, just to check - do you have contract data set to "YES" in the Ethereum app settings on the ledger nano itself? |
After setting contract data was set to Yes, the OpenCerts issuing worked. |
We were unable to issue OpenCerts on the Ledger site yesterday, after several attempts throughout the day.
Attached the screenshot, and errors.
inpage.js:1 MetaMask: We will stop injecting web3 in Q4 2020.
Please see this article for more information: https://medium.com/metamask/no-longer-injecting-web3-js-4a899ad6e59e
get @ inpage.js:1
inpage.js:1 MetaMask: MetaMask will soon stop reloading pages on network change.
For more information, see: https://docs.metamask.io/guide/ethereum-provider.html#ethereum-autorefreshonnetworkchange
Set 'ethereum.autoRefreshOnNetworkChange' to 'false' to silence this warning.
(anonymous) @ inpage.js:1
The resource was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate
as
value and it is preloaded intentionally.The resource was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate
as
value and it is preloaded intentionally.The resource was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate
as
value and it is preloaded intentionally.The resource was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate
as
value and it is preloaded intentionally.The resource was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate
as
value and it is preloaded intentionally.popover-index.html:27 Blocked autofocusing on a
DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/disable-console.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/contentscript.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/inpage.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
The text was updated successfully, but these errors were encountered: