Http 405 not allowed



  • Hi
    Been using DAVx5 for a while with synology nas and it was all fine until last week. I think there was an update and now all I get is an error and no sync.

    Here is the debug, it looks like the http request has changed an so now gets a not allowed response. Nothing has changed on the nas and now all our devices have the same not allowed error.

    — BEGIN DEBUG INFO —
    Account name: Keith@local.host
    Authority: com.android.calendar

    HTTP REQUEST:
    Request{method=PROPFIND, url=https://192.168.1.94:5001/caldav.php/Keith/home/, tags={}}
    <?xml version=‘1.0’ encoding=‘UTF-8’ ?><propfind xmlns=“DAV:” xmlns:CAL=“urn:ietf:params:xml:ns:caldav” xmlns:CARD=“urn:ietf:params:xml:ns:carddav”><prop><supported-report-set /><n0:getctag xmlns:n0=“http://calendarserver.org/ns/” /><sync-token /></prop></propfind>

    HTTP RESPONSE:
    Response{protocol=http/1.1, code=405, message=Not Allowed, url=https://192.168.1.94:5001/caldav.php/Keith/home/}
    <html>
    <head><title>405 Not Allowed</title></head>
    <body>
    <center><h1>405 Not Allowed</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>

    REMOTE RESOURCE:
    https://192.168.1.94:5001/caldav.php/Keith/home/

    EXCEPTION:
    at.bitfire.dav4jvm.exception.HttpException: HTTP 405 Not Allowed
    at at.bitfire.dav4jvm.DavResource.checkStatus(DavResource.kt:364)
    at at.bitfire.dav4jvm.DavResource.checkStatus(DavResource.kt:338)
    at at.bitfire.dav4jvm.DavResource.processMultiStatus(DavResource.kt:432)
    at at.bitfire.dav4jvm.DavResource.propfind(DavResource.kt:325)
    at at.bitfire.davdroid.syncadapter.CalendarSyncManager$queryCapabilities$1.invoke(CalendarSyncManager.kt:65)
    at at.bitfire.davdroid.syncadapter.CalendarSyncManager$queryCapabilities$1.invoke(CalendarSyncManager.kt:42)
    at at.bitfire.davdroid.syncadapter.SyncManager.useRemote(SyncManager.kt:809)
    at at.bitfire.davdroid.syncadapter.SyncManager.useRemoteCollection(SyncManager.kt:830)
    at at.bitfire.davdroid.syncadapter.CalendarSyncManager.queryCapabilities(CalendarSyncManager.kt:63)
    at at.bitfire.davdroid.syncadapter.SyncManager$performSync$1.invoke(SyncManager.kt:121)
    at at.bitfire.davdroid.syncadapter.SyncManager$performSync$1.invoke(SyncManager.kt:53)
    at at.bitfire.davdroid.syncadapter.SyncManager.unwrapExceptions(SyncManager.kt:835)
    at at.bitfire.davdroid.syncadapter.SyncManager.performSync(SyncManager.kt:112)
    at at.bitfire.davdroid.syncadapter.CalendarsSyncAdapterService$CalendarsSyncAdapter.sync(CalendarsSyncAdapterService.kt:55)
    at at.bitfire.davdroid.syncadapter.SyncAdapterService$SyncAdapter.onPerformSync(SyncAdapterService.kt:86)
    at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:272)

    SOFTWARE INFORMATION

    • at.bitfire.davdroid 2.4.0.1-gplay (280) from com.android.vending
    • org.dmfs.tasks 1.1.18 (74800) from com.android.vending
    • com.android.providers.contacts 2.0.50 (205000000)
    • com.android.providers.calendar 1.0.00.35 (100000035)
    • com.samsung.android.contacts 3.8.25.22 (382500022)
    • com.samsung.android.calendar 4.4.04.7 (440400007) from com.sec.android.app.samsungapps
    • com.trtf.blue 1.9.5.36 (14870) from com.android.vending

    CONNECTIVITY (at the moment)
    Active connection: WiFi, CONNECTED

    CONFIGURATION
    Power saving disabled: yes
    android.permission.READ_CONTACTS: granted
    android.permission.WRITE_CONTACTS: granted
    android.permission.READ_CALENDAR: granted
    android.permission.WRITE_CALENDAR: granted
    org.dmfs.permission.READ_TASKS: granted
    org.dmfs.permission.WRITE_TASKS: granted
    android.permission.ACCESS_COARSE_LOCATION: denied
    System-wide synchronization: automatically
    Account: Keith@local.host
    Address book sync. interval: 240 min
    Calendar sync. interval: 240 min
    OpenTasks sync. interval: manually
    WiFi only: false
    [CardDAV] Contact group method: GROUP_VCARDS
    [CalDAV] Time range (past days): 90
    Manage calendar colors: true
    Use event colors: false

    SQLITE DUMP
    android_metadata
    | locale |
    | en_GB |

    services
    | _id | accountName | service | principal |
    | 4 | Keith@local.host | carddav | https://192.168.1.94:5001/caldav.php/Keith/ |
    | 5 | Keith@local.host | caldav | https://192.168.1.94:5001/caldav.php/Keith/ |

    sqlite_sequence
    | name | seq |
    | services | 5 |
    | homesets | 25 |
    | collections | 14 |

    homesets
    | _id | serviceID | url |
    | 20 | 5 | https://192.168.1.94:5001/caldav.php/Keith/ |
    | 21 | 5 | https://192.168.1.94:5001/caldav.php/group%3D%3Dhttp/ |
    | 22 | 5 | https://192.168.1.94:5001/caldav.php/group%3D%3Dusers/ |
    | 23 | 4 | https://192.168.1.94:5001/caldav.php/Keith/ |
    | 24 | 4 | https://192.168.1.94:5001/caldav.php/group%3D%3Dhttp/ |
    | 25 | 4 | https://192.168.1.94:5001/caldav.php/group%3D%3Dusers/ |

    collections
    | _id | serviceID | type | url | privWriteContent | privUnbind | forceReadOnly | displayName | description | color | timezone | supportsVEVENT | supportsVTODO | source | sync |
    | 12 | 5 | CALENDAR | https://192.168.1.94:5001/caldav.php/Keith/Keith Admin--rftpl/ | 1 | 1 | 0 | FamilyCalendar | Our calendar | -439477 | <null> | 1 | 0 | <null> | 1 |
    | 13 | 5 | CALENDAR | https://192.168.1.94:5001/caldav.php/Keith/home/ | 1 | 1 | 0 | My Calendar | <null> | -1852160 | <null> | 1 | 0 | <null> | 1 |
    | 14 | 5 | CALENDAR | https://192.168.1.94:5001/caldav.php/Keith/home_todo/ | 1 | 1 | 0 | Inbox | <null> | <null> | <null> | 0 | 1 | <null> | 0 |

    SYSTEM INFORMATION
    Android version: 8.0.0 (R16NW.T820XXU2BRL1)
    Device: samsung SM-T820 (gts3lwifi)

    — END DEBUG INFO —


  • developer

    DAVx5 hasn’t changed sync requests for a long time. This looks like a server error. Do other clients still work? Also, the DAVx5 latest version is 2.5, please try with it (but I guess the problem will persist, because its probably not a DAVx5 problem).



  • Thanks - it turns out that the caldav service on the synology had failed. It all came back to life after a reboot.


  • developer

    Thanks for the update!


Log in to reply
 

Similar topics