Sync Failure, User Token Not Refreshed

[weary hawk]

Hardware: rm2
Firmware: 3.18.2.3
Cloud: rmfakecloud v0.0.24 via Docker in Kubernetes, via /etc/hosts override, no proxy on-device
Other mods: Syncthing installed via entware

Symptoms: Sync failures with "Unable to sync"

Logs:

Jun 01 13:02:00 reMarkable rm-sync[291]: rm.network.usertoken: UserToken: setting a new userToken (eyJhbGciOiJIUzI1NiIs...)
Jun 01 13:02:10 reMarkable xochitl[240]: 13:02:10.465 rm.network.usertoken     Scheduled token update at 2025-06-01 15:57:09.000000000, 10498534ms from now (scheduleUpdate /home/runner/work/xochitl/xochitl/src/xofm/libs/network/src/usertoken.cpp:133)

It seems that the scheduled user token update doesn't fire on time. If I restart the tablet or xochitl, the initial "immediate" token refresh runs and syncs are fine for ~3 hrs till that token expires.

Jun 01 16:09:33 reMarkable rm-sync[744]: rm.network.usertoken: Scheduled immediate token update

Time, date, timezone are all in sync between tablet and rmfakecloud, down to the second.

I've tried a re-pair, device reboots, rmfakecloud restarts, etc. Has anyone else seen this?

[fathom quartz]

You may want to report the issue on the rmfakecloud repo so that the maintainer can look into it.

[weary hawk]

I suspect it’s on the tablet side, I may swap over to the official cloud to see if I can replicate there

[fathom quartz]

If you can't replicate there, it may be a missing endpoint, or something missing from the current endpoints.

[weary hawk]

Yeah, it’s annoying to test, cause it takes hours for the old one to expire