This is a replacement of the cloud, in case you want to sync/backup your files and have full control of the hosting environment.
See the project documentation for setup and configuration.
| Device | Is Supported |
|---|---|
| reMarkable 1 | ✅ |
| reMarkable 2 | ✅ |
| reMarkable Paper Pro | ✅ |
| reMarkable Paper Pro Move | ✅ |
The current release of rmfakecloud supports file synchronization up to reMarkable software 3.27.1. Newer releases have not been tested yet.
See the documentation for how to setup your device to use rmfakecloud.
| Features | Supported | Notes |
|---|---|---|
| File synchronization (1.0) | ✅ | |
| File synchronization (1.5, 2, 3, 4) | ✅ | |
| Send document by email | ✅ | |
| Handwriting recognition | ✅ | |
| Handwriting search | ❌ | |
| Screen sharing | ✅ | |
| Storage integrations | ✅ | |
| Integration with Dropbox | 🟡 | WIP |
| Integration with Google Drive | 🟡 | WIP |
| Integration with OneDrive | ❌ | |
| Integration with WebDAV | ✅ | Nextcloud, Owncloud, ... |
| Integration with FTP | ✅ | |
| Messaging integrations | ✅ | |
| Messaging integration through webhook | ✅ | |
| Calendar integration | ✅ | ICS currently supported |
| Messaging integration to Slack | 🟡 | Not directly, use a webhook with zapier/make/n8n |
| Archive document to cloud | 🟡 | It works but the information is not saved |
| Passcode (PIN) reset | ✅ | reMarkable 1 / reMarkable 2 only |
| Document rendering in web interface | ❌ | WIP |
STORAGE_URL should not be set (or only https://some.ho.st without a port should be used)/data will have to be manually moved to the user that will be createdsetuser -u user -s
or modify the profile and add sync15:true
a full resync will be needed (the tablet will do it), the old files are kept as they were and everything is put in a new directoryrun ./dev.sh which should start the UI and backend
synced:false prior to syncing (advisable just to disconnect, reconnect the cloud)check the connectivity between the tablet and the host: ping my.remarkable.com (should be localhost) ping local.remarkable.com (should be localhost) ping thehostpc wget -qO- http://host:3000 (or relevant ports, should get Working...) wget -qO- https://local.appspot.com (should get Working...)
check that the proxy is running and certs are installed:
echo Q | openssl s_client -connect localhost:443 -verify_hostname local.appspot.com -CAfile /etc/ssl/certs/ca-certificates.crt 2>&1 | grep Verify
You should see: Verify return code: 0 (ok)
if both (host and tablet) are on a wifi make sure "Client Isolation" is not activated on the AP
check if the proxy is configured correctly ``` systemctl status proxy
journalctl -u proxy
``
- check whether the CA cert was installed correctly
when doingupdate-ca-certificatesthere should have been1 added`
check the logs
check xochitls's logs, stop the service, start manually with more logging ``` systemctl stop xochitl QT_LOGGING_RULES=rm.network.*=true xochitl | grep -A3 QUrl
if you see *SSL Handshake failed* then something is wrong with the certs
- check sync logs
journalctl -u rm-sync
```
$ claude mcp add rmfakecloud \
-- python -m otcore.mcp_server <graph>