Did you do the SQL Updates from /usr/share/doc/sogo
I assume you might need sql-update-5.5.1_to_5.6.0.sh

I have 5.5.1 installed and there is no such script as a sql-update-5.5.1_to_5.6.0.sh (the last being sql-update-3.2.10_to_4.0.0.sh)

also there is no error in the log indicating an error related to database schema.

sogo-log:

Aug 15 11:50:00 sogod [17689]: version 5.5.1 -- starting
Aug 15 11:50:00 sogod [17689]: vmem size check enabled: shutting down app when vmem > 384 MB. Currently at 90 MB
Aug 15 11:50:00 sogod [17689]: <0x0x561d29f7d700[SOGoProductLoader]> SOGo products loaded from '/usr/lib/GNUstep/SOGo':
Aug 15 11:50:00 sogod [17689]: <0x0x561d29f7d700[SOGoProductLoader]>   ContactsUI.SOGo, PreferencesUI.SOGo, MailerUI.SOGo, MainUI.SOGo, AdministrationUI.SOGo, Contacts.SOGo, Appointments.SOGo, MailPartViewers.SOGo, CommonUI.SOGo, Mailer.SOGo, SchedulerUI.SOGo
Aug 15 11:50:00 sogod [17689]: All products loaded - current memory usage at 97 MB
Aug 15 11:50:00 sogod [17689]: <0x0x561d29fcc4a0[WOWatchDog]> listening on 127.0.0.1:20000
Aug 15 11:50:00 sogod [17689]: <0x0x561d29fcc4a0[WOWatchDog]> watchdog process pid: 17689
Aug 15 11:50:00 sogod [17689]: <0x0x7fb7b1ba2360[WOWatchDogChild]> watchdog request timeout set to 10 minutes
Aug 15 11:50:00 sogod [17689]: <0x0x561d29fcc4a0[WOWatchDog]> preparing 3 children
Aug 15 11:50:00 sogod [17689]: <0x0x561d29fcc4a0[WOWatchDog]> child spawned with pid 17690
Aug 15 11:50:00 sogod [17689]: <0x0x561d29fcc4a0[WOWatchDog]> child spawned with pid 17691
Aug 15 11:50:00 sogod [17689]: <0x0x561d29fcc4a0[WOWatchDog]> child spawned with pid 17692
Aug 15 11:50:00 sogod [17692]: <0x0x561d29ffe460[WOHttpAdaptor]> notified the watchdog that we are ready
Aug 15 11:50:00 sogod [17691]: <0x0x561d29ffe460[WOHttpAdaptor]> notified the watchdog that we are ready
Aug 15 11:50:00 sogod [17690]: <0x0x561d2a00e6c0[WOHttpAdaptor]> notified the watchdog that we are ready

syslog:

Aug 15 11:49:58 s4 systemd[1]: Stopping SOGo is a groupware server...
Aug 15 11:50:00 s4 systemd[1]: sogo.service: Deactivated successfully.
Aug 15 11:50:00 s4 systemd[1]: Stopped SOGo is a groupware server.
Aug 15 11:50:00 s4 systemd[1]: sogo.service: Consumed 1.180s CPU time.
Aug 15 11:50:00 s4 systemd[1]: Starting SOGo is a groupware server...
Aug 15 11:50:00 s4 systemd[1]: Started SOGo is a groupware server.

seems smooth

I did some research on the installation:

1. Nightly build and Ubuntu repo use different installation directories (Templates and WebServerResources are in /usr/share/in Ubuntu while in /usr/lib in Nightly)
2. I completely removed and reinstalled the repo version (which uses a more up-to-date libgnustep-base1.28)

sogo seems to work now but the web frontend, cal- and carddav connectors are missing.

To get this, I need to set up a virtual host on the web server.

There used to be a template (contained path and access rights to some internal directories) which I cannot find any more.

Current situation:
sogod -> up and running
web -> missing configuration

Is there a place I can find it?

just a guess:

do you have configured "localhost" as imap server in sogo.conf?

if so, you could try to change it to 127.0.0.1: this forces usage of ipv4. sogo 4.71 introduces ipv6 support...

Current findings and resolution:

1. the Ubuntu sogo package lacks the SOGo.conf file for Apache -> No web frontend with this package out of the box

2. SOGo documentation has the sample config file deleted (it was in previous documentations that I luckily downloaded)

3. Re-Installing sogo from scatch (after completely cleaning all remains of previous installations and nightly's) -> sogo runs as a daemon

4. Recover a backup of my previous Apache config file for my virtual host allows web frontend but no content. Cards and Cal works in the web frontend and as services

5. NO exchanging 127.0.0.1 with 127.0.0.1: or localhost does not change anything (please refer to the GNUStep source code to see why).

6. Blank page after logon -> the syslog records logon denies. This is due to default (selfsigned) snakeoil.pem certificates. Server name and port mismatches for
   SOGoIMAPServer = imaps://<server_name_as_in_certificate>:993
   If server name matches, make sure port 993 for imaps is selected (depending on MTA-config)
   => DO NOT USE "/?tls=YES" after the port.

7. Be aware of Apache configuration. Apache2 has a defined structure with configurations, sites, modules and ports (only the first two are relevant). If you use virtual servers, do not enable the configuration. Rather set a default site that points to an error page.
   There are some rewrites and aliases in the configuration that make SOGo a pain in the neck administering (there are two nearly identical directory branches in /usr/lib and /usr/share and it is not obvious, which branch is taken - due to symlinks between the two)

=> IT WOULD BE APPRECIATED IF THE SOGO TEAM WOULD PROVIDE A SAMPLE APACHE CONFIG FOR REFERENCE!!! (Thanks)

Hi war,

would this help ? https://www.sogo.nu/files/docs/apache/SOGo.conf

If this is what your looking for I will update documentation on website

Yes, if it was available from the documentation, it should serve as a starting point.

Embedding it as a virtual host could be left to the administrator (URL rewrites, SSL). There was an amendment related to Apples CalDav and CardDav.

# For Apple autoconfiguration
<IfModule rewrite_module>
RewriteEngine On
RewriteRule ^/.well-known/caldav/?$ /SOGo/dav [R=301]
RewriteRule ^/.well-known/carddav/?$ /SOGo/dav [R=301]
</IfModule>

for me it looks like there are no packages for ubuntu 22.04: https://www.sogo.nu/download.html

so the 20.04 sogod compatible possible just crashes on ubuntu 22.04.

-> compile sogo yourself for ubuntu 22.04 or ask the sogo team to provide packages for it.

Hey there, a new entry in FAQ has been added : https://www.sogo.nu/support/faq/how-to-configure-apache-as-frontend.html

For Ubuntu 22.04 compatibility, this would be great as this is a LTS version. Put it in my todo.

Hi, as, this a duplicate of 0005511 I suggest to close this ticket. Let me know if you want to keep it opened.

I would not consider this a duplicate:

5511 requests a dedicated package for Ubuntu 22.04 (like was available for 20.04 for SOGo 5.7.1)
This issue - 5574 - has to do with a repo package 5.5.1 that fails to deliver the web configuration.

=> 5511 does not exist
=> 5574 exists but is outdated and broken

The forum entry (https://www.sogo.nu/support/faq/how-to-configure-apache-as-frontend.html) is a fragment that needs to be embedded into a virtual host definition or added as a configuration but as is does not help either.

All in all, SOGo requires deep administrative skills to install either on Ubuntu (and as I've come to learn) Fedora server. It is not an install-and-forget service as it used to be.

Ok thanks for clarification

Ubuntu provides 5.5.1 in its standard repo

Please CLOSE this issue.