-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
url connection failure on org-caldav-check-dav but url works #209
Comments
This does seem to be be a bug in emacs auth-source or url stuff. See this reddit thread I found: https://www.reddit.com/r/emacs/comments/dct8vl/help_debug_orgcaldav_problems/ update: well, so far neither patching url-auth.el nor switching to emacs 28 made any difference. |
I had the same issue, but the issue is actually a bug in nextcloud 18.0.4, not in emacs. It affects Evolution and ios icalendar integration too, see: nextcloud/server#20624 The issue is now fixed in nextcloud master, but hasn't been pushed out. This pull request fixes the issue: nextcloud/server#20632 You can manually add the fix until nextcloud 18.0.5 rolls out. |
Thank You! I did not investigate nextcloud changes much because the curl command seemed to work. I really appreciate you responding. My sincere thanks. |
@alraban, thanks for pointing to the issue. I am running a snap version of nextcloud on ubuntu 18.04.
Anyone have ideas on how to pull the fix in? |
I don't know anything about snaps, but if you look at the pull request it's actually just a change to two lines of php in apps/dav/lib/Connector/Sabre/AnonymousOptionsPlugin.php. There are some more expansive changes to the test suite, but those aren't necessary to get things working again. So I just found the affected file at that location underneath my nextcloud root directory and edited those two lines. For a normal install the nextcloud root is typically whereever the webroot is (e.g. /var/www/ on debian), but I have no idea how snaps work or are structured. |
Thanks @alraban. It turns out that the snap file system is read-only, so I will ask over at the page of the snap maintainer. Looks like it has to wait for the snap to upgrade to 18.05, right? Is there an ETA for 18.05? |
It seems the only problem is the OPTIONS call. This is only done for initially checking a working DAV but is not actually needed for syncing. So in org-caldav-check-connection, if you comment out the line
you might be able to sync again. |
@dengste, many thanks. Yes that did it. Hopefully the snap will be updated to 18.05 before I upgrade org-caldav again. |
Upgrade to NextCloud 18.0.6 worked for me. I think this can be closed? |
I have a puzzling problem after nextcloud and emacs upgrades
I have successfully been using org-caldav to sync with my nextcloud calendars for about 1 year. I recently upgraded my machine (os, emacs and nextcloud changed) and I now have trouble, but only with org-caldav. Syncing my android devices works and sending OPTION request with
curl returns the correct DAV header information.
I assume this is probably due to some change in nextcloud but perhaps someone here can help me diagnose this?
System is Kubuntu 20.04, nextcloud 18.04, emacs 26.3, org-mode 9.6.3
The failure
The page returned is this:
But the calendar url works:
A clue?
.authinfo.gpg works for email, mu4e, etc and has always worked for org-caldav. But setting auth-source-debug t does not add information to the message buffer when I call org-caldav-sync. I do get messages from auth-source when using my email through mu4e. I've tried regular auth-source with .authinfo.gpg and auth-source-pass putting the secretes in a file named by host. same result.
Error backtrace from debug-on-error:
The text was updated successfully, but these errors were encountered: