Yes, still working the kinks out. (Specifically, debugging the interaction between nginx and cgit via slowcgi) On Sat, 18 Jan 2014, Ben Lindstrom wrote: > > And FYI.. From my work (US - ATT) and my home (US - VISI) both come back with 504 Bad Gateway as well. > > - Ben > > On Jan 18, 2014, at 8:18 AM, mancha <mancha1 at hush.com> wrote: > > > Loganaden Velvindron <loganaden <at> gmail.com> writes: > >> On Sat, Jan 18, 2014 at 1:23 PM, Darren Tucker <dtucker <at> zip.com.au> > > wrote: > >>> On Sat, Jan 18, 2014 at 7:19 PM, mancha <mancha1 <at> hush.com> wrote: > >>>> Also getting "504 Gateway Time-out" here. Problem likely lies > >>>> server-side. > >>> > >>> Interesting. Actually poking the http and https services shows the > >>> same problem for me. In summary: > >>> > >>> ping works. > >>> telnet anongit.mindrot.org on port 80 and 443 accept connections > >>> git clone works > >>> http and https on anongit.mindrot.org connect but return "504 Gateway > >>> Time-out" from nginx. > >> > >> It was working quite well some time ago. However, it's no longer the > >> case right now > > > > Though it still doesn't work for me, the error has changed from > > "504 Gateway Time-out" to "502 Bad Gateway". Maybe this information > > helps debug things. > > > > _______________________________________________ > > openssh-unix-dev mailing list > > openssh-unix-dev at mindrot.org > > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev > > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev at mindrot.org > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev >
