This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

TB 128.x How to publish calendar to webDAV url.

  • 1 eyano
  • 0 eza na bankokoso oyo
  • 1 view
  • Eyano yasuka ya Cbhihe

more options

Hello @all: I run TB 128 on up to date Archlinux with gdm. I want to publish one of my TB calendars to a network volume to which a group of people will have consult access. For that the sequence of step is:

  1. Click Events and Tasks.
  2. Click Publish.
  3. Click the calendar you want to publish, and click OK. (A small window appears with a url field to complete)
  4. Enter your WebDAV url. 

The issue is when I enter the WebDAV url. My url for the particular (already existing) directory I want to publish to is:

   davs://b2drop.mydomain/remote.php/webdav/Calendars/

Trial 1 I enter the above url in the appropriate field of the small window and .... nothing happens. I cannot click the "Publish" button in the small url field window, because it is grayed out. Trial 2 I tried to modify the URL so the publish button would become active. That happened when using:

   https://b2drop.mydomain/remote.php/webdav/Calendars/

In that case the username and password are requested. I enter them and I get an error message:

  "Error: Publishing the calendar file failed. Status code: 401: Unauthorized"

Trial 3 I go to my remote b2drop.domain volume and secure the actual link that point to the still empty directory, copy-paste it as

   https://b2drop.domain/index.php/s/sCHzHY95kPEC4Gi

in the url field, click Publish, ... and nothing happens.

I am probably missing something basic. Any pointer anyone ?

Hello @all: I run TB 128 on up to date Archlinux with gdm. I want to publish one of my TB calendars to a network volume to which a group of people will have consult access. For that the sequence of step is: 1. Click Events and Tasks. 2. Click Publish. 3. Click the calendar you want to publish, and click OK. (A small window appears with a url field to complete) 4. Enter your WebDAV url. The issue is when I enter the WebDAV url. My url for the particular (already existing) directory I want to publish to is: davs://b2drop.mydomain/remote.php/webdav/Calendars/ '''Trial 1''' I enter the above url in the appropriate field of the small window and .... nothing happens. I cannot click the "Publish" button in the small url field window, because it is grayed out. '''Trial 2''' I tried to modify the URL so the publish button would become active. That happened when using: https://b2drop.mydomain/remote.php/webdav/Calendars/ In that case the username and password are requested. I enter them and I get an error message: "Error: Publishing the calendar file failed. Status code: 401: Unauthorized" '''Trial 3''' I go to my remote b2drop.domain volume and secure the actual link that point to the still empty directory, copy-paste it as https://b2drop.domain/index.php/s/sCHzHY95kPEC4Gi in the url field, click Publish, ... and nothing happens. I am probably missing something basic. Any pointer anyone ?

All Replies (1)

more options

Trial 4 Rather than publishing my local calendar to a remote network empty volume (as publishing to an empty WebDAV volume seems weird), I went to my remote Webdav calendar, created a new empty calendar My_calendar, then copy-pasted the corresponding WebDAV-ICS-URL into the same WebDAV url field as before. Logically at that point, I am asked or my credentials, which once entered yield:

  "Error: Publishing the calendar file failed. Status code: 403: Forbidden"

Ezalaki modifié na Cbhihe

Helpful?

Tuna motuna

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.