You might want to ssh out and check if that is allowed. If you can ssh out,
you should be able to clone from bitbucket ssh too [ Though you might not
be able to push, depending on whether or not you own the repository]
On 18 June 2013 19:59, Saket Choudhary <sake...@gmail.com> wrote:
> Hi Sebastian,
> I work behind a proxy too(In my case I have to supply a username and
> password too )
> I have the following thins setup in my ~/.bashrc:
> export http_proxy= http://username:password@proxy-url:proxy-port/
> then source it:
> $ source ~/.bashrc
> or maybe relogin .
> and the .hgrc settings that you have specified usually work for me
> Here are few links that I remember using . I am no longer behind a proxy ,
> so would not be able to verify this now, Though I remember pushing and
> pulling from behind proxy using the above settings
> On 18 June 2013 19:48, Sebastian Schaaf <sch...@ibe.med.uni-muenchen.de>wrote:
>> Hi all,
>> I'm currently trying to set up a galaxy-dist instance on a SLES server
>> within an 'encapsulated' network (hospital environment; here all sensitive
>> data is stored and handled). Within this network, clients are only capable
>> of accessing the internet via HTTP/HTTPS and FTP, using a proxy - adress
>> and port (8080) are the same for all three protocols.
>> Mercurial (which I had to set up in advance) is accessible and more or
>> less in default configuration (more on that down below).
>> What I get after executing the command 'hg clone
>> "abort: error: _ssl.c:491: error:140700FC:SSL routines:SSL23_GET_SERVER_*
>> *HELLO:unknown protocol"
>> Google search indicates something more general, so outside the exclusive
>> scope of Galaxy. On top, no connection to Galaxy was listed, also not in
>> this mailing list's archive.
>> Following some hints I just tried to set the proxy via a '.hgrc' file in
>> the galaxy user home like this:
>> host = url:port
>> host = url:port
>> (re-login after that) and also set the system variables '$http_proxy' and
>> '$https_proxy'. Another approach described was to call
>> 'hg --config http_proxy.host=url:port clone https://bitbucket.org/galaxy/
>> **galaxy-dist#stable <https://bitbucket.org/galaxy/galaxy-dist#stable>'
>> Nothing worked out.
>> Does anyone experienced similar behaviour or has got some ideas how to
>> solve this?
>> Thanks in advance,
>> Sebastian Schaaf, M.Sc. Bioinformatics
>> University of Munich
>> Please keep all replies on the list by using "reply all"
>> in your mail client. To manage your subscriptions to this
>> and other Galaxy lists, please use the interface at:
>> To search Galaxy mailing lists use the unified search at:
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: