Topic: SOGo doesn't work although it appears to authenticate users

[edform]

I know there has been much discussion of this topic but I cannot find a solution to my version of the "it doesn't work" situation anywhere; so here goes again...

I've loaded the smeserver-sogo contribution to a brand new SME 8b5 server by following the http://smeserver.nethesis.it/sogo/ howto and carefully solving each of the problems that arise with that procedure - incorrect repo configurations, unfulfilled dependencies, the need to update Ldap etc.

Once the install was complete I could raise the SOGo login screen with http://hostname/SOGo and using a valid username/password combination plainly authenticates the user because the URL changes to https://hostname.domain/SOGo/so/username/Mail, but the system will not display the page.

What's more, the user seems to remain logged in, even across server restarts, because the URL changes from http://hostname/SOGo to https://hostname.domain/SOGo/so/username/Mail without displaying the login page if I try to login again.

I'll check whether restarting the Windows machine that I'm running the browser login on detaches the user and add another note when I've done it.

Yes! Loging out and back in to the workstation releases the user - so that's probably a browser cache problem and nothing to do with the inability of the system to display the application.

What have I done wrong?

Ed Form

[edform]

I wondered if this was a browser incompatibilty issue so I loaded Firefox and the same problem occurred but with a more informative error message...

   Server not found

   Firefox can't find the server at mini-itx.theformsonline.com.
   etc. etc.

I know for certain that SOGo starts because the server shows it happening in the boot sequence, so what else can be missing?

Then I thought about the change from "http://hostname/SOGo" to "https://hostname.domainname/SOGo/so/username/Mail" and wondered if that was the problem. I altered the address in the screen with the "unable to display page" to "https://hostname/SOGo/so/username/Mail" and up came the SOGo opening page - the address also changed to "https://hostname/SOGo/so/username/Mail/View". From that point on the thing worked perfectly.

So the problem seems to be a duff link in a configuration file somewhere. Anyone know the location?

Ed Form

[edform]

I found the issue. The server was set up as server only with a single network card but today I added a second card and reconfigured the machine as a dedicated server and gateway. The URLs http://hostname.domainname/SOGo and https://hostname.domainname/SOGo now both work perfectly.

Ed Form

[Stefano]

Ed, you should report it as a bug, thank you

[edform]

Ed, you should report it as a bug, thank you

I'd be happy to, but where? The SME Bugzilla doesn't accept bugs for SME 8 Contribs as far as I can see.

Ed

[Stefano]

I'd be happy to, but where? The SME Bugzilla doesn't accept bugs for SME 8 Contribs as far as I can see.

Ed

you are right..

you could report your issue in this topic as I'm sure that Alessio will read it..

hth

[edform]

you could report your issue in this topic as I'm sure that Alessio will read it..

Done!

Ed Form