-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it possible to connect macOS or iOS apps to rmfakecloud? #300
Comments
I realized I was wrong and I didn't really log in. I just realized that typing in 8 random letters takes me to the app's file screen,, well I'm even more confused. |
I can see the rmfakecloud docker logs
|
in order to make the mac/ios app work, you will need a reverse proxy with ssl enabled and a self-signed certificate in front of rmfakecloud (nginx e.g.), then make the device trust the ca used to sign that certificate, then make your dns point the domains below to your instance
|
Hey, I suspect an issue with my certificate, but since I couldn't find any logs for the remarkable app on windows I'm not sure. Have a great day |
have you tried re-paring the app after the proxy is enabled?
I have no experience with windows systems tho
…On Sun, May 12, 2024 at 20:42, Thomas Roux ***@***.***(mailto:On Sun, May 12, 2024 at 20:42, Thomas Roux <<a href=)> wrote:
> in order to make the mac/ios app work, you will need a reverse proxy with ssl enabled and a self-signed certificate in front of rmfakecloud (nginx e.g.), then make the device trust the ca used to sign that certificate, then make your dns point the domains below to your instance
>
> hwr-production-dot-remarkable-production.appspot.com
> internal.cloud.remarkable.com
> local.appspot.com
> my.remarkable.com
> ping.remarkable.com
> service-manager-production-dot-remarkable-production.appspot.com
> webapp-prod.cloud.remarkable.engineering
Hey,
Did you have additional information about how to make the windows/mac app work with rmfakecloud ?
I tried to set up my reverse proxy to serve these domains with an certificates signed with my own CA (trusted by my devices, systemwide).
With a DNS override, I can access to the rmfakecloud API within my browser with no warning and by using the official endpoint (internal.cloud.remarkable.com).
But when I try to use the RM windows app, the sync does not work. Some thing strange is that when I enable my fiddler proxy (HTTPS flow analyser, use a user system trusted CA to sign all certificates for HTTPS trafic going through the proxy), the sync is working !
I suspect an issue with my certificate, but since I couldn't find any logs for the remarkable app on windows I'm not sure.
If you have an idea...
Have a great day
—
Reply to this email directly, [view it on GitHub](#300 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AD5XTCNW4ZTIC2ZF7CAPNO3ZB6SX3AVCNFSM6AAAAABGGAUR36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGMZDGOJWGU).
You are receiving this because you commented.Message ID: ***@***.***>
|
Pairing and syncing are working great with the proxy enabled but doesn't when it's disabled. |
what is acting as a proxy when your fiddler proxy is disabled? |
no you don't need to adjust the STORAGE_URL env variable. |
Here is my reverse proxy config (fake official API):
This is the reverse proxy config for the public access (lets encrypt certificate):
The discovery endpoint return the URL specified in the STORAGE_URL so I assume that I need to put my public domain, it is working with my tablet because rmfakecloud-proxy is installed on it and redirect all the trafic to my public domain. But for the official app, I don't know what I need to set... |
no need to change STORAGE_URL, leave it on your public domain.
|
Hey,
|
what is showing the nginx logs? |
and what version of rmfakecloud are you using? |
Specified in the last message :
Last version |
what do you get when you execute |
Found the problem, I tried to curl the API on Linux and it showed me an certificate error. The problem was that I didn't exported the full chain for my certificate used in NGINX. It create no problem with windows but linux/the remarkable app does not trust it. Problem solved ! |
To follow on integrating remarkable app with rmfakecloud, I managed to patch the android app to trust my own CA, with the correct DNS redirect the app is working flowlessly with rmfakecloud. Maybe it could be relevant to create a guide for user who want to use rmfakecloud with official remarkable apps... @y0grt |
it's quite dependant on the setup of each user, but the instruction here are relevant https://ddvk.github.io/rmfakecloud/remarkable/setup/ |
I apologize for what may seem like a stupid question. I hope someone can help me.
I have properly installed rmfakecloud using docker on hetzner's vps, and my remarkable2 can connect to my rmfakecloud properly, and also can upload documents and thus synchronize them to my remarkable2 through rmfakecloud webpage properly. i feel very much comfortable using it! I find it very comfortable to use.
However, I have both a macbook pro and an iphone, and I would like to synchronize them with my remarkable2. I noticed that rmfakecloud works on the principle of self-signed certificates for the official RMarkable sync server, and uses a reverse proxy to forward the sync requests to rmfakecloud, which in turn provides a great alternative to the official RMarkable sync server - very important for me in mainland China. As you know, in mainland China's network environment, remarkable's synchronization service is completely unavailable.
I use Surge as my proxy/VPN software on my macbook pro and iphone. Surge is essentially a network debugger with MitM and Rewrite. This made me think of rmfakecloud, the principle of rmfakecloud seems to use MitM and Rewrite. so I tried to transfer the requests to the remarkable sync server to my rmfakecloud in Surge, here is my config file:
After deployment, I opened the remarkable app on both ios and macOS. I entered the one-time code I got from rmfakeable. Luckily, I passed the verification and went to the normal interface of the app. But, strangely, the file is empty here, and obviously not synced up with my rmfakecloud -- even after having logged in successfully.
Am I missing some important domain name related to synchronization?
The text was updated successfully, but these errors were encountered: