2017-07-08 21:36 GMT+02:00 Walter Paganini <synthsc...@gmail.com>: > 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 <https://foobar: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: <https://foobar:8080/>443 ... > > It also works correctly if I keep the 8080 port but change the protocol to > HTTP, as in: > > fossil clone http://server-address: <https://foobar:8080/>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 <https://foobar:8080/> tag.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
