I renamed caldb.sqlite.bak to caldb.sqlite, and I made the system the master.
I still get an error message when I click the calendar button in SurgeWeb:
Cal Request Failed: 401 Unauthorized
I have port 80 blocked and always used port 7443 on the (now dead) master.
When I try https://myserver.com:7443/cal my login is not accepted and I get this error message when I leave the login window:
Sabre_DAV_Exception_NotAuthenticated No basic authentication headers were found 1.6.2
In the cal.log file:
01/08/18 22:44:02 [27148] NETWIN NetWin Info Test BEGIN
01/08/18 22:44:02 [27148] NETWIN NetWin Info Test END
01/08/18 22:45:53 [27160] ----
01/08/18 22:45:53 [27160] Sabre CAL
01/08/18 22:45:53 [27160] need auth beforeMethod [GET-]
01/08/18 22:45:53 [27160] Sabre CAL END
01/08/18 22:45:53 [27162] ----
01/08/18 22:45:53 [27162] Sabre CAL
01/08/18 22:45:53 [27162] need auth beforeMethod [GET-]
01/08/18 22:45:53 [27162] Sabre CAL END
01/08/18 22:46:17 [27167] ----
01/08/18 22:46:17 [27167] Sabre CAL
01/08/18 22:46:17 [27167] need auth beforeMethod [GET-]
01/08/18 22:46:17 [27167] Sabre CAL END
01/08/18 22:46:33 [27169] ----
01/08/18 22:46:33 [27169] Sabre CAL
01/08/18 22:46:33 [27169] need auth beforeMethod [GET-]
01/08/18 22:46:33 [27169] NWAUTH user=john@wilkes.com pass={hidden} hash=1c74855d13c34eb9421fcbc4d47a1192
01/08/18 22:46:33 [27169] NWAUTH Cached login expired (john@wilkes.com) age=399607/1800
01/08/18 22:46:33 [27169] No cached login, trying IMAP
01/08/18 22:46:33 [27169] Imap login exception imap_open(): Couldn't open stream {127.0.0.1:143/notls}INBOX
01/08/18 22:46:33 [27169] NWAUTH authorised=[NO]
01/08/18 22:46:33 [27169] Sabre CAL END
01/08/18 22:46:38 [27172] ----
01/08/18 22:46:38 [27172] Sabre CAL
01/08/18 22:46:38 [27172] need auth beforeMethod [GET-]
01/08/18 22:46:38 [27172] Sabre CAL END
--
John Wilkes
john@wilkes.com
> On Jan 8, 2018, at 1:04 PM, Surgemail Support (Marijn) <surgemail-support@netwinsite.com> wrote:
>
> X-SpamDetect-Info: ------------- Start ASpam results ---------------
> X-SpamDetect-Info: This message may be spam. This message BODY has been altered to show you the spam information
> X-SpamDetect: ****: 4.1 sd=4.1 0.68(X-Verify-Helo:-ERR) 0.40(X-myrbl:Color=orange) [nnot=0,ng=0,nsum=0,nb=0,nw=0,0.13]
> X-SpamDetect-Info: ------------- End ASpam results -----------------
>
>
> Calendaring data is not "live mirrorred" but copied once per day from the master to the slave for backup puposes as caldb.sqlite.bak. This is the reason calendaring is normally disabled on the slave. In order to enable calendaring on on the mirror:
>
> 1) copy / rename surgemail/scripts/data/caldb.sqlite.bak to surgemail/scripts/data/caldb.sqlite
>
> 2) either make the system the master, OR comment out this check in surgemail/scripts/cal.php
>
> //if(getenv("CLUSTER_MASTER")!='TRUE'){
> // print("ERROR: calendaring can only be used on the MASTER of a mirrorred cluster");
> // return;
> //}
>
> Marijn
>
>
>
> On Tuesday 09/01/2018 at 5:36 am, John Wilkes wrote:
>> I installed the php modules that CalDAV needs and when I tried to “verify authentication integration” I got an error message that calendaring is available on the master only.
>>
>> I changed g_mirror_mode to “MASTER” in the (former) mirror’s surgemail.ini, shutdown the mirror and restarted.
>>
>> Now when I verify authentication integration I get the login popup, but it does not accept my password.
>>
>> If I try to see my calendar in SurgeWeb, I get an error message: Cal Request Failed: 401 Unauthorized
>>
>> What do I need to do to fix this?
>>
>> Thanks,
>> John
>>
>> —
>> john@wilkes.com
>>
>>
>>
>>> On Jan 7, 2018, at 5:11 PM, John Wilkes <john@wilkes.com> wrote:
>>>
>>> I have a mirror setup, and I use the caldav and carddav on my server. Are calendar and contacts mirrored?
>>>
>>> My server disk drive failed, and I am currently running on the mirror (still as a “slave”) while I organize a new server system, but I don’t see my calendar in SurgeWeb, just a blank blue page, and the only contacts are those to whom I have sent email while running on the mirror.
>>>
>>> Thanks,
>>> John
>>>
>>> —
>>> john@wilkes.com
>>
>>
>
>
|
