Skip to content
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.

failed to build documents tree, last error: failed to fetch document tree request failed with status 500 #274

Closed
edef1c opened this issue Nov 17, 2022 · 23 comments

Comments

@edef1c
Copy link

edef1c commented Nov 17, 2022

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.

edef@jaguar ~> rmapi
ERROR: 2022/11/17 12:39:42 main.go:43: failed to build documents tree, last error: failed to fetch document tree request failed with status 500
edef@jaguar ~ [1]> rmapi ls
ERROR: 2022/11/17 12:39:48 main.go:43: failed to build documents tree, last error: failed to fetch document tree request failed with status 500
@edef1c
Copy link
Author

edef1c commented Nov 17, 2022

Reproduces for me on master.

@ddvk
Copy link
Collaborator

ddvk commented Nov 17, 2022

run it with RMAPI_TRACE=1 and see if you can get more detail on the error

@ddvk
Copy link
Collaborator

ddvk commented Nov 20, 2022

I have the same error, it seems that they started migrating stuff, but not all accounts. Even the desktop app can't connect anymore

@ymendel
Copy link

ymendel commented Nov 20, 2022

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.

@edef1c
Copy link
Author

edef1c commented Nov 20, 2022

run it with RMAPI_TRACE=1 and see if you can get more detail on the error

Tokens censored, but the rest is verbatim:

Trace: 2022/11/20 22:59:51 transport.go:177: request: GET /document-storage/json/2/docs HTTP/1.1
Host: document-storage-production-dot-remarkable-production.appspot.com
Authorization: Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
User-Agent: rmapi

 <nil>
Trace: 2022/11/20 22:59:51 transport.go:190: HTTP/2.0 500 Internal Server Error
Content-Length: 323
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
Content-Type: text/html; charset=UTF-8
Date: Sun, 20 Nov 2022 22:59:51 GMT
Server: Google Frontend


<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>500 Server Error</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Server Error</h1>
<h2>The server encountered an error and could not complete your request.<p>Please try again in 30 seconds.</h2>
<h2></h2>
</body></html>
 <nil>
Trace: 2022/11/20 22:59:51 transport.go:194: request failed with status 500
Trace: 2022/11/20 22:59:51 main.go:36: failed to fetch document tree request failed with status 500
Trace: 2022/11/20 22:59:51 transport.go:177: request: POST /token/json/2/user/new HTTP/1.1
Host: webapp-production-dot-remarkable-production.appspot.com
Authorization: Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
User-Agent: rmapi

 <nil>
Trace: 2022/11/20 22:59:52 transport.go:190: HTTP/2.0 200 OK
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
Cache-Control: private
Content-Type: text/plain; charset=utf-8
Date: Sun, 20 Nov 2022 22:59:52 GMT
Server: Google Frontend
Vary: Accept-Encoding
X-Cloud-Trace-Context: 18ea1896d386ed0b9b4937a3c478fc1d
X-Ratelimit-Limit: 5
X-Ratelimit-Remaining: 3
X-Ratelimit-Reset: 17

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx <nil>
Trace: 2022/11/20 22:59:52 auth.go:53: user token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Trace: 2022/11/20 22:59:52 transport.go:177: request: GET /document-storage/json/2/docs HTTP/1.1
Host: document-storage-production-dot-remarkable-production.appspot.com
Authorization: Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
User-Agent: rmapi

 <nil>
Trace: 2022/11/20 22:59:52 transport.go:190: HTTP/2.0 500 Internal Server Error
Content-Length: 323
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
Content-Type: text/html; charset=UTF-8
Date: Sun, 20 Nov 2022 22:59:52 GMT
Server: Google Frontend


<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>500 Server Error</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Server Error</h1>
<h2>The server encountered an error and could not complete your request.<p>Please try again in 30 seconds.</h2>
<h2></h2>
</body></html>
 <nil>
Trace: 2022/11/20 22:59:52 transport.go:194: request failed with status 500
Trace: 2022/11/20 22:59:52 main.go:36: failed to fetch document tree request failed with status 500
Trace: 2022/11/20 22:59:52 transport.go:177: request: POST /token/json/2/user/new HTTP/1.1
Host: webapp-production-dot-remarkable-production.appspot.com
Authorization: Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
User-Agent: rmapi

 <nil>
Trace: 2022/11/20 22:59:52 transport.go:190: HTTP/2.0 200 OK
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
Cache-Control: private
Content-Type: text/plain; charset=utf-8
Date: Sun, 20 Nov 2022 22:59:52 GMT
Server: Google Frontend
Vary: Accept-Encoding
X-Cloud-Trace-Context: 6aafee73a88305f118775905a6746014
X-Ratelimit-Limit: 5
X-Ratelimit-Remaining: 2
X-Ratelimit-Reset: 29

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx <nil>
Trace: 2022/11/20 22:59:52 auth.go:53: user token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Trace: 2022/11/20 22:59:52 transport.go:177: request: GET /document-storage/json/2/docs HTTP/1.1
Host: document-storage-production-dot-remarkable-production.appspot.com
Authorization: Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
User-Agent: rmapi

 <nil>
Trace: 2022/11/20 22:59:52 transport.go:190: HTTP/2.0 500 Internal Server Error
Content-Length: 323
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
Content-Type: text/html; charset=UTF-8
Date: Sun, 20 Nov 2022 22:59:52 GMT
Server: Google Frontend


