Author Topic: SOGo not working after update to Zentyal 5.0.1  (Read 3209 times)

lucrus

  • Zen Apprentice
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
SOGo not working after update to Zentyal 5.0.1
« on: February 02, 2018, 10:51:28 am »
I've updated from Zentyal 4.1 to 5.0.1.

After the update, when I try to log into SOGo, I'm redirected to:

https://localhost/(null):/SOGo/so/direzione/Mail

which obviously yelds a 404. Where does that "(null)" in the URL come from? What should be in its place?

wochozka

  • Zen Apprentice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: SOGo not working after update to Zentyal 5.0.1
« Reply #1 on: August 17, 2018, 11:33:02 pm »
I've updated from Zentyal 4.1 to 5.0.1.

After the update, when I try to log into SOGo, I'm redirected to:

https://localhost/(null):/SOGo/so/direzione/Mail

which obviously yelds a 404. Where does that "(null)" in the URL come from? What should be in its place?

I've the same problem. Please, have you solved this yet? Thanks :)

lucrus

  • Zen Apprentice
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: SOGo not working after update to Zentyal 5.0.1
« Reply #2 on: August 18, 2018, 09:31:07 am »
No. My "solution" was to avoid SOGo webmail altogether.  :-\

scottdr

  • Zen Apprentice
  • *
  • Posts: 18
  • Karma: +6/-0
  • Zentyal community edition 7.1.1
    • View Profile
Re: SOGo not working after update to Zentyal 5.0.1
« Reply #3 on: August 23, 2018, 03:55:47 pm »
I've changed my users shortcuts to go straight to their Inbox URL https://<server-ip>/SOGo/so/<userID>/Mail/view

This seems to work OK.

It would be nice to have a cure, but I ran out of time researching where this NULL addition gets added

scottdr

  • Zen Apprentice
  • *
  • Posts: 18
  • Karma: +6/-0
  • Zentyal community edition 7.1.1
    • View Profile
Re: SOGo not working after update to Zentyal 5.0.1
« Reply #4 on: August 23, 2018, 04:20:05 pm »
Update:
I have modified /usr/share/zentyal/stubs/sogo/SOGo.conf-apache.mas and changed the line: -

RequestHeader set "x-webobjects-server-url" "https://%{REQUEST_HOST}e:443"

to: -

RequestHeader set "x-webobjects-server-url" "https://%{REQUEST_HOST}e"

Then restarted "SOGo Webmail" from the console.

I made a copy of SOGo.conf-apache.mas before making any changes just in case I made an error.

Hope this helps

Thanks to a CZ site with the answer http://www.abclinuxu.cz/poradna/linux/show/438278
« Last Edit: February 03, 2022, 05:14:10 pm by scottdr »