General discussion on installation and configuration of SOGo

Text archives Help


Re: [SOGo] Proxy error after upgrade to Sogo V3


Chronological Thread 
  • From: "Christian Mack" ( ) < >
  • To:
  • Subject: Re: [SOGo] Proxy error after upgrade to Sogo V3
  • Date: Thu, 30 Jun 2016 09:15:10 +0200
  • Dmarc-filter: OpenDMARC Filter v1.2.0 mail.inverse.ca F0390F2012E

Hello

Am 29.06.2016 um 17:00 schrieb Alessio Cecchi
( ):
>
> I upgrade from sogo 2.3.12 to sogo 3.1.3 with also the MySQL DB
> migration via sql-update-3.0.0-to-combined-mysql.sh to "nine tables"
> configurations.
>
> For almost users all works fine but someone was able to login but the
> Sogo interfaces don't allow to do nothing with and show a "Proxy error"
> message.
>
> In sogo.log I found this:
>
> Jun 29 16:55:50 sogod [20426]: 192.168.6.12 "GET /SOGo/ HTTP/1.1" 200
> 7220/0 0.015 23061 68% 4K
> Jun 29 16:56:00 sogod [20426]: SOGoRootPage successful login from
> '192.168.6.12' for user
> ' '
> - expire = -1 grace = -1
> Jun 29 16:56:00 sogod [20426]: 192.168.6.12 "POST /SOGo/connect
> HTTP/1.1" 200 27/88 0.100 - - 0
> Jun 29 16:56:00 sogod [20426]: 192.168.6.12 "GET
> /SOGo//
> HTTP/1.1" 302 0/0 0.003 - - 0
> Jun 29 16:56:00 sogod [20426]: 192.168.6.12 "GET
> /SOGo// /view
> HTTP/1.1" 302 0/0 0.004 - - 0
> Jun 29 16:56:00 sogod [20426]: 192.168.6.12 "GET
> /SOGo/so/ /Mail
> HTTP/1.1" 302 0/0 0.003 - - 0
> Jun 29 16:56:00 sogod [20426]: 192.168.6.12 "GET
> /SOGo/so/ /Mail/view
> HTTP/1.1" 200 17220/0 0.034 69812 75% 0
> Jun 29 16:56:00 sogod [20426]: 192.168.6.12 "GET
> /SOGo/so/ /Calendar/alarmslist?browserTime=1467212179
> HTTP/1.1" 200 63/0 0.006 - - 0
> EXCEPTION: <NSException: 0x7f1dc90b1eb0> NAME:NSInvalidArgumentException
> REASON:Tried to add nil value for key 'PreventInvitationsWhitelist' to
> dictionary INFO:{FoldersOrder = (personal); PreventInvitations = 0;
> PreventInvitationsWhitelist = ""; }
> Jun 29 16:56:00 sogod [20426]: 192.168.6.12 "GET
> /SOGo/so/ /jsonDefaults
> HTTP/1.1" 200 3203/0 0.015 - - 0
> Jun 29 16:56:00 sogod [18140]: <0x0x7f1dc8bbcec0[WOWatchDogChild]> child
> 20429 exited
> Jun 29 16:56:00 sogod [18140]: <0x0x7f1dc8bbcec0[WOWatchDogChild]>
> (terminated due to signal 6)
> Jun 29 16:56:00 sogod [18140]: <0x0x7f1dc88ee2f0[WOWatchDog]> child
> spawned with pid 21503
> Jun 29 16:56:01 sogod [20425]: 192.168.6.12 "GET
> /SOGo/so/ /Mail/0/view
> HTTP/1.1" 200 614/0 0.421 - - 4K
> Jun 29 16:56:01 sogod [20425]: 192.168.6.12 "POST
> /SOGo/so/ /Mail/unseenCount
> HTTP/1.1" 200 21/31 0.094 - - 0
>
>
> And in apache error.log:
>
> [Wed Jun 29 16:56:00 2016] [error] [client 192.168.6.12] (20014)Internal
> error: proxy: error reading status line from remote server
> 127.0.0.1:20000, referer:
> https://sogo-v3.ciao.it/SOGo/so/ /Mail/view
> [Wed Jun 29 16:56:00 2016] [error] [client 192.168.6.12] proxy: Error
> reading from remote server returned by
> /SOGo/so/ /jsonSettings,
> referer:
> https://sogo-v3.ciao.it/SOGo/so/ /Mail/view
> [Wed Jun 29 16:56:38 2016] [error] [client 192.168.6.12] (20014)Internal
> error: proxy: error reading status line from remote server
> 127.0.0.1:20000, referer:
> https://sogo-v3.ciao.it/SOGo/so/ /Preferences
> [Wed Jun 29 16:56:38 2016] [error] [client 192.168.6.12] proxy: Error
> reading from remote server returned by
> /SOGo/so/ /jsonSettings,
> referer:
> https://sogo-v3.ciao.it/SOGo/so/ /Preferences
>
>
> Can I fix it or is a bug?
> Thanks

Check the preferences of that user.
Did she disable being invitable?
Did she have an empty whitelist for that?
Perhaps it will help to add someone to the whitelist.

If that workaround helps, it is a bug ;-)


Kind regards,
Christian Mack

--
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature




Archive powered by MHonArc 2.6.18.

Top of page