OK, I got it solved! For whatever reason the line: ProxyPass /SOGo http://127.0.0.1:20000/SOGo retry=0 was missing in my SOGo.conf.
I have no idea why, or why it worked before without the line. However it is working now. Thank you for steering me towards the Apache! Best regards Ingo 2014-12-15 13:36 GMT-08:00 Ingo N. <[email protected]>: > > Oh, actually I get: > The requested URL /SOGo was not found on this server. > when going to myhost.com/SOGo > > 2014-12-15 13:34 GMT-08:00 Ingo N. <[email protected]>: > >> Hi Maxime, >> >> Thank you for your reply. >> A netstat gives me: tcp 0 0 127.0.0.1:20000 0.0.0.0:* >> LISTEN >> but it doesn't say sogo. >> Also I don't get anything on myhost.com:20000 >> I was wrong with Android, it doesn't work either. So it looks like >> something in my Apache is wrong. >> Any ideo how I can figure that out? >> >> Thanks for your help! >> Ingo >> >> 2014-12-15 13:03 GMT-08:00 Maxime RUBINO <[email protected]>: >> >>> Hi Ingo, >>> >>>> Hi guys, >>>> >>>> I just updated SOGo a couple days ago from 2.2.10 to 2.2.11a. >>>> It seems like that since then I am having problems. I didn't realize it >>>> until today, since I mostly use it on my Android, but the web interface is >>>> not working (404) and my Thunderbird is not either. >>>> >>> >>> Do you have check your apache conf ? 404, page not found, so... >>> >>>> >>>> A ps -ax | grep sogo shows that there are 4 worker tasks running. >>>> >>> Check listening ports 20000 from sogod (tcp6 or tcp4 ?) with netstat >>> -anlput | grep sogo >>> >>>> >>>> The sogo.log doesn't show any errors. >>>> >>> If you don't have any errors/command in sogo.log, you have a problem >>> with sogo proxy conf from apache. >>> >>> -- >>> Cordialement, >>> Maxime RUBINO >>> >>> -- >>> [email protected] >>> https://inverse.ca/sogo/lists >>> >> -- [email protected] https://inverse.ca/sogo/lists
