Unable to download repositories.json

[Blacktiger]

I don't get any packages listed when I do Package Control: Install Package. In the console, I get the following lines:

Package Control: Error submitting usage information. URL error [Errno 10061] No connection could be made because the target machine actively refused it downloading https://sublime.wbond.net/submit?package_control_version=1.5.0&sublime_platform=windows&package=Package+Control&sublime_version=2210&version=1.5.0&operation=install.
reloading /C/Users/martzm/AppData/Roaming/Sublime Text 2/Packages/User/Package Control.sublime-settings
Package Control: Error downloading channel. URL error [Errno 10061] No connection could be made because the target machine actively refused it downloading https://sublime.wbond.net/repositories.json.
Package Control: Error downloading channel. URL error [Errno 10061] No connection could be made because the target machine actively refused it downloading https://sublime.wbond.net/repositories.json.
Package Control: No updated packages

• If I manually go to repositories.json in the browser I do get what looks like a valid response.
• My company uses a proxy server.
• I also tried the test build of package control from here but I saw the same console output.

[atinypixel]

I have this same issue.

[schell]

I also have this issue.

[schell]

I was running an HTTP proxy (Charles) that was freaking out Package Control. It had something to do with SSL. I turned off the proxy (after reinstalling a bunch =P) and everything seems to work fine now.

[mannyishere]

I have the same issue.

[schlamar]

@atinypixel @schell @mannyishere Have you all tried the testing version?

@Blacktiger Have you configured your proxy in Package Control settings?

@wbond IMO it is time to make the testing version an official release.

[atinypixel]

I don't have access to proxy settings info. IT does want employees knowing that stuff.

On Jul 6, 2012, at 1:13 AM, Marc Schlaichreply@reply.github.com wrote:

@atinypixel @schell @mannyishere Have you all tried the testing version?

@Blacktiger Have you configured your proxy in Package Control settings?

@wbond IMO it is time to make the testing version an official release.

---

Reply to this email directly or view it on GitHub: https://github.com/wbond/sublime_package_control/issues/151#issuecomment-6797994

[wbond]

I've posted a new version of Package Control (1.5.0.11) just today at https://sublime.wbond.net/testing/Package%20Control.sublime-package. Please:

1. In Sublime Text, click the Preferences > Browse Packages… menu entry
2. Browse up a folder and then into the Installed Packages folder
3. Download http://sublime.wbond.net/testing/Package%20Control.sublime-package and copy it into the Installed Packages directory
4. Restart Sublime Text

Also note that in the new version, there are separate settings for proxy_username and proxy_password which you may need to set.

This new version adds support for basic, digest and ntlm auth for proxies. Unfortunately I don't have any of these to test against, but I am hoping it will help with your issue, and you can report any issues back.

[Blacktiger]

I downloaded the new testing package. I've attempted to configure the proxy server, but I have no idea what I am doing and we use automatic proxy settings on Windows in my environment. I did find out an alternative proxy server that uses port 9119 but I'm not sure if I configured that correctly.

[schlamar]

@Blacktiger find your proxy settings in Windows under Control -> Internet settings -> Connections -> LAN settings

[Blacktiger]

Automatic is checked there, so that doesn't really help.

[wbond]

Well, according to the python documentation, to use the automatic proxy settings, just don't enter any proxy info. To accomplish this with Package Control, just don't set the http_proxy or https_proxy settings.

[schlamar]

@wbond I am not sure at this point. The documentation states that urllib2 is able to get the proxy settings automatically from the registry. But this does not imply that it can deal with automatic proxy discovery...

[wbond]

Alright, well, unfortunately trying to integrate something like pacparser is too much work right now. I need to get the current staged version out to fix a bunch of bugs that have been present for a while.

As long as I don't hear of any bugs affecting users who have gotten it successfully running on some version in the past, I am planning on launching version 1.5.0.12 later tonight, or some time this weekend.

[mannyishere]

I am using CNTLM. Using the testing version works after changing proxy settings in Package Control. The latest prod version doesn't work.

[schlamar]

@atinypixel If you don't have automatic proxy discovery it should work anyway.

[Blacktiger]

Going to http://proxy seems to have given me the script that my company uses for automatic proxy. I think that I'm using "iprism.mycompany.com:3128" for the proxy host. I tried manually configuring with that host/port combo but no matter what I do I get a 407 Proxy Authentication Required.

[wbond]

@Blacktiger Well, looking at the iPrism documentation, it seems it could use a whole bunch of different auth methods. Can you try setting the proxy_username and proxy_password settings (in Package Control > Settings - User) to your Windows login and password? I'd be curious if you could just try at least once to see if that is what is required.

[Blacktiger]

Ok, I was finally able to get it to work. I needed to put http:// in front of the proxy. My settings look like this for anyone else having this problem:

"http_proxy": "http://iprism.mycompany.com:3128", "proxy_username": "username", // (windows username) "proxy_password": "password", // (windows password)

[brandondrew]

@Blacktiger : you're hitting CNTLM, but still passing your Windows login info? Is that a mistake or did you really need to do that to make it work?

[Blacktiger]

I really needed to do that to get it to work. I am no longer using that configuration though. We have an alternative proxy at my company that doesn't require a username/password so I'm using that now and with the latest version of package control it works for me.