Este site irá ter funcionalidade limitada enquanto fazemos manutenção para melhorar a sua experiência. Se um artigo não resolve o seu problema e quiser colocar uma questão, temos a nossa comunidade de apoio à espera de o ajudar em @FirefoxSupport no Twitter, /r/firefox no Reddit.

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Trouble with Baikal CalDAV server (Either "momentarily not available" or no password prompt)

  • 4 respostas
  • 1 tem este problema
  • 2 visualizações
  • Última resposta por nathan27

more options

My setup:

OS: Debian 11 (bullseye) Thunderbird version: 78.11.0 Install source: Debian repos

Summary:

I have a self-hosted instance Baikal (a WebDAV server). I have succesfully used two applications other than Thunderbird to sync to this server: vdirsyncer (CLI) and DAVx5 (Android), so I know the server is working.

I am having trouble subscribing to a calendar from this server with Thunderbird. The nature of the problem I encounter depends on what I've selected for Baikal's "WebDAV authentication type" config option.

When I choose "Digest" or "Apache", the problem is that Thunderbird never prompts me for a password. I can add the calendar and give it a name just fine, but the password prompt is never shown. When I switch to the calendar view, the calendar remains greyed out. When I click "ENABLE", the calendar flashes onto the window momentarily and then reverts to its original state.

When I choose "Basic", Thunderbird prompts me for a password, but then the calendar page shows a ⚠️ icon next to the calendar in question, and when I hover over it, the tooltip reads "The calendar Master is momentarily not available"

Details:

The setup dialog asks for a username and URL. I provide my DAV username; for the URL, I have tried both:

  • the generic Baikal DAV url (https://my.baikal.domain/dav.php)
  • the URL suggested in this official Baikal guide (https://my.baikal.domain/calendars/[username]/[calendarname]/)

The latter does NOT work to produce a password prompt on "Basic" authentication.

After I enter these details, the next dialog window asks me to name the calendar, and asks for an email address to associate with it. I have tried both leaving it blank and selecting the email address associated with my DAV account; the result is the same.

In one help thread I found online, someone suggested enabling the `calendar.network.multirealm` option in the config editor; I've tried this to no avail.

Thanks in advance for any help.

My setup: OS: Debian 11 (bullseye) Thunderbird version: 78.11.0 Install source: Debian repos Summary: I have a self-hosted instance Baikal (a WebDAV server). I have succesfully used two applications other than Thunderbird to sync to this server: vdirsyncer (CLI) and DAVx5 (Android), so I know the server is working. I am having trouble subscribing to a calendar from this server with Thunderbird. The nature of the problem I encounter depends on what I've selected for Baikal's "WebDAV authentication type" config option. When I choose "Digest" or "Apache", the problem is that Thunderbird never prompts me for a password. I can add the calendar and give it a name just fine, but the password prompt is never shown. When I switch to the calendar view, the calendar remains greyed out. When I click "ENABLE", the calendar flashes onto the window momentarily and then reverts to its original state. When I choose "Basic", Thunderbird prompts me for a password, but then the calendar page shows a ⚠️ icon next to the calendar in question, and when I hover over it, the tooltip reads "The calendar Master is momentarily not available" Details: The setup dialog asks for a username and URL. I provide my DAV username; for the URL, I have tried both: * the generic Baikal DAV url (https://my.baikal.domain/dav.php) * the URL suggested in this official Baikal guide (https://my.baikal.domain/calendars/[username]/[calendarname]/) The latter does NOT work to produce a password prompt on "Basic" authentication. After I enter these details, the next dialog window asks me to name the calendar, and asks for an email address to associate with it. I have tried both leaving it blank and selecting the email address associated with my DAV account; the result is the same. In one help thread I found online, someone suggested enabling the `calendar.network.multirealm` option in the config editor; I've tried this to no avail. Thanks in advance for any help.

Solução escolhida

correct unless you are using a commercial TLS certificate.

Ler esta resposta no contexto 👍 1

Todas as respostas (4)

more options

Calendar view is the only one that stands a chance of working. Next ensure that you are not using SSL/TLS connection encryption. Most self hosted servers use self signed certificates that are not trusted.

Then ensure the end point is for a calendar collection not a caldav collection.

more options

> Next ensure that you are not using SSL/TLS connection encryption.

Do you mean that my server must be accessible over http rather than https?

more options

Solução escolhida

correct unless you are using a commercial TLS certificate.

more options

I'm having this issue with a Let's Encrypt certificate. Are those also not supported?