Got it, proxy_http was not enabled in my apache settings.
Now i have a login screen but it seems not to have any UI template loaded.
Am 06.01.2011 16:45, schrieb Stefan Fuhrberg:
Here's the content of my apaches error_log:
[Thu Jan 06 14:42:38 2011] [warn] Init: Session Cache is not
configured [hint: SSLSessionCache]
[Thu Jan 06 14:42:38 2011] [notice] Apache/2.2.13 (Linux/SUSE)
mod_ssl/2.2.13 OpenSSL/0.9.8k PHP/5.3.0 configured -- resuming normal
operations
[Thu Jan 06 14:43:04 2011] [warn] proxy: No protocol handler was valid
for the URL /SOGo. If you are using a DSO version of mod_proxy, make
sure the proxy submodules are included in the configuration using
LoadModule.
[Thu Jan 06 14:43:06 2011] [warn] proxy: No protocol handler was valid
for the URL /SOGo. If you are using a DSO version of mod_proxy, make
sure the proxy submodules are included in the configuration using
LoadModule.
[Thu Jan 06 14:46:42 2011] [warn] proxy: No protocol handler was valid
for the URL /SOGo. If you are using a DSO version of mod_proxy, make
sure the proxy submodules are included in the configuration using
LoadModule.
[Thu Jan 06 14:49:22 2011] [warn] proxy: No protocol handler was valid
for the URL /SOGo. If you are using a DSO version of mod_proxy, make
sure the proxy submodules are included in the configuration using
LoadModule.
[Thu Jan 06 14:49:23 2011] [warn] proxy: No protocol handler was valid
for the URL /SOGo. If you are using a DSO version of mod_proxy, make
sure the proxy submodules are included in the configuration using
LoadModule.
[Thu Jan 06 14:49:25 2011] [warn] proxy: No protocol handler was valid
for the URL /SOGo. If you are using a DSO version of mod_proxy, make
sure the proxy submodules are included in the configuration using
LoadModule.
[Thu Jan 06 14:49:27 2011] [warn] proxy: No protocol handler was valid
for the URL /SOGo. If you are using a DSO version of mod_proxy, make
sure the proxy submodules are included in the configuration using
LoadModule.
[Thu Jan 06 15:31:13 2011] [warn] proxy: No protocol handler was valid
for the URL /SOGo. If you are using a DSO version of mod_proxy, make
sure the proxy submodules are included in the configuration using
LoadModule.
[Thu Jan 06 15:49:44 2011] [warn] proxy: No protocol handler was valid
for the URL /SOGo. If you are using a DSO version of mod_proxy, make
sure the proxy submodules are included in the configuration using
LoadModule.
[Thu Jan 06 15:50:14 2011] [warn] proxy: No protocol handler was valid
for the URL /SOGo/WebServerResources. If you are using a DSO version
of mod_proxy, make sure the proxy submodules are included in the
configuration using LoadModule.
[Thu Jan 06 15:50:19 2011] [warn] proxy: No protocol handler was valid
for the URL /SOGo/. If you are using a DSO version of mod_proxy, make
sure the proxy submodules are included in the configuration using
LoadModule.
[Thu Jan 06 16:40:30 2011] [notice] caught SIGTERM, shutting down
Maybe these errors causing the Web Frontend not to work?
Am 06.01.2011 14:47, schrieb Jan-Frode Myklebust:
On Thu, Jan 06, 2011 at 02:45:24PM +0100, Stefan Fuhrberg wrote:
That fixed the Adaptor Message, rest of the log looks still the same.
RequestHeader set "x-webobjects-server-port" "443"
RequestHeader set "x-webobjects-server-name" "sogo"
RequestHeader set "x-webobjects-server-url" "http://sogo";
x-webobjects-server-port should likely be "80" for an http url.
-jf
--
Mit freundlichen Grüßen
ZAG Personaldienste
i.A. Stefan Fuhrberg
Ihre Antwort richten Sie bitte an: mailto:kontakt...@zag.de
Besuchen Sie uns im Internet: http://www.zag.de
ZAG Verwaltungs-Gesellschaft GmbH
IT-Abteilung
Nikolaistraße 11
30159 Hannover
Fon: 0511-12606444
Fax: 0511-12606419
Amtsgericht: Hannover
Handelsregister: HRB 52841
Geschäftsführer: Wolfgang Klenner, Bastian Tau, Martin Weiß
--
users@sogo.nu
https://inverse.ca/sogo/lists
