Modify

Ticket #2803 (closed defect: invalid)

Opened 2 years ago

Last modified 2 years ago

Zarafa Ical core 2.0.17

Reported by: stuartiannaylor@… Owned by: jsalamero@…
Milestone: 2.0.X Component: zarafa
Severity: major Keywords: ical, zarafa, upgrade
Cc:

Description

On an upgrade to 2.0.17 from 2.0.16.

The zarafa ical gateway nolonger works. The ical gateway starts the correct ports are in the firewall but you receive a connection error whilst the logs seem empty.

Attachments

Change History

comment:1 Changed 2 years ago by jsalamero@…

  • Status changed from new to closed
  • Resolution set to invalid

Hi,

ICAL support wasn't added until last version so it's hard to believe it broke with the upgrade :)

 http://trac.zentyal.org/browser/branches/2.0/client/zarafa/ChangeLog

Check configuration on the webinterface and open the port in the firewall. If still not working have a look at /var/log/zarafa/ical.log and paste here the relevant lines.

comment:2 follow-up: ↓ 3 Changed 2 years ago by stuartiannaylor@…

Dunno I had it working in 2.0.17

I am using php icalendar that uses a cron job

wget --user=bookings --password=*  http://192.168.2.1:8008/ical/

I changed that to

wget --user=bookings --password=password --no-check-certificate  https://192.168.2.1:8443/ical/

All works now but the logs show the gateway connection stopped being logged exactly when I updated to 2.0.17

It still works as long as I use a secure connection.

The cron job was still running but on a standard connection to port 8008 a connection failure occurs

comment:3 in reply to: ↑ 2 Changed 2 years ago by stuartiannaylor@…

Replying to stuartiannaylor@…:

Dunno I had it working in 2.0.16 (should of said)

I am using php icalendar that uses a cron job

wget --user=bookings --password=*  http://192.168.2.1:8008/ical/

I changed that to

wget --user=bookings --password=password --no-check-certificate  https://192.168.2.1:8443/ical/

All works now but the logs show the gateway connection stopped being logged exactly when I updated to 2.0.17

It still works as long as I use a secure connection.

The cron job was still running but on a standard connection to port 8008 a connection failure occurs

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.