Ah, I misunderstood.
On 02 Jul 2013, at 01:16, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
> Sorry, I express myself wrong. Indeed, from the server side (the image running shub), I do not use Zodiac at all. But in another image (where I am having the problem), if I try to connect to the Monticello repository (served by HTTPS by nginx in the other server) I do have the problem and in this case I am trying to communicate via HTTPS from Pharo. Wouldn't be using Zodiac here?
Yes, to access an HTTPS based repository, you need Zodiac.
If all Zn+Zdc tests are green, that means you are good.
I see that you get a ConnectionTimedOut error while connecting, that's like the very first step ;-)
What I would do is: make sure you can access your HTTPS repo in other ways, using a regular browser and/or curl. You know, MC repo serving is just plain HTTP(S) with basic authentication: you should be able to list a repo or download a version using any other means.
If that works, try to do the same using ZnClient, like this:
ZnClient new
� � � � username: 'marianopech' password: 'secret';
� � � � get: 'http://www.smalltalkhub.com/mc/SvenVanCaekenberghe/STON/main/Ston-Core-SvenVanCaekenberghe.35.mcz'.
Good luck !
Sven
PS: I also see you are using a numeric IP address, not a DNS name. That won't work with virtual hosts AFAIK.
--
Sven Van Caekenberghe
Proudly supporting Pharo
http://pharo.org
http://association.pharo.org
http://consortium.pharo.org