General discussion on installation and configuration of SOGo

Text archives Help


Re: [SOGo] Thunderbird Fetching Wrong Certificates After Update to1.3.4


Chronological Thread 
  • From: Asai < >
  • To:
  • Subject: Re: [SOGo] Thunderbird Fetching Wrong Certificates After Update to1.3.4
  • Date: Thu, 30 Dec 2010 12:00:11 -0700
  • Organization: Global Change Multi-Media

I had changed the SOGo.conf file from https://mydomain to https://mydomain after I realizes I left the https in there by mistake, but it's still trying to connect via 443.  Restarted apache and sogo...

SOGO.conf is as follows.  I don't believe there's anything wrong with it...but maybe I don't know what I'm looking at:

Alias /SOGo.woa/WebServerResources/ \
      /usr/GNUstep/System/Library/SOGo/WebServerResources/
Alias /SOGo/WebServerResources/ \
      /usr/GNUstep/System/Library/SOGo/WebServerResources/
AliasMatch /SOGo/so/ControlPanel/Products/(.*)/Resources/(.*) \
           /usr/GNUstep/System/Library/SOGo/$1.SOGo/Resources/$2

<LocationMatch "^/SOGo/so/ControlPanel/Products/.*UI/Resources/.*\.(jpg|png|gif|css|js)">
  SetHandler default-handler
</LocationMatch>

## Uncomment the following to enable proxy-side authentication, you will then
## need to set the "SOGoTrustProxyAuthentication" SOGo user default to YES and
## adjust the "x-webobjects-remote-user" proxy header in the "Proxy" section
## below.
#<Location /SOGo>
#  AuthType XXX
#  Require valid-user
#  SetEnv proxy-nokeepalive 1
#  Allow from all
#</Location>

ProxyRequests Off
SetEnv proxy-nokeepalive 1
ProxyPreserveHost On

# When using CAS, you should uncomment this and install cas-proxy-validate.py
# in /usr/lib/cgi-bin to reduce server overloading
#
# ProxyPass /SOGo/casProxy http://localhost/cgi-bin/cas-proxy-validate.py
# <Proxy http://localhost/app/cas-proxy-validate.py>
#   Order deny,allow
#   Allow from your-cas-host-addr
# </Proxy>

ProxyPass /SOGo http://127.0.0.1:20000/SOGo retry=0

<Proxy http://127.0.0.1:20000/SOGo>
## adjust the following to your configuration
  RequestHeader set "x-webobjects-server-port" "80"
  RequestHeader set "x-webobjects-server-name" "triata.globalchangemultimedia.net"
  RequestHeader set "x-webobjects-server-url" "http://globalchangemultimedia.net"

## When using proxy-side autentication, you need to uncomment and
## adjust the following line:
#  RequestHeader set "x-webobjects-remote-user" "%{REMOTE_USER}e"

  RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
  RequestHeader set "x-webobjects-remote-host" %{REMOTE_HOST}e env=REMOTE_HOST

  AddDefaultCharset UTF-8
 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]

--asai

On 12/30/2010 11:52 AM, Ludovic Marcotte wrote:
" type="cite"> Check your Apache SOGo configuration file to see if your changes are still in there and if you have no trace of "example.com".

--
Ludovic Marcotte :: +1.514.755.3630
Inverse inc. :: http://inverse.ca


Date: Thu, 30 Dec 2010 10:30:58 -0700
Subject: [SOGo] Thunderbird Fetching Wrong Certificates After Update to 1.3.4

Greetings,

I updated to 1.3.4 this morning, and since then my Thunderbird users are reporting that they are being prompted about an invalid security certificate for our domain.  We have a security cert set up for another domain on the same IP address as the SOGo domain.  SOGo seems to be wanting to connect via port 443 now, whereas before it was fine connecting over port 80.  Does this make sense?  How do I change it back to connect on port 80 again?

--asai



Archive powered by MHonArc 2.6.16.

Top of page