Sync seems to work partially, looking for help and alternatives #354

jpmvferreira · 2025-03-08T12:08:42Z

jpmvferreira
Mar 8, 2025

I've been using rmfakecloud as an off-site backup in case something happens to my Remarkable2 on my own personal server. The setup uses Wireguard behind the scene not to expose rmfakecloud to the world.

I've checked the WebUI and some things are inconsistent:

Files that I have already deleted weeks/months ago are still showing up as there;
However, files that were added after deleting the previous files are there;
Notebooks that have had updates very recently show very old dates and newer notebooks aren't there.

It is clear something is wrong with the sync, especially given that rmfakecloudctl reports

# rmfakecloudctl status
Status: enabled (active)
Upstream server: http://10.1.1.1 (invalid)
Run `rmfakecloudctl disable` to disable rmfakecloud-proxy.
Run `rmfakecloudctl set-upstream https://<server>` to set the upstream server.

it also fails the following check

# echo Q | openssl s_client -connect localhost:443  -verify_hostname local.appspot.com -CAfile /etc/ssl/certs/ca-certificates.crt 2>&1 | grep Verify

and some funky behavior which I cannot explain:

# systemctl status xochitl
● xochitl.service - reMarkable main application
     Loaded: loaded (/lib/systemd/system/xochitl.service; disa
bled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/xochitl.service.d
             └─toltec-wrapper.conf
     Active: inactive (dead)

# systemctl status proxy
Unit proxy.service could not be found.

It is probably and issue on my end, but I don't remember doing anything after I left rmfakecloud working.

Anyways, there's two options for me, which I would like to get some feedback from the community:

Fix rmfakecloud and avoid screwing up next time;
Reset the device, install rclone, synchronize it with any cloud provider and avoid running a web server.

If anybody has another alternative which works well for them and is very stable (the feature which I surely value the most), please do let me know!

Eeems · 2025-03-08T16:49:05Z

Eeems
Mar 8, 2025

It looks like you installed rmfakecloud proxy with toltec and are using a launcher, my guess is oxide.

rmfakecloudctl appears to be pointing you at the issue. The upstream you set isn't valid. You'll need to troubleshoot why that url isn't working. Likely something is wrong with your wireguard configuration.

What OS version are you running?

12 replies

Eeems Apr 7, 2025

In toltec the unit is rmfakecloud-proxy which is in the rmfakecloudctl output.
Based on the output you provided, the connection is being refused, so it isn't an issue with TLS, but with the proxy accepting connections.

You cannot skip the TLS side of things here, as all you are doing is providing a MITM proxy to redirect traffic to your rmfakecloud instance, and the app requires the protocol to be HTTPS.

8000

jpmvferreira Apr 13, 2025
Author

Thanks for the explanation, as I said, I'm not very knowledgeable when its comes to networking.
And you are correct, the proxy isn't unable to connect to the server for some reason

# systemctl status rmfakecloud-proxy
Apr 05 15:33:32 pergaminho systemd[1]: Started rmfakecloud reverse proxy.
Apr 05 15:33:32 pergaminho rmfakecloud-proxy[230]: 2025/04/05 15:33:32 cert-file=/opt/var/rmfakecloud-proxy/rmfakecloud-proxy.bundle.crt key-file=/opt/var/rmfakecloud-proxy/rmfakecloud-proxy.key listen-addr=127.0.
42.10:443 upstream-url=http://10.1.1.1
Apr 05 15:34:23 pergaminho rmfakecloud-proxy[230]: 2025/04/05 15:34:23 http: proxy error: dial tcp 10.1.1.1:80: i/o timeout
Apr 05 15:34:58 pergaminho rmfakecloud-proxy[230]: 2025/04/05 15:34:58 http: proxy error: dial tcp 10.1.1.1:80: i/o timeout
Apr 05 15:35:37 pergaminho rmfakecloud-proxy[230]: 2025/04/05 15:35:37 http: proxy error: dial tcp 10.1.1.1:80: i/o timeout

Although I can wget 10.1.1.1:80, which is a Wireguard IP, and get the webpage index.html.

I've restarted the unit, the error is gone but the issue remains.

Eeems Apr 13, 2025

Based on the OpenSSL error, the proxy is refusing connection. So it's not that it can't connect to the upstream, it's that it's not letting you connect to it. Are you getting the same output when running openssl?

jpmvferreira Apr 18, 2025
Author

You cannot skip the TLS side of things here, as all you are doing is providing a MITM proxy to redirect traffic to your rmfakecloud instance, and the app requires the protocol to be HTTPS.

I've checked my config, and TLS is not configured, it's commented out on my configuration file.
I don't remember ever setting it up.
In the documentation, the default configuration file has a comment saying uncomment if using TLS, which I interpreted as being something optional.

So should I create a key and a certificate and uncomment this portion of the configuration file?

Eeems Apr 19, 2025

I think we are talking past each other here. The TLS configuration for the rmfakecloud-proxy on your device which is auto installed and configured by installing the package with toltec where all you do is use rmfakecloudctl to point it at the upstream. This is where TLS is configured. This is where OpenSSL needs to communicate with. Your upstream is being reported as fine and that it can be reached by rmfakecloudctl. Your rmfakecloud-proxy instance, on your device, is what you are failing to connect to.

I also had a question at the end of my last comment that you have not answered.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Sync seems to work partially, looking for help and alternatives #354

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment 12 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

Sync seems to work partially, looking for help and alternatives #354

Uh oh!

jpmvferreira Mar 8, 2025

Replies: 1 comment · 12 replies

Uh oh!

Eeems Mar 8, 2025

Uh oh!

Eeems Apr 7, 2025

Uh oh!

jpmvferreira Apr 13, 2025 Author

Uh oh!

Eeems Apr 13, 2025

Uh oh!

Uh oh!

jpmvferreira Apr 18, 2025 Author

Uh oh!

Uh oh!

Eeems Apr 19, 2025

jpmvferreira
Mar 8, 2025

Replies: 1 comment 12 replies

Eeems
Mar 8, 2025

jpmvferreira Apr 13, 2025
Author

jpmvferreira Apr 18, 2025
Author