that's a funny error, not really but there many different opinions on what can fix it just search google.
but i think it's due to timeout since it looks like you are on a Raspberry PI, try setting timeout HIGH http://httpd.apache.org/docs/current/mod/mod_proxy.html#proxytimeout also while your are testing change "x-webobjects-server-name" and "x-webobjects-server-url" in your apache config to use the ip address of your box just be sure. if nothing works try open port "20000" on your box and connect directly, or use lynx or similar text based browser to try localhost:20000 Regards Christian On Saturday, May 2, 2015 13:55 CEST, "Tobias Lindinger" <tobias.lindin...@web.de> wrote: > Hi, > > I have similar problems when trying to login into the web interface. An > internal error ("An unhandled error occurred.") is displayed in the browser. > The only log containing any error messages is apache error log which says: > > [Sat May 02 06:25:15.595138 2015] [mpm_prefork:notice] [pid 5864] AH00163: > Apache/2.4.10 (Raspbian) configured -- resuming normal operations > [Sat May 02 06:25:15.595423 2015] [core:notice] [pid 5864] AH00094: Command > line: '/usr/sbin/apache2' > [Sat May 02 13:49:10.628558 2015] [proxy_http:error] [pid 18399] > (20014)Internal error: [client 192.168.2.212:54232] AH01102: error reading > status line from remote server 127.0.0.1:20000, referer: > http://192.168.2.184/SOGo/ > > My Apache config is like the following: > > Alias /SOGo.woa/WebServerResources/ > /usr/lib/GNUstep/SOGo/WebServerResources/ > Alias /SOGo/WebServerResources/ > /usr/lib/GNUstep/SOGo/WebServerResources/ > <Directory /usr/lib/GNUstep/SOGo/> > > <IfVersion < 2.4> > Order deny,allow > Allow from all > </IfVersion> > <IfVersion >= 2.4> > Require all granted > </IfVersion> > > # Explicitly allow caching of static content to avoid browser specific > behavior. > # A resource's URL MUST change in order to have the client load the new > version. > <IfModule expires_module> > ExpiresActive On > ExpiresDefault "access plus 1 year" > </IfModule> > </Directory> > > ProxyRequests Off > SetEnv proxy-nokeepalive 1 > SetEnv force-proxy-request-1.0 1 > SetEnv proxy-initial-not-pooled 1 > ProxyPreserveHost On > #AllowCONNECT 20000 > ProxyPass /SOGo http://127.0.0.1:20000/SOGo retry=0 > #ProxyPassReverse /SOGo http://127.0.0.1:20000/SOGo retry=0 > ProxyPass /Microsoft-Server-ActiveSync > http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync retry=0 > connectiontimeout=5 timeout=3600 > > <Proxy http://127.0.0.1:20000/SOGo> > RequestHeader set "x-webobjects-server-port" "80" > RequestHeader set "x-webobjects-server-name" "raspberrypi" > RequestHeader set "x-webobjects-server-url" "http://raspberrypi"; > RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0" > RequestHeader set "x-webobjects-remote-host" %{REMOTE_HOST}e env=REMOTE_HOST > AddDefaultCharset UTF-8 > Order allow,deny > Allow from all > </Proxy> > ## We use mod_rewrite to pass remote address to the SOGo proxy. > # The remote address will appear in SOGo's log files and in the X-Forward > # header of emails. > RewriteEngine On > RewriteRule ^/SOGo/(.*)$ /SOGo/$1 [env=REMOTE_HOST:%{REMOTE_ADDR},PT] > > > Is there any error within the apache config that could cause the error in the > web interface? > > Thanks in advance, > Tobias > > -----Ursprüngliche Nachricht----- > Von: users-requ...@sogo.nu [mailto:users-requ...@sogo.nu] Im Auftrag von > Christian M. Jesnen > Gesendet: Freitag, 1. Mai 2015 19:57 > An: users@sogo.nu > Betreff: Re: [SOGo] login failed > > based on the log you send along, you successfully login so one must assume > your database connection is working > > so based on my experience > > have you checked that the imap settings for the domain i correct.? > - Folder names > - Folder separator > that will cause the UI to hang on login but after a while you would be able > to use the calendar and contact page > > other things that will cause the UI to hang "forever" is the configuration of > your web server you might have it set incorrect proxy settings > > that's basically all i got to offer at this point > > ooh one more thing, the error with "No child available to handle incoming > request" is usually (for me), when the configuration is flawed > > Regards > Christian > > > On Friday, May 1, 2015 17:22 CEST, <artbala...@gmail.com> wrote: > > > Hi there I have difficulties login on newly installed sogo webmail. I can > > access the login page of my sogo installation but it was stuck in there,, > > then > > after sometimes I was unable to connect. > > I've pasted log errors of my sogo logs. > > > > May 01 10:39:04 sogod [3807]: localhost "GET /SOGo.woa/WebServerResources/ > > ContactsUI.js?lm=1430483560 HTTP/1.1" 200 56027/0 0.029 - - 0 > > May 01 10:39:04 sogod [3795]: [ERROR] <0x0x7fd7e2e3ea98[WOWatchDog]> No > > child > > available to handle incoming request!.............. > > -- > users@sogo.nu > https://inverse.ca/sogo/lists > > -- > users@sogo.nu > https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
