Thanks for that tip. Examining the logs; - nothing in trac.log (at least, not anything when trying to open the url after it times out and gives a 500 internal server error) - Apache's error.log:
[Tue Oct 23 07:26:59 2007] [error] [client 84.53.73.194] FastCGI: comm with (dynamic) server "/home/twcore/twcore.org/index.fcgi" aborted: (first read) idle timeout (60 sec) [Tue Oct 23 07:26:59 2007] [error] [client 84.53.73.194] FastCGI: incomplete headers (0 bytes) received from server "/home/twcore/ twcore.org/index.fcgi" It's a long shot because this seems to be a very general error but do you know what this means or where I can look for a solution? If I monitor the server when opening the URL I don't even see a python process getting started to execute index.fcgi (which it did before). Is this something with Trac or apache? Regards, Koen Werdler On Oct 23, 11:39 am, Jani Tiainen <[EMAIL PROTECTED]> wrote: > werdlerk kirjoitti: > > > > > Hey, > > > I tried getting a SSL Certificate (self-signed) running with my Trac- > > website. This didn't work (for whatever reason) so I removed it. Now > > unfortunately my website is down. (The browser just keeps waiting for > > a response from the server and finally times out with a server error.) > > > When running ./index.fcgi from the prompt, the following errors are > > put before the normal html page: > > > drpepper: 01:48 PM$ ./index.fcgi > > WSGIServer: missing FastCGI param REQUEST_METHOD required by WSGI! > > WSGIServer: missing FastCGI param SERVER_NAME required by WSGI! > > WSGIServer: missing FastCGI param SERVER_PORT required by WSGI! > > WSGIServer: missing FastCGI param SERVER_PROTOCOL required by WSGI! > > Status: 200 Ok > > Cache-control: must-revalidate > > Expires: Fri, 01 Jan 1999 00:00:00 GMT > > Content-Type: text/html;charset=utf-8 > > Content-Length: 16681 > > [...] > > > In the source code it says these errors show that the server is > > broken. Do you know how this can be fixed? > > The URL to the website ishttp://www.twcore.org. > > You can't run fastcgi frontend from commandline. It expects to have > standard CGI parameters that are passed by webserver so there is no > point to run it from command line. > > So you need to figure out working setup for your server (apparently you > broke something when testing). Logs are friends. > > -- > > Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
