-
Notifications
You must be signed in to change notification settings - Fork 97
failed to build documents tree, last error: failed to fetch document tree request failed with status 500 #274
Comments
Reproduces for me on master. |
run it with RMAPI_TRACE=1 and see if you can get more detail on the error |
I have the same error, it seems that they started migrating stuff, but not all accounts. Even the desktop app can't connect anymore |
Interestingly, I was getting a 429, but now I'm getting a 500. That sounds more like something is just going wrong with their servers, but it could be a different manifestation of the same problem. |
Tokens censored, but the rest is verbatim:
|
Either my reMarkable itself can't synchronise, or the desktop app doesn't work anymore (or both!), so this doesn't seem to be unique to rmapi indeed. |
I wrote to support that my desktop app can't sync. Then after they answered with the usual, turn it off and on again, unpairing and pairing it magically started using sync 1.5 |
Is this re-pairing the device or the desktop app? |
re-pair of the device (tablet) |
@ddvk Did that, but I have problems.
Re-pairing did not solve the problem for me. |
unpair the tablet (via the web interface or from the tablet) |
This is happening to me too; tried repairing the device and rmapi, neither helped. EDIT: The Read on Remarkable chrome extension also fails; it seems like perhaps my account is in some weird state. EDIT: Fixed below. |
Aha, I found a fix. My remarkable was running firmware 2.11.something; updating it to 2.15.1.1189 forced an entire resync of the device, and rmapi no longer crashes. |
Ah, I've been running 2.5.0.27 all this time, since I have a bunch of Toltec stuff installed and have auto-update disabled.
That's very working! It has also resolved some weird syncing issues I've been having on the device. |
NB, I did re-pair the device (and rmapi) prior to the update. Maybe the next one coming through can try doing just the firmware update to see if that does the trick alone? |
I am running
|
I have the exact same problem as the immediately prior post from posita. I was about to post the same trace. I first noticed it yesterday on two different reMarkable accounts using two different tablets running 2.15.1.1189 on three different desktops - two Linux (Chromebooks) and one Mac. All had been working perfectly for over a year. I've tried all suggestions in this thread to no avail. I guess reMarkable have changed something in their Cloud/API? I'm happy to help with testing any potential fixes. Thanks in antiicipation. |
I wonder if splitbrain/ReMarkableAPI#36 is related? |
I started having this issue a couple of days ago. My tablet was updated to v3 last night, which I'm guessing was related. Still getting a 500 response when trying to re-authenticate with a one-time code now, maybe they've changed the service endpoint for the version 3 rollout or something like that... |
the auth url did change but this is only in master, we have to create a new release |
I can verify that I was able to (re)connect and perform operations with v0.0.23. Thanks for the quick fix! 🙇 |
Same here. Thanks :-) |
should work now |
rmapi had been working fine for me, but at some point it just fully stopped working.
Even with a fresh login token (had to delete my old tokens, or
rmapi login
yielded status 429), nothing much changes. No puts, no gets.I upgraded to 0.0.22.1 to no avail.
The text was updated successfully, but these errors were encountered: