[SOGo] Second Host on SOGo/Zentyal Server
I am trying to install a second, ssl enabled vhost on my Sogo/Zentyal
server, but I'm running into difficulty with the proxy. I keep getting the
error
The stylesheet
https://www.[i]mysecondsite[/i].com/SOGo.woa/WebServerResources/dtree.css?lm=1459872312
was not loaded because its MIME type, “application/octet-stream”, is not
“text/css”.
I have a ProxyPass directive, to send everything non-sogo related into
another server. That doesn't seem to be having any effect on the above
error. I have even tried copying and pasting the original sogo conf file,
to the second site, but it doesn't work. I have tried with and without the
SOGo.woa proxypass directive. Sogo does not seem to pick up the Alias
/SOGo.woa/WebServerResources/ , as it won't load any of the .woa resources,
without the ProxyPass /SOGo.woa ... Does anyone have any ideas?
Here is my .conf file That I am currently working with. Keep in mind that I
have heavily changed the second, ssl, virtualhost. I started by duplicating
the original VirtualHost, changing the ServerName and ServerAlias, but that
didn't work.
user www-data
group www-data
WSGILazyInitialization On
WSGIPythonPath /usr/lib/openchange/web/rpcproxy
WSGIScriptAlias /rpc/rpcproxy.dll
/usr/lib/openchange/web/rpcproxy/rpcproxy.wsgi
WSGIScriptAlias /rpcwithcert/rpcproxy.dll
/usr/lib/openchange/web/rpcproxy/rpcproxy.wsgi
ServerName zentyal.myfirstsite.com
ServerAlias autodiscover.myfirstsite.com
DocumentRoot /var/www/html
SSLEngine on
SSLCertificateFile /etc/ocsmanager/myfirstsite.com.pem
ProxyAddHeaders On
Autodiscover begin
ProxyPassMatch /[Aa]utodiscover(.*)$
http://127.0.0.1:5000/autodiscover$1
#
EWS
#
ProxyPass /ews http://127.0.0.1:5000/ews
#
RPC Proxy begin
#
# Extremely high timeout required by clients)
Timeout 300
KeepAlive On
KeepAliveTimeout 120
MaxKeepAliveRequests 500
AddDefaultCharset utf-8
Include /etc/apache2/mods-available/wsgi.load
Include /etc/apache2/mods-available/env.load
SetEnv RPCPROXY_LOGLEVEL INFO
SetEnv NTLMAUTHHANDLER_WORKDIR /var/cache/ntlmauthhandler
SetEnv SAMBA_HOST 127.0.0.1
WSGIPassAuthorization On
WSGIProcessGroup %{GLOBAL}
Require all granted
SOGo webmail begin
Alias /SOGo.woa/WebServerResources/
/usr/lib/GNUstep/SOGo/WebServerResources/
Alias /SOGo/WebServerResources/
/usr/lib/GNUstep/SOGo/WebServerResources/
AliasMatch /SOGo/so/ControlPanel/Products/(.*)/Resources/(.*)
/usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2
AllowOverride None
Require all granted
# Explicitly allow caching of static content to avoid browser
specific
# behavior. A resource URL MUST change in order to have the client
# load the new version.
ExpiresActive On
ExpiresDefault "access plus 1 year"
SetHandler default-handler
## 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.
#
# AuthType XXX
# Require valid-user
# SetEnv proxy-nokeepalive 1
# Allow from all
#
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
# http://localhost/app/cas-proxy-validate.py>
# Order deny,allow
# Allow from your-cas-host-addr
#
ProxyPass /SOGo http://127.0.0.1:2/SOGo retry=0
ProxyPass /sogo/ http://127.0.0.1:2/SOGo
ProxyPass /sogo http://127.0.0.1:2/SOGo
ProxyPass /webmail/ http://127.0.0.1:2/SOGo
ProxyPass /webmail http://127.0.0.1:2/SOGo
ProxyPass /_debug http://127.0.0.1:5000/_debug retry=0
http://127.0.0.1:2/SOGo>
## 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-url" "https://
%{REQUEST_HOST}e:443"
SetEnvIf Host "(.*):?" REQUEST_HOST=$1
AddDefaultCharset UTF-8
Require all granted
# For apple autoconfiguration
RewriteEngine On
RewriteRule ^/.well-known/caldav/?$ /SOGo/dav [R=301]
CustomLog ${APACHE_LOG_DIR}/ocsmanager-access.log combined
ErrorLog ${APACHE_LOG_DIR}/ocsmanager-error.log
[SOGo] Auth. Capitalizing Login
Is there a way to force SOGo to accept what was typed in the login box, and not use the LDAP uid? This causes a problem when, the uid is or is not capitalized, but dovecot won't accept the case. If SOGo could be forced to pass the login, as typed, instead of passing the uid, it would eliminate this issue. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Updated Documentation 2.0.4
I found #1 at the end of the installation guide, so I apologize for bringing that to light. Might I be so bold as to suggest moving it to the beginning, as it's a key component in the entry of data for SOGo. On Thu, Feb 28, 2013 at 8:22 AM, Kevin Smith theonlytalkingg...@gmail.comwrote: Thanks for taking the time to ask, Francis. I hate having to write in a mailing list, asking for help. It's usually a last resort, for me. A couple examples: - No updated information on the sogo user. I had to dig on the net to find out the command to add defaults is now sudo -u sogo. - The location for the defaults file, if using sudo -u sogo defaults write sogod [command] is incorrect. In Ubuntu, it's in /var... not /usr... - There is no basic documentation as to where sogo.conf is supposed to reside, how it interacts with apache if sogo.conf is even created in Ubuntu. There was no sogo.conf created, when I used apt-get, in my installation. The documentation lists it as /etc/httpd/conf.d/SOGo.conf. httpd does not exist in Ubuntu, it's apache2. - How to list the defaults file, using sudo -u sogo defaults read sogod. - Installing from the .tar file, as far as I can tell, has no 'INSTALLATION' file, with directions on how to use the 'manual' install. - Providing numerous examples, maybe in an appendix, for setup scenarios would be amazingly helpful. If this software is to be extraordinarily successful, it should have the documentation for someone with less than 5 years of Linux experience can use, but that's just my opinion. On Thu, Feb 28, 2013 at 6:38 AM, Francis Lachapelle flachape...@inverse.ca wrote: Hi Only Talking Goat On 2013-02-27, at 4:02 PM, theonlytalkingg...@gmail.com wrote: Does anyone know of a comprehensive installation and usage guide for 2.0.4? I installed it on Ubuntu, using apt-get, and the documentation from the website is horribly wrong, for the most part. None of it works and it's outdated. I can't find any information about how SOGo interacts with Apache. Most of the files are not in the same place... Help. The guide is for RHEL/CentOS. Where is the documentation wrong for Ubuntu? Francis -- flachape...@inverse.ca :: +1.514.755.3640 :: http://www.inverse.ca Inverse :: Leaders behind SOGo (http://sogo.nu) and PacketFence ( http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Updated Documentation 2.0.4
Thanks for taking the time to ask, Francis. I hate having to write in a mailing list, asking for help. It's usually a last resort, for me. A couple examples: - No updated information on the sogo user. I had to dig on the net to find out the command to add defaults is now sudo -u sogo. - The location for the defaults file, if using sudo -u sogo defaults write sogod [command] is incorrect. In Ubuntu, it's in /var... not /usr... - There is no basic documentation as to where sogo.conf is supposed to reside, how it interacts with apache if sogo.conf is even created in Ubuntu. There was no sogo.conf created, when I used apt-get, in my installation. The documentation lists it as /etc/httpd/conf.d/SOGo.conf. httpd does not exist in Ubuntu, it's apache2. - How to list the defaults file, using sudo -u sogo defaults read sogod. - Installing from the .tar file, as far as I can tell, has no 'INSTALLATION' file, with directions on how to use the 'manual' install. - Providing numerous examples, maybe in an appendix, for setup scenarios would be amazingly helpful. If this software is to be extraordinarily successful, it should have the documentation for someone with less than 5 years of Linux experience can use, but that's just my opinion. On Thu, Feb 28, 2013 at 6:38 AM, Francis Lachapelle flachape...@inverse.cawrote: Hi Only Talking Goat On 2013-02-27, at 4:02 PM, theonlytalkingg...@gmail.com wrote: Does anyone know of a comprehensive installation and usage guide for 2.0.4? I installed it on Ubuntu, using apt-get, and the documentation from the website is horribly wrong, for the most part. None of it works and it's outdated. I can't find any information about how SOGo interacts with Apache. Most of the files are not in the same place... Help. The guide is for RHEL/CentOS. Where is the documentation wrong for Ubuntu? Francis -- flachape...@inverse.ca :: +1.514.755.3640 :: http://www.inverse.ca Inverse :: Leaders behind SOGo (http://sogo.nu) and PacketFence ( http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
