Subscription to .ics calendar suddenly not showing

[Oliwally1]

I've been subscribing to a workplace read-only google calendar .ics for some years and it has always worked. Something like this:

https.....calendar.google.com/calendar/ical/...........calendar.google.com/private-........../basic.ics

But over the last two weeks the calendar is no longer showing (Thunderbird 78.11.0 64bit). I have unsubscribed and re-subscribed but to no avail. The entry is showing in my list of calendars, no error messages, but not showing any calendar entries/events.

Strangely, another, very similar google calendar from my workplace does show. Also an .ics link.

My workplace IT people have confirmed that no changes have been made to the calendar or any permissions.

Outlook has no trouble connecting to the same calendar subscription link, so the calendar is definitely still up and running (it better - the whole organisation relies on it )

I have the same Thunderbird setup on two laptops and the very same issue is showing on both, only for that particular calendar.

Is there a cache that I need to clear out or delete? How do I fix this problem?

Thanks for your help.

[tanstaafl]

1. This is a remote only calendar? i.e. you aren't synching a local and remote calendar?

2. Are you using CalDAV to connect to the calendar? If not, how are you connecting?

3. The problem still occurs if you temporarily disable all add-ons via help -> restart with add-ons disabled?

4. You can enable calendar.debug.log and calendar.debug.log.verbose in the config editor and then look at the error console in tools -> developer tools to see what it logged. That might give you a clue as to what's going on. Most calendar problems I read about are connection problems or the calendar not being listed. Connecting to the calendar and listing it but not retrieving its data is unusual.

I'd redirect this thread to the Calendar forum (where the calendar experts used to hang out) but that forum seems pretty dead nowadays.

https://www.reddit.com/r/Thunderbird/co ... tb_launch/ seems to describe a similar problem that was supposedly fixed in 78.5.0 but several users complain still occurs.

https://stackoverflow.com/questions/338 ... -lightning

[Oliwally1]

Thanks so much for helping out!

1. This is a remote only calendar? i.e. you aren't synching a local and remote calendar?

Yes, a remote calendar

2. Are you using CalDAV to connect to the calendar? If not, how are you connecting?

No, not using CalDAV. It always worked without this.... I just simply put in the address when creating a new calendar, using the 'on the network' option.

3. The problem still occurs if you temporarily disable all add-ons via help -> restart with add-ons disabled?

No, doesn't work even with add-ons disabled

4. You can enable calendar.debug.log and calendar.debug.log.verbose in the config editor and then look at the error console in tools -> developer tools to see what it logged. That might give you a clue as to what's going on. Most calendar problems I read about are connection problems or the calendar not being listed. Connecting to the calendar and listing it but not retrieving its data is unusual.

I played with this for a while but could not make much sense of the outputs.
There was a mention of 'calendar' but no reference to that particular calendar...

I'd redirect this thread to the Calendar forum (where the calendar experts used to hang out) but that forum seems pretty dead nowadays.

https://www.reddit.com/r/Thunderbird/co ... tb_launch/ seems to describe a similar problem that was supposedly fixed in 78.5.0 but several users complain still occurs.

https://stackoverflow.com/questions/338 ... -lightning

I'll have a look at those to see how I go. Thanks very much for helping out.

[Oliwally1]

Hmm... I've poked and prodded and looked around for solutions, but I am not making any headway. I even have the same problem on my Linux laptop running Thunderbird.

How do I produce an error log that may tell me a little more? I'm new to this so would need detailed instructions and what to look for in the log.

Thanks again for helping out.