has been sent to my personal address ;-) -- [email protected] https://inverse.ca/sogo/lists
--- Begin Message ---After SOGoSuperUsernames in your sogo.conf, why are you indiscriminately commenting out and changing values without going by what the documentation says? :) Start with the minimal as suggested in the documentation.Anyway, that aside, could you please try changing the following two lines: <IfModule headers_module> RequestHeader set "x-webobjects-server-port" "443" <================ Make sure you know whether to use 443 or 80 SetEnvIf Host (.*) HTTP_HOST=$1 #RequestHeader set "x-webobjects-server-name" "%{HTTP_HOST}e" env=HTTP_HOST #RequestHeader set "x-webobjects-server-url" "https://%{HTTP_HOST}e"; env=HTTP_HOST RequestHeader set "x-webobjects-server-name" "FQDN" RequestHeader set "x-webobjects-server-url" "https://FQDN"; AddDefaultCharset UTF-8 Be sure to know whether it is http or https - if you do not have a certificate, please stay with http/port 80. This is just to test On Wed, 13 Mar 2019 at 20:33, Carsten Pieper <[email protected]> wrote: > Hi Markus, > Am 13.03.19 um 16:12 schrieb Markus Winkler ([email protected]): > > Hi Carsten, > > On Wed, 13 Mar 2019 at 02:56:17PM +0100, Carsten Pieper wrote: > > I was looking in nginx because it feels for me that something before SOGo > is not running correctly yet. > > > what I still cannot understand: you have Apache configured for SOGo, > right? What's the purpose of the additional Nginx in your setup? And do > you really have them _both_ running on the same host, are you sure? > > Yes I am, that is the default config in Plesk virtual servers. Nginx is > working as reverse proxy, see: > https://docs.plesk.com/de-DE/onyx/administrator-guide/webserver/apache-und-ngnixwebserver-linux/apache-mit-nginx.70837/ > (Sorry, German, but different translations are available. > > > > It would be good to know which webserver is doing which job. Could you > please send us an output of 'ps aux' and 'netstat -lntp' or something > similar? > > It would be helpful if you could: > > o set 'LogLevel debug' (in case of using Apache) > > Please find attached my /etc/apache2/conf-available/SOGo.conf > > and my /etc/sogo/sogo.conf > > > > o send an extract of the logs (configured for CustomLog and ErrorLog) > of the webserver which is serving SOGo right after you try to access > SOGo via browser (when you say that you get an 'Internal Server Error', > then there must be something to find in the log) - even if it doesn't > seem: > > I checked /var/log/sogo.log, var/log/apache2/error.log > and /var/log/nginx/error.log > and found nothing helpful to get the login screen displayed. > > > "interesting" to you. > > I've attached you the current sogo.log and apache error.log. > > > > makes me even more think that the problem is caused somewhere in Apache or > Nginx, not in SOGo. > > > At the moment I assume you have a problem with your webserver(s), but just > to be sure: did you check if the SOGo deamon is really running and listens > on the configured port? You should see something like this: > > tcp 0 0 127.0.0.1:20000 0.0.0.0:* LISTEN 1508/sogod > > Please find attached the output from ps and netstat in running > processes.txt > > > > Any other ideas are really appreciated, I think it's something really > stupid :-), > > > Let's see after you give a little more input. ;-) > > Thanks and regards, > Markus > > -- > > > THANK you so much for your support, I'm a little blinded at the moment... > > Regards, > > Carsten > > > > > > > > > > > > > -- > [email protected] > https://inverse.ca/sogo/lists > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)
--- End Message ---