<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>500 Server Error</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Server Error</h1>
<h2>The server encountered an error and could not complete your request.<p>Please try again in 30 seconds.</h2>
<h2></h2>
</body></html>
 <nil>
Trace: 2022/11/20 22:59:52 transport.go:194: request failed with status 500
Trace: 2022/11/20 22:59:52 main.go:36: failed to fetch document tree request failed with status 500
ERROR: 2022/11/20 22:59:52 main.go:43: failed to build documents tree, last error: failed to fetch document tree request failed with status 500

@edef1c
Copy link
Author

edef1c commented Nov 20, 2022

I have the same error, it seems that they started migrating stuff, but not all accounts. Even the desktop app can't connect anymore

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.

@ddvk
Copy link
Collaborator

ddvk commented Nov 26, 2022

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

@edef1c
Copy link
Author

edef1c commented Dec 2, 2022

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?

@ddvk
Copy link
Collaborator

ddvk commented Dec 2, 2022

re-pair of the device (tablet)

@martin-braun
Copy link

@ddvk Did that, but I have problems.

  1. The instructions say to get the code from https://my.remarkable.com/device/desktop/ which doesn't work, I only get a white site. I surpassed the problem by simple attempting to pair the regular desktop app to get a code, but there is another problem, which is
  2. I'm getting "auth.go:50: failed to create user token from device token request failed with status 429" and afterwards "main.go:42: failed to build documents tree, last error: failed to fetch document tree request failed with status 500", now

Re-pairing did not solve the problem for me.

@ddvk
Copy link
Collaborator

ddvk commented Dec 5, 2022

@ddvk Did that, but I have problems.

  1. The instructions say to get the code from https://my.remarkable.com/device/desktop/ which doesn't work, I only get a white site. I surpassed the problem by simple attempting to pair the regular desktop app to get a code, but there is another problem, which is

  2. I'm getting "auth.go:50: failed to create user token from device token request failed with status 429" and afterwards "main.go:42: failed to build documents tree, last error: failed to fetch document tree request failed with status 500", now

Re-pairing did not solve the problem for me.

unpair the tablet (via the web interface or from the tablet)
then pair it and then try pairing rmapi

@isovector
Copy link

isovector commented Dec 17, 2022

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.

@isovector
Copy link

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.

@edef1c
Copy link
Author

edef1c commented Dec 18, 2022

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.
I've just updated to 2.15.1.1189, and…

edef@jaguar ~> rmapi
WARNING!!! Using the new 1.5 sync, this has not been fully tested yet!!! first sync can be slow
ReMarkable Cloud API Shell
[/]>

That's very working! It has also resolved some weird syncing issues I've been having on the device.
Maybe we can add a hint to update your firmware if it can't build the directory tree?

@edef1c
Copy link
Author

edef1c commented Dec 18, 2022

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?

@posita
Copy link

posita commented Dec 20, 2022

I am running rmapi v0.0.22.1 (latest) and my reMarkable2 is running 2.15.1.1189 (also latest). I started getting this error suddenly. I unpaired and repaired the device. I removed my existing desktop token via my.remarkable.com and now am getting the following repeatedly:

% RMAPI_TRACE=1 rmapi ls
Trace: 2022/12/19 20:27:28 config.go:61: config fail /home/<redacted>/.config/rmapi/rmapi.conf doesn't exist/n
Enter one-time code (go to https://my.remarkable.com/device/desktop/connect): <redacted>
Trace: 2022/12/19 20:27:37 transport.go:177: request: POST /token/json/2/device/new HTTP/1.1
Host: webapp-production-dot-remarkable-production.appspot.com
Authorization: Bearer
User-Agent: rmapi

{"code":"<redacted>","deviceDesc":"desktop-linux","deviceID":"<redacted>"} <nil>
Trace: 2022/12/19 20:27:38 transport.go:190: HTTP/2.0 500 Internal Server Error
Content-Length: 323
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
Content-Type: text/html; charset=UTF-8
Date: Tue, 20 Dec 2022 02:27:38 GMT
Server: Google Frontend


<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>500 Server Error</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Server Error</h1>
<h2>The server encountered an error and could not complete your request.<p>Please try again in 30 seconds.</h2>
<h2></h2>
</body></html>
 <nil>
Trace: 2022/12/19 20:27:38 transport.go:194: request failed with status 500
ERROR: 2022/12/19 20:27:38 auth.go:93: failed to create a new device token

@morewithout
Copy link

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.

@posita
Copy link

posita commented Dec 20, 2022

I wonder if splitbrain/ReMarkableAPI#36 is related?

@dancorne
Copy link

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...

@ddvk
Copy link
Collaborator

ddvk commented Dec 21, 2022

the auth url did change but this is only in master, we have to create a new release

@posita
Copy link

posita commented Dec 21, 2022

I can verify that I was able to (re)connect and perform operations with v0.0.23. Thanks for the quick fix! 🙇

@morewithout
Copy link

Same here. Thanks :-)

@ddvk
Copy link
Collaborator

ddvk commented Jan 1, 2023

should work now

@ddvk ddvk closed this as completed Jan 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants