General discussion on installation and configuration of SOGo

Text archives Help


Re: [SOGo] Ssl and reverse proxy


Chronological Thread 
  • From: "Christian Mack" ( ) < >
  • To:
  • Subject: Re: [SOGo] Ssl and reverse proxy
  • Date: Wed, 24 Aug 2016 11:09:47 +0200
  • Dmarc-filter: OpenDMARC Filter v1.2.0 mail.inverse.ca F032AEE5FC4

Hello

Am 27.07.2016 um 21:32 schrieb Andrew J Hacker
( ):
> Trying to install Sogo on a backend server with a front end apache proxy
>
> Tried a few different things but generally trying to get this working and
> having all kinds of issues.
> Not sure where to put different pieces of the Apache config...
> user -> SSL -> Front end Apache mod_proxy -> HTTP (80) -> Backend apache
> mod_proxy (proxy HTTP to 127.0.0.1:20000)
> i have alias for webresources on back end and proxypass on front and for
> 443 to 80 and then again on the backend from 80 to 20000
> i get many different errors from 404's on the JS to can't find SOGo index
> to infinite loops.
> Are there any guidelines for doing this?
> I could map the 443 on the front end directly to port 20000 on the backend
> but then i can't do aliasing
> Thanks!Andrew
>

You have to map directly to 20000 in your Apache like this.
...
RewriteCond %{REQUEST_METHOD} ^(GET|HEAD) [NC]
RewriteRule ^/$ https://frontend.server.tld/SOGo/ [L,R=301]

RewriteRule ^/.well-known/caldav/?$
https://frontend.server.tld/SOGo/dav/ [L,R=301]
RewriteRule ^/.well-known/carddav/?$
https://frontend.server.tld/SOGo/dav/ [L,R=301]

...

ProxyRequests Off
SetEnv proxy-nokeepalive 1
SetEnv force-proxy-request-1.0 1
SetEnv proxy-initial-not-pooled 1
ProxyPreserveHost On
ProxyTimeout 300
connectiontimeout=10 timeout=60
ProxyPass /SOGo http://backend.server.tld:20000/SOGo retry=0
connectiontimeout=120 timeout=900 keepalive=On
<Proxy http://backend.server.tld:20000/SOGo>
## adjust the following to your configuration
RequestHeader set "x-webobjects-server-port" "443"
RequestHeader set "x-webobjects-server-name" "frontend.server.tld"
RequestHeader set "x-webobjects-server-url" "https://frontend.server.org";

## 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" "%{SENDER_IP_ADDRESS}e"

AddDefaultCharset UTF-8

Order allow,deny
Allow from all
</Proxy>
...


Then you have to set
WOPort = backend.server.tld:20000;
in your sogo.conf


Hope this hint helps.


Kind regards,
Christian Mack

--
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature



  • Re: [SOGo] Ssl and reverse proxy, Christian Mack, 08/24/2016

Archive powered by MHonArc 2.6.18.

Top of page