I cannot help you directly, but I just wanted to say that at my workplace, we are also behind a proxy, and I did not have to reconfigure Racket in any way. I also have to put in the "insteadOf" rule for git clones, as only HTTPS traffic is allowed, but I believe the Racket package manager just runs git as a subprocess: package installation from github.com repositories works fine.
Also, the error you are getting from `tcp-connect` is related to port 433 which is HTTPS, so your "insteadOf" rule seems to work. Maybe your workplace blocks all access to github.com? Alex. On Tuesday, December 11, 2018 at 3:21:30 AM UTC+8, making-a-racket wrote: > > Does anyone have any input on this? This is an important hurdle for my, > hopefully eventual, use of Racket at work, and I imagine it is important to > other industrial users as well. > > I have confirmed that it is indeed my work's proxy/firewall that is > blocking Racket's package manager. For now, I have been able to get > security exceptions made for the following Racket URLs: > > - https://download.racket-lang.org > - https://mirror.racket-lang.org > - https://pkgs.racket-lang.org > - https://planet-compats.racket-lang.org > > This is working better, but now the package manager is getting stuck at > downloading the repository from github.com. For example, when trying to > install "beautiful-racket", I get here: > > Resolving "beautiful-racket" via > https://download.racket-lang.org/releases/7.0/catalog/ > Resolving "beautiful-racket" via https://pkgs.racket-lang.org > Downloading repository git:// > github.com/mbutterick/beautiful-racket/?path=beautiful-racket > tcp-connect: connection failed > address: github.com > port number: 443 > system error: A connection attempt failed because the connected party > did not properly respond after a period of time, or established connection > failed because connected host has failed to respond.; errid=10060 > > The error message is not good and differs on different machines, but I am > suspecting the failure is due to using git:// instead of https://. The > former won't be allowed through the proxy/firewall, but the latter would > be. For git, you can configure git to use https:// rather than git@ or > git://. Does anyone know if Racket is hard-coded to use git://? Is there > any configuration file I can edit to change the method used? For example, > in git, you can do: > > git config --global url."https://".insteadOf git:// > > I am guessing the underlying mechanism is using the net/git-checkout > library (https://docs.racket-lang.org/net/git-checkout.html)? Is there a > local install of git in the Racket install location where I could provide a > configuration for? Can I change the package manager code to use https:// > instead? > > Also, if anyone has any pointers to how to add proxy support and fix the > git URL long term and for all users, I would be happy to try and see if I > could make the changes myself to submit back to Racket. > > Thanks. > > On Thursday, September 13, 2018 at 1:59:43 PM UTC-4, making-a-racket wrote: >> >> Hello, >> >> I would love to experiment with and potentially use Racket at work, but I >> am currently unable to use the package manager (raco) behind a proxy. >> >> >> 1. Is there any advice for configuring the Racket ecosystem for being >> used behind a proxy? >> 2. Does Racket respect the "http_proxy", "https_proxy", and >> "no_proxy" environment variables? >> 3. What do the proxy settings in the Browser preferences tab do? >> >> I know that you can manually download and install packages, but I would >> prefer not having to do that. It seems at some point Racket's package >> manager explicitly did not support working behind proxies ( >> https://lists.racket-lang.org/users/archive/2014-April/061965.html), but >> I am not for sure if that is still the case. >> >> >> Thank you for any help! >> > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
