Pusher stops after getting "403 forbidden" error

49 views
Skip to first unread message

Salman Zafar

unread,
Jun 14, 2016, 11:54:11 AM6/14/16
to Couchbase Mobile

CBLRestPusher stops syncing after encountering "403 forbidden" error. 


The logs are as follows - 

CBLMultipartUploader[PUT http://xxxxx:*****@xxxxxxxxx/<document_id>?new_edits=false]: Got error Error Domain=CBLHTTP Code=403 "403 forbidden" UserInfo={NSURL=http:/xxxxx:xxxxx@xxxxxxxxx/<document_id>?new_edits=false, NSLocalizedFailureReason=forbidden, NSLocalizedDescription=403 forbidden}


Replication: CBLRestPusher[http:/xxxxx:*****@xxxxxxx] took 0.330 sec; error=Error Domain=CBLHTTP Code=403 "403 forbidden" UserInfo={NSURL=http://xxxxx:xxxxx@xxxxxxxx/<document_id>?new_edits=false, NSLocalizedFailureReason=forbidden, NSLocalizedDescription=403 forbidden}


The only way for me to remove this problem is to have the particular document completely removed from everywhere. But all documents are important, and this is not a clean solution.


Has anyone else seen this same issue? How did you resolve it?

Is it an issue on couchbase lite or server? 


By the logs, it looks like there is an issue with the attachment. But I have not even touched the document, it was synced from server.

This issue is becoming a big blocker and keeps on coming again and again.


Complete solutions will be welcome.


Couchbase Lite - version 1.2

Couchbase Server - 4.1

Sync Gateway - 1.2.1

Jens Alfke

unread,
Jun 14, 2016, 12:56:14 PM6/14/16
to mobile-c...@googlegroups.com

On Jun 14, 2016, at 1:24 AM, Salman Zafar <salmanz...@gmail.com> wrote:

CBLRestPusher stops syncing after encountering "403 forbidden" error. 

Looks like a Couchbase Lite bug; a 403 shouldn’t stop the replication. Please file an issue on Github and we’ll investigate.

By the logs, it looks like there is an issue with the attachment. But I have not even touched the document, it was synced from server.

For whatever reason, the server is rejecting the document as invalid. Check the sync function (if you’re using Sync Gateway) or the validation function (if it’s CouchDB.)

—Jens
Reply all
Reply to author
Forward
0 new messages