Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Error on extension installation. #6188

Closed
mahdiar opened this issue Dec 5, 2013 · 7 comments
Closed

Error on extension installation. #6188

mahdiar opened this issue Dec 5, 2013 · 7 comments
Assignees

Comments

@mahdiar
Copy link

mahdiar commented Dec 5, 2013

Hi
When I click to inastall any extension it sgows the following error :
cannot connect to server error

@njx
Copy link
Contributor

njx commented Dec 6, 2013

@mahdiar - is it possible that you have a firewall that blocks outgoing HTTP access from certain programs? (It's odd that you would see the list of available extensions but not be able to install one, though.)

One thing that would help us diagnose this is if you choose Debug > Show Developer Tools, then try to install an extension. Then, in Chrome (where the developer tools appear), see if there are any errors (lines in red) in the Console tab.

@ghost ghost assigned dangoor Dec 6, 2013
@njx
Copy link
Contributor

njx commented Dec 6, 2013

Medium priority to @dangoor to follow up.

@marcelgerber
Copy link
Contributor

@mahdiar Do you use a proxy? As far as I know, there was an issue some time ago where this error appeared while a proxy was used.

@busykai
Copy link
Contributor

busykai commented Dec 10, 2013

I'm behind a proxy and I'm seeing this situation as well. I believe what happens is CEF picks up system proxy configuration, but since the installation process itself happens on node, it fails due to the proxy.

@mahdiar
Copy link
Author

mahdiar commented Dec 18, 2013

I check the console tab and there is the error :
[Extension] Error -- could not read native directory: /home/mahdiar/.config/Brackets/extensions/user ExtensionLoader.js:261
(anonymous function)

@dangoor
Copy link
Contributor

dangoor commented Dec 19, 2013

@mahdiar Can you check that that directory exists? Are the permissions set reasonably?

@dangoor
Copy link
Contributor

dangoor commented Mar 17, 2014

I believe this is a dupe of #6280 which I believe has just been fixed.

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

No branches or pull requests

5 participants