problem with Google iCal Sync through cronjob

[snoeby]

Hi there

I'm trying to sync various Google Calendars with JEvents. Whilst everything works fine with a manual "refresh" I tried to get the sync working through a cronjob on our host.

Here's what I did:
1) Get the iCal Link of google
2) In JEvents link Google Kalender with iCal Link... works well
3) tested manual refresh, works well
4) created a cronjob with the following content:
/usr/local/bin/curl -o --url http://www.URL_To_Our_Website.COM/index ... als.reload > /dev/null 2>&1

The cronjob seems to run, but the calendar won't update... here's the cronjob output:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
100 106k 0 106k 0 0 58669 0 --:--:-- 0:00:01 --:--:-- 59319

so apparently something is running... but what... and why is the calendar not being updated?

Best regards!

[carcam]

Why are you using -o in the curl command without the output file where to write the results? Just change add a filename after the -o option to see what are you getting with the curl command or simply replace it with -s and check if it works.

[snoeby]

Hi carcam

I tried replacing in -o with -s ... the result is that it still doesn't work
But the cron deamon is sending me an email containing the HTML content of our website with the calendar view..

Any ideas?

[Geraint]

did you enable anonymous refresh of the calendar in JEvents backend?

[snoeby]

yes, the calendar is public, anonymous refresh is allowed (thus I know the URL to configure the cronjob) and even calendar viewing is public...

[Geraint]

what if you run the anon refresh URL in a webbrowser?

[snoeby]

In that case (running the anon refresh URL in a browser) I get a 403 error (not allowed to view the resource)

[snoeby]

as an add-on to the message above, just to be clear:
when I enter the anon url directly in a browser the html content of the 403-error message is NOT the same as when replacing the curl -o option with -s
using curl -s does NOT get a 403-error message....
hmm??

[Geraint]

If you get a 403 in the webbrowser then this is what google will get.

What does the URL look like?

[snoeby]

the URL is: http://www.snowboardregion-nordwest.ch/ ... als.reload

and the cronjob commands I've tried are:
/usr/local/bin/curl -o --url http://www.snowboardregion-nordwest.ch/ ... als.reload
> /dev/null 2>&1

/usr/local/bin/curl -s --url http://www.snowboardregion-nordwest.ch/ ... als.reload
> /dev/null 2>&1