I use both versions of course. The error messages don’t have anything to do with the protocol of the web-request (think about 7 layer ISO modell…).
Lets specify: The ZEG-5.1.0 is supposted to work without modifications, it doesn’t. "SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY" points to a Memcached Problem, but Memcached is installed correctly and modifying the conf file doesn’t change anything. There is probably something wrong with the current ZEG build. Could some of the people who created it, check it. SOGoRootPage Login from '192.168.122.12' for user 'smbuser' might not have worked - password policy: 65535 grace: -1 expire: -1 bound: 0 Is such a generic error message (“might not have worked”: how can that be a computer term). I turned on all debug options in sogo.conf, but don’t get any messages. I don’t think I get log entries on Samba DC too, so I can’t even check if LDAP requests are made. Anybody? Von: users-requ...@sogo.nu <users-requ...@sogo.nu> Im Auftrag von maxnux Gesendet: Mittwoch, 19. Juni 2024 15:17 An: users@sogo.nu Betreff: Re:[SOGo] you use http or https in the link ? El 18/6/24 a las 15:56, ballt (ba...@mds4u.de <mailto:ba...@mds4u.de> ) escribió: Downloaded newest version, installed VM. System works, but I can’t login via Web interface. Immediately after login I get logged out. Tried all test user, created new one, no change. Error message in sogo.log is: Jun 16 16:07:08 sogod [2761]: <0x0x561a780f0df0[SOGoCache]> an error occurred when caching value for key 'admin-motd': "SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY" I also have a manual installation, that doesn’t allow me to log in too. Try to log using samba. Made all changes to sogo.conf. Error message is always: SOGoRootPage Login from '192.168.122.12' for user 'smbuser' might not have worked - password policy: 65535 grace: -1 expire: -1 bound: 0 Any ideas? Thomas
