I looked at the scripts..judging by the file names, they don't seem to
apply to my case considering i updated from v2.3.8 to v3.0.2. am i
wrong?
- Fabe
On 2016-03-08 02:30, Purga wrote:
Have you updated the SQL tables as well?
https://github.com/inverse-inc/sogo/tree/master/Scripts
On Mon, Mar 7, 2016 at 7:25 AM, <fsanti...@garbage-juice.com> wrote:
Hello,
I switched my repo to that of v3 Sogo and updated my installation
today.
I also use nginx and centos 7.2.x.
As of now, i can no longer open my inboxes in the web UI.
Activesync seems to work fine on my mobile devices. My sogo log
reports:
Mar 06 17:59:10 sogod [10019]: <0x0x563aa66570d0[SOGoCache]> Using
host(s) '127.0.0.1' as server(s)
Mar 06 17:59:10 sogod [10019]: localhost "GET
/SOGo/so/fsanti...@garbage-juice.com/Mail/view [1] HTTP/1.0" 200
14748/0 0.081 66066 77% 6M
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry '{DAV:}write' already
exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry
'{DAV:}write-properties' already exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: [WARN]
<0x0x563aa6a10c40[SOGoWebDAVAclManager]> entry '{DAV:}write-content'
already exists in DAV permissions table
Mar 06 17:59:12 sogod [10019]: localhost "GET
/SOGo/so/fsanti...@garbage-juice.com/Calendar/alarmslist?browserTime=1457305156
[2] HTTP/1.0" 200 63/0 0.007 - - 256K
Mar 06 17:59:12 sogod [4127]: localhost "GET
/SOGo/so/fsanti...@garbage-juice.com/jsonSettings [3] HTTP/1.0" 200
189/0 0.003 - - 0
Mar 06 17:59:12 sogod [10019]: localhost "GET
/SOGo/so/fsanti...@garbage-juice.com/jsonDefaults [4] HTTP/1.0" 200
2125/0 0.009 - - 12K
EXCEPTION: <NSException: 0x563aa63dc030>
NAME:NSInvalidArgumentException REASON:NGImap4Connection(instance)
does not recognize allFoldersMetadataForURL:onlySubscribedFolders:
INFO:(null)
In Chrome, I simply see 'OK' in a pop down message.
In firefox, I see "Bad gateway" in the same box.
My nginx error log reports:
2016/03/06 17:59:12 [error] 4354#4354: *2 upstream prematurely
closed connection while reading response header from upstream,
client: x.x.x.x, server: _, request: "GET
/SOGo/so/fsanti...@garbage-juice.com/Mail/0/view [5] HTTP/2.0",
upstream:
"http://127.0.0.1:20000/SOGo/so/fsanti...@garbage-juice.com/Mail/0/view";,
host: "mail.garbage-juice.com [6]", referrer:
"https://mail.garbage-juice.com/SOGo/so/fsanti...@garbage-juice.com/Mail/view";
What could be going on? This worked fine prior to my upgrade with
v2.3.8 (latest).
Thanks.
- Fabian S.
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
Links:
------
[1] http://fsanti...@garbage-juice.com/Mail/view
[2]
http://fsanti...@garbage-juice.com/Calendar/alarmslist?browserTime=1457305156
[3] http://fsanti...@garbage-juice.com/jsonSettings
[4] http://fsanti...@garbage-juice.com/jsonDefaults
[5] http://fsanti...@garbage-juice.com/Mail/0/view
[6] http://mail.garbage-juice.com
--
users@sogo.nu
https://inverse.ca/sogo/lists
