CODEWITHSUNDEEP
socketscommon-lispquicklisp
automaton
automaton

Reputation: 1121

Connection refused error installing quicklisp

On evaluating (quicklisp-quickstart:install) in SBCL I get(linux):

debugger invoked on a SB-BSD-SOCKETS:CONNECTION-REFUSED-ERROR in thread
#<THREAD "main thread" RUNNING {1002978FF3}>:
  Socket error in "connect": ECONNREFUSED (Connection refused)

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT] Exit debugger, returning to top level.

(SB-BSD-SOCKETS:SOCKET-ERROR "connect")

and in CMUCL I get:

Error in function CONNECT-TO-INET-SOCKET: Error connecting socket to [beta.quicklisp.org:80]: Connection refused [Condition of type SOCKET-ERROR]

Restarts: 0: [ABORT] Return to Top-Level.

Debug (type H for help)

(CONNECT-TO-INET-SOCKET "beta.quicklisp.org" 80 :STREAM :LOCAL-HOST ...)

Upvotes: 3

Views: 847

Answers (1)

Xach
Xach

Reputation: 11819

This can happen if there is a proxy involved. Many system programs (like wget, web browsers, etc) will look at environment variables or other configurations to automatically use the proxy properly, but Quicklisp must be told about it explicitly.

You might see proxy settings in your environment variables.

If you know your proxy URL, you can set it during installation with the :proxy option to install.

Upvotes: 1

Related Questions