rmfakecloud

Open source

host your own cloud for the remarkable

1.3K stars0 likes1 views

About

host your own cloud for the remarkable

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.

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

For SW >= 3.15 STORAGE_URL should not be set (or only https://some.ho.st without a port should be used)
after v0.0.3 the files in /data will have to be manually moved to the user that will be created
with v0.0.5 the new diff sync15 is added as an option, in order to use it modify the user with setuser -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 directory

run ./dev.sh which should start the UI and backend

(applies when you don't have security, version &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

#or

journalctl -u proxy

check whether the CA cert was installed correctly when doing update-ca-certificates there should have been 1 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
```