Re: [fossil-users] Cannot clone repository over SSL

[Walter Paganini]

2017-07-08 21:36 GMT+02:00 Walter Paganini :

> Thanks for your reply Jan, fortunately I managed to solve the issue by
> myself some minutes ago; but your intuition was right, the issue was linked
> to my nginx configuration. More specifically, this is the clone command I
> was running:
>
> fossil clone https://server-address:8080  ...
>
> My nginx reverse-proxy is configured to forward HTTP requests on the 8080
> port as HTTPS request to the 443 port, which is the correct SSL port.
> However, since I was using the HTTPS protocol for my request on the 8080
> port, nginx couldn't figure out that it had to forward my request to the
> 443 port. If I manually change the port as in the following command,
> everything works fine:
>
> fossil clone https://server-address: 443 ...
>
> It also works correctly if I keep the 8080 port but change the protocol to
> HTTP, as in:
>
> fossil clone http://server-address: 8080 ...
>

Whoops, looks like Gmail inserted some dummy URL I used in my reply and
later renamed. Just for sake of correctness, of course the correct commands
are without that weird  tag.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Cannot clone repository over SSL

[Jan Danielsson]

On 07/08/17 15:34, Walter Paganini wrote:
[---]
> Any idea about what might be causing this issue and how to solve it?

   Not specifically, not without seeing your nginx configuration.
Though I recall having seen someone post a how-to on how to put fossil
behind an nginx, and I believe there's even a page for it on fossil's
wiki.  You could start by comparing that to your configuration.  (That
said, I haven't actually followed that guide; I don't recall if it was
for SSL, and nor do I know if cloning works through it).


-- 
Kind regards,
Jan Danielsson

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Cannot clone repository over SSL

[Walter Paganini]

Hi, it seems like I'm having a problem with a Fossil server that I'm
running on a private remote machine.

The first time I cloned the repository on my local machine, the connection
wasn't encrypted via SSL and so everything went pretty smooth.

At a later stage, I decided to setup an nginx reverse-proxy on the server
to enable SSL encryption: apparently, it worked fine since I'm able to
visit the Fossil web interface with my browser (which warns me that the
certificate is self-signed, as expected, so I know that the connection is
actually an HTTPS one).

>From that moment, I kept on working on my project, perfectly able to
pull/push stuff from and to the remote repository. However, today I asked a
friend of mine to clone the repository on his machine, but his Fossil
client replied with an "unknown protocol" error (I can't type the exact
error since I'm texting from my phone and I won't be able to use a laptop
for some hours, however I will report the exact error message later, if
needed).

Later, I tried to clone the repository on my machine again, and I
experienced the same issue. Although I'm able to pull and push using the
repository that I cloned when the server wasn't SSL-protected (my Fossil
client even asked me to trust the certificate right after I started the
nginx reverse-proxy and tried to push some stuff, so it seems that it
noticed the change), I'm not able to clone it again now that the SSL
encryption is on.

I even tried to build the Fossil client from source to be sure that SSL was
enabled, but that didn't solve my issue, as the freshly built executable
reported the same error when I tried to clone the repository.

Any idea about what might be causing this issue and how to solve it?

Many thanks in advance,
Walter
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users