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
