Or, I could have waited longer for my browser: 504 Gateway Time-out
nginx/0.7.65 Whatever back end system nginx is proxying is not responding. Regards, Tyler On 2012-01-10 14:23, Tyler J. Wagner wrote: > Domain registration, DNS, and routing are all good. The host is responding > to ping on 78.24.191.177, and responding to TCP sockets on 80 and 443. HTTP > requests to port 80 respond with a redirect to "https://openwrt.org/";, > which is bad because the SSL cert has common name "www.openwrt.org". So > that should be fixed. > > Moving on, sending an SSL request to port 443 returns a valid cert signed > by Starfield Secure Certification Authority (themselves signed by > ValiCert). So all that works. > > After that, however, the server does not respond to HTTP requests within > the SSL stream. > > Translation: admin error, or restart nginx. > > Regards, > Tyler > > > On 2012-01-10 13:49, gettons wrote: >> Do you have any idea why the website has been down for the last 2 days ? >> >> >> -- >> Tommaso >> >> >> >> >> >> _______________________________________________ >> openwrt-users mailing list >> [email protected] >> https://lists.openwrt.org/mailman/listinfo/openwrt-users > -- "We must not confuse dissent with disloyalty. We must remember always that accusation is not proof and that conviction depends upon evidence and due process of law. We will not walk in fear, one of another. We will not be driven by fear into an age of unreason, if we dig deep in our history and our doctrine, and remember that we are not descended from fearful men — not from men who feared to write, to speak, to associate and to defend causes that were, for the moment, unpopular." -- Edward R. Murrow _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-users
