I had the myetherwallet chrome extension on 2 different computers (1 laptop, 1 desktop, both logged into chrome with the same google account.
I had 5 wallets on my laptop that I couldn't see on the desktop even though I was using the same google account.
I accidentally pressed the sync button feature in google extension setting from the desktop and now I can't see the wallets from my laptop, they are gone.
I never recorded the private key's for these private wallets.
Do you know of a way to rollback Chrome extension history or otherwise recover the wallet data? I am on Mac, will a system rollback restore the local profile Chrome data?
Please help if you can.
Related
After yet another reboot of my macbook, chrome stopped loading my webapp.
It returns literally nothing in browser window and the only thing i managed to find is that requests in chrome's timeline has status "cancelled".
If I'm trying to get there from another website (by changin url and hitting "return" button), it also does nothing, it doesn't even try to reload page.
Other browsers load it fine atm.
I've received this report from a user about couple of weeks ago, but now i've got it myself, so I assume the problem is in my server.
Recently, i've found that my android phone also can't access the website from chrome browser. The behaviour is the same. However, android default browser has access.
What could that be? Where should i look?
I'd provide more information, but there is no error codes or messages of any kind, so i have no idea what information could help in this question.
Also, i have a chrom browser extension (similar to Pocket), which also is unable to access server. The notable difference is that extension uses Socket.io only.
There were no recent code changes on server side except letsencrypt certificate renewal.
I've tried this:
server restart
different ip/locations (vpn and public access points)
chrome data cleanup / chrome version degrade / chrome reinstallation / chrome canary installation
tried to open server address directly - no difference
I am working on a desktop app using Google Drive SDK through OAuth2 authentication, and would like to share Google Drive files from my desktop app. I have studied the "Share" feature in Google's official Google Drive desktop version, and found that it just simply loads the following url in an embedded webbrowser: https://drive.google.com/sharing/share?shareUiType=default&authuser=0&foreignService=googledrivesync&access_token=(Oauth2AccessToken)&subapp=10&shareProtocolVersion=2&gaiaService=wise&theme=2&client=desktop&command=settings&hl=en_US&popupWindowsEnabled=false&id=(theFileId) .
After loading the url, the sharing web page will show up in the embedded IE browser. In Google Drive, no matter you have signed in Google or not in IE, the share function always works.
I employed the same url in my embedded webbrowser, and the sharing page shows up just as expected, but the actually sharing function only works when your have signed in Google in IE already. If your account is not in a Google signed-in status in IE, the sharing will not succeed. There is no problem for displaying the sharing page, but error message "The server encountered an error. Please try again later." will be given when "Share" button is clicked.
I have spent several days on this problem, using Fiddler to monitor the HTTP package, trying Firefox and Chrome instead of IE, modifing different setting in Google developer console... but still have no clue how Google Drive can successfully share files in its embedded IE browser without having to sign in first.
NOTE: this is not an IE problem, same problem happends in Firefox and Chrome too.
Any tip or trick is appreciated.
I have noticed on some computers with google chrome, the option to allow access to the users media device (webcam or microphone) is not enabled. However I am speaking more to getting chrome to even prompt the user to 'allow'. Personally, my chrome Version 42.0.2311.90 (64-bit) works great. However, I have encountered others unable to even see the popup box to allow/block.
This is what shows:
However, on those computers in question, even after setting this option to 'ask for access', the browser when the page is refreshed does not record this option and just returns to the option to 'continue blocking'. Even inside of he advanced privacy settings, the option to ask for access is selected. Is there a security setting in the browser that needs to be set?
We have a Chrome Extension application that we have developed and would like to distribute it only a limited number of internal users.
This would be a private app, but to install it, users now have to follow the manual steps of going to Settings -> Extensions -> clicking on Developer mode -> drop the .crx in there.
I would like to know if there is a way to just have private App Store to privately distribute this app and not have it on Chrome Web Store for anyone to see/download/use.
Thanks for your help in advance ---
You use the Chrome Web Store. 2 options are available:
Share an unlisted Chrome extension from the Chrome Web Store (anyone with the link will be able to install it)
Chrome customers using G Suite or Education can use the Chrome Web Store to host private apps restricted only to their users on the same domain.
See https://support.google.com/chrome/a/answer/2663860
Update 2016-05-20: From https://support.google.com/chrome/a/answer/2663860?hl=en
Chrome customers using Google Apps for Work or Education can use the Chrome Web Store to host private apps restricted only to their users or people who you share a direct link to the app with. Users from the same Chrome domain will see their organization's private apps in a private collection in the Chrome Web Store.
Update 2015-10-27: Google has updated installation policies in attempt to curb malicious extension activity on Windows. On the chrome extension hosting page:
Warning: As of Chrome 33, Windows users can only download extensions
hosted in the Chrome Web store, except for installs via enterprise
policy or developer mode (see Protecting Windows users from malicious
extensions). As of Chrome 44, no external installs are allowed from a
path to a local .crx on Mac (see Continuing to protect Chrome users
from malicious extensions).
With the latest versions of Google Chrome, users are no longer going to be able to just click a download link and have it install with the correct HTTP headers. This leaves you with 4 possible options:
user downloads extension and then drags the file into the extension management page (This no longer works on Windows per update note)
change registry settings on users computers
user downloads extension source folder and loads extension from source in the extension management page
Re-enable extension installs with command-line flag as suggested by Rob W
I have created and distributed several different Google Chrome extensions privately within my company and went with the first option. It is an extra step for the users but it wasn't a big deal. The users did not have to have developer mode enabled in their Chrome browser for this to work.
Yes, you can. You need to create the crx file through the google chrome "Extensions" page (visit: chrome://extensions/ NOTE: You cannot click the link you have to manually copy and paste it, chrome does not allow you to visit the link from href)
On the Extensions page, check the box "developer mode", choose "pack extension".
Now you get the following popup. Click "browse" for the Extension root directory and navigate to the folder containing your extension (the folder containing manifest.json).
The first time you do this, ignore private key file. It will generate one for you automatically and save it to the same folder.
When you release a new version of the extension, use the generated private key file. This way for someone to update the extension, it won't ask for permissions again.
TO INSTALL
To install the extension, just get each user to manually drag the newly created extension crx into the Extensions page (chrome://extensions/).
The first time it will ask for permissions just like when installing from the Chrome Web Store.
For each new version, as long as you used the same private key file for each new version, users just drag the new version into the Extensions page the same way except they won't be asked for permissions again. It will just update the extension.
WARNINGS:
Beware the way you distribute the extension crx file. When user downloads the extension .crx file in Google Chrome, it will think you're trying to install the extension from that page, and come up a warning "couldn't be installed from this site". You need to make sure that users know to ignore the error, and check their downloads folder for the extension to manually install it.
Whenever you download the .crx file, Chrome will give the user a warning saying it might contain a virus. There is no way around this. Even if you zip up the file, Chrome will read the contents and give the same warning. Some users won't install because of this. A workaround is to rename the .crx to something else, like .RENAME_TO_CRX, but this is a hassle and a lot of users either won't want to or won't be able to figure it out.
You can't update the extension automatically. It's just not possible because Chrome manually blocked this capability.
NOTE: Another way would be to release it on the Chrome Store, but only for certain users (not public). Only people with the link could install, OR you could make it only certain people can install and even if you had the link but weren't part of the group, they couldn't view the extension. Only problem here is if you don't want Google to see the extension.
If you use Google Apps, it appears there's now a way to publish apps and extensions to the Chrome Web Store, but only make it visible to users of that domain.
https://support.google.com/chrome/a/answer/2663860?hl=en
Since its internal, could you change registry settings on their computers?
Because if so, you can use them to allow easy install of extensions from outside the web store or force install extensions on their machine.
Look here....
http://www.chromium.org/administrators/policy-templates
http://www.chromium.org/administrators/policy-list-3#ExtensionInstallSources
http://www.chromium.org/administrators/policy-list-3#ExtensionInstallForcelist
I am desining a Chrome, FF and Safari extension. I wnt someone to be able to let spmeone install the plugin on no more than 5 computers. So, basically one account on my site can 'authorise' up to 5 computers. And deauthorise them as well. Are there any ways to do this?
Thanks
First off, I don't think you can identify/authenticate at the computer level. But what you can do is identify/authenticate at the browser level. Just use the browser's local storage to:
Generate a unique ID at the first launch
Tie it to an account manager online
Store the ID locally
Use the tied ID for further uses of your extension
It can be hackable, but it requires to go edit the browser's local storage manually. 99.95% of your users won't be able to do that.
Also, I think you would have to inform the user properly about this.