I know that the nginx config has nothing to to with the SOGo config, but with the alias directive you can redirect things.
Anyway, I did create the directory /usr/local/etc/sogo/ and copied the config over, yet nothing has changed. Also, I'm doing my testing in a separate browser in private mode, so no caching on the browser side can be the cause of interference. Best Richard On Mon, Sep 2, 2024, 14:45 Christian Mack <users@sogo.nu> wrote: > Hello > > The SOGo configuration location has nothing to do with nginx. > > As you changed the installation Path to /usr/local/, SOGo will expect > its configuration at /usr/local/etc/sogo/ > You could symlink that to /etc/sogo/ or copy the files into it. > > > Kind regards, > Christian Mack > > Am 02.09.24 um 14:10 schrieb Richard (rrosn...@gmail.com): > > Hi, > > so, to check if an issue I reported [1] is only related to the SOGo > version > > we use or if it's a general issue, I compiled SOGo now manually and > > installed it (so it's now located in /usr/local/lib in parallel to > > /usr/lib/). Trying to change our nginx config to point to /usr/local/lib > it > > looks like the installation isn't getting its config that's located in > > /etc/sogo. At least it only shows the green header bar, so login seems to > > succeed, but sogo log says > > > > Sep 02 14:02:03 sogod [21933]: [ERROR] > >> <0x0x5581b2e2b1b0[NGImap4ConnectionManager]> IMAP4 login failed: > >> host=localhost, user=anonymous, pwd=yes > >> url=imap://anonymous@localhost/?tls=NO&tlsVerifyMode=default > >> base=(null) > >> base-class=(null)) > >> = <0x0x5581b57be680[NGImap4Client]: login=anonymous(pwd) > >> socket=<NGActiveSocket[0x0x5581b57c40a0]: mode=rw > >> address=<0x0x5581b56f06c0[NGInternetSocketAddress]: host=localhost > port=511\ > >> 02> connectedTo=<0x0x5581b472e3f0[NGInternetSocketAddress]: > host=localhost > >> port=143>>> > >> Sep 02 14:02:03 sogod [21933]: <0x5581b5cb6c50[SOGoMailAccount]:0> > >> renewing imap4 password > >> Sep 02 14:02:03 sogod [21933]: <0x0x5581b2c37aa0[SOGoCache]> an error > >> occurred when caching value for key 'session:U+82hHFVjokuzDLa': "SERVER > HAS > >> FAILED AND IS DISABLED UNTIL TIMED RET\ > >> RY" > >> Sep 02 14:02:07 sogod [21933]: [ERROR] > >> <0x0x5581b2e2b1b0[NGImap4ConnectionManager]> IMAP4 login failed: > >> host=localhost, user=anonymous, pwd=yes > >> url=imap://anonymous@localhost/?tls=NO&tlsVerifyMode=default > >> base=(null) > >> base-class=(null)) > >> = <0x0x5581b5a35ac0[NGImap4Client]: login=anonymous(pwd) > >> socket=<NGActiveSocket[0x0x5581b58d63d0]: mode=rw > >> address=<0x0x5581b5823f40[NGInternetSocketAddress]: host=localhost > port=431\ > >> 24> connectedTo=<0x0x5581b5752420[NGInternetSocketAddress]: > host=localhost > >> port=143>>> > >> Sep 02 14:02:07 sogod [21933]: [ERROR] > <0x5581b5cb6c50[SOGoMailAccount]:0> > >> Could not connect IMAP4 > >> > > > > Is there something like an nginx directive I could set to tell sogo what > > settings file to use? > > > > Best > > Richard > > > > > > [1]: https://bugs.sogo.nu/view.php?id=5976 > > > > -- > Christian Mack > Universität Konstanz > Kommunikations-, Informations-, Medienzentrum (KIM) > Abteilung IT-Dienste Forschung, Lehre, Infrastruktur > 78457 Konstanz > +49 7531 88-4416 > >
