Hi Odhiambo,

thanks for your answer,

I'm running on MySQL and can actually log in to the database from console with the user configured in the conf. sogo-tool dump-defaults does not return anything.

I was looking in nginx because it feels for me that something before SOGo is not running correctly yet.

Other LogLevel or Debug options in sogo.conf do not help, wihich makes me even more think that the problem is caused somewhere in Apache or Nginx, not in SOGo. I do not find any request in SOGo.log, it just says it started fine and that was it.

Any other ideas are really appreciated, I think it's something really stupid :-),

Thanks a lot,

Carsten


Am 13.03.19 um 14:04 schrieb Odhiambo Washington (odhia...@gmail.com):


On Wed, 13 Mar 2019 at 15:48, Carsten Pieper <users@sogo.nu <mailto:users@sogo.nu>> wrote:

    Hi all,

    sorry, I think I have quite a stupid question this time.

    I try to install SOGo v4.0.7 on my new server on Ubuntu 16.

    Installation succeeded, I copied the database from the old server,


Which database?

    checked /etc/sogo/sogo.conf

    and /etc/apache2/conf-enabled/SOGo.conf

    When I try to open https://mydomain.tld/SOGo/ I get an Internal
    Server Error on mydomain.tld:443.

    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.


Why are you checking  /var/log/nginx/error.lo, if I may ask?

    I checked if SOGo is running:

    root@server:/var/log/nginx# service sogo status
    ● sogo.service - LSB: SOGo server
       Loaded: loaded (/etc/init.d/sogo; bad; vendor preset: enabled)
       Active: active (running) since Wed 2019-03-13 11:48:07 CET; 1h
    52min ago
         Docs: man:systemd-sysv-generator(8)
      Process: 24670 ExecStop=/etc/init.d/sogo stop (code=exited,
    status=0/SUCCESS)
      Process: 24740 ExecStart=/etc/init.d/sogo start (code=exited,
    status=0/SUCCESS)
       CGroup: /system.slice/sogo.service
               ├─24811 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile
    /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log
               ├─24812 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile
    /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log
               ├─24813 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile
    /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log
               └─24814 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile
    /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log

    Mar 13 11:48:07 mydomain.tld sogo[24740]:  * Starting SOGo sogo
    Mar 13 11:48:07 mydomain.tld sogo[24740]:    ...done.

    Does anybody have an idea what I'm doing wrong and I have to do to
    get the login screens displayed?

Does "LogLevel Debug" in /etc/apache2/conf-enabled/SOGo.conf help??

How about you check the configs closely again?
How about enable the Debug options in sogo.conf?




--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
--
users@sogo.nu
https://inverse.ca/sogo/lists
--


CARSTEN PIEPER
Dyckburgheide 1
48157 Münster
Deutschland

Fon:    +49 251 3997257
Fax:    +49 251 3997256
Mobil:  +49 151 46673961
E-Mail:         i...@carstenpieper.com
Internet:       www.carstenpieper.com

--
users@sogo.nu
https://inverse.ca/sogo/lists

Reply via email to