Tablet is not syncing (Notifications Socket is Not OK?) #235
Comments
|
the tablet doesn't trust: |
|
I'm using let's encrypt, the tablet trust |
These lines lead me to believe that it doesn't trust it though. Did you test the curl call from the device, or your computer? |
Sorry for late answer, I can curl from the device without add untrusted cert: root@reMarkable:~# ./installer.sh gencert
CA exists
Private key exists
Pub key exists
crt exists
root@reMarkable:~# curl https://remarkable.redacted
<!doctype html><html lang="en"><head><meta charset="utf-8"/><meta name="viewport" content="width=device-width,initial-scale=1"/><meta name="theme-color" content="#000000"/><meta name="description" content="RM FakeApi"/><title>rmfakecloud</title><script defer="defer" src="/static/js/main.9c2de5b1.js"></script><link href="/static/css/main.d94d89ba.css" rel="stylesheet"></head><body><noscript>You need to enable JavaScript to run this app.</noscript><div id="root"></div></body></html>root@reMarkable:~# |
|
Continuing error reporting of sync here instead of #237 I tried:
log.txt shows successful pairing but then the following errors: I checked the setting in
Bit stumped as to what may be the cause of failed tablet-> server sync Looks like the main error is Any ideas? |
|
is there something in the rmfakecloud's logs with "notifications" ? |
|
I think this may be caused by a mismatch between the SSL ciphers on the remarkable and the nginx reverse proxy: When testing On the A connection from other clients is fine. So, I think the remarkable is trying to use an old cipher/SSL version and the nginx server rejects it. Tried to loosen the default ciphers with the following in nginx reverse-proxy, but still getting the error: Any ideas which cipher may be needed? I guess this also explains why it stopped working (nginx server update woud have restricted old, insecure ciphers) |
|
wget on the rM doesn't support SSL at all out of box, but that isn't related to the proxy. You can grab a version of it that does work to use for testing here: http://toltec-dev.org/thirdparty/bin/wget-v1.21.1 |
|
Thanks for tip regarding wget |
|
Related issue? Change to the problematic configuration. Note that these are the only changes to the above working config: Rebooted the tablet. Sync is still not working, xochitl log still shows the "notifications" error. The weird part? Packet capture no longer shows the port 443 traffic. Changed capture location to the router/AP (OpenWRT), and there is zero traffic (on any port) coming from the tablet when the xochitl errors occur. My initial thought was a hardcoded sync call to 443, but post-reboot I'm stumped. I'm not familiar enough with the various bits to perform deeper inspection / logging on the tablet (are there debug settings for -proxy?). Happy to dig deeper, just point me in the right direction.
|
|
I'm also seeing
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name hwr-production-dot-remarkable-production.appspot.com;
server_name service-manager-production-dot-remarkable-production.appspot.com;
server_name local.appspot.com;
server_name my.remarkable.com;
server_name internal.cloud.remarkable.com;
server_name ping.remarkable.com;
ssl_certificate_key /etc/nginx/proxy.key;
ssl_certificate /etc/nginx/proxy.bundle.crt;
include /etc/letsencrypt/options-ssl-nginx.conf;
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;
location / {
proxy_pass http://tunnel;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto https;
proxy_redirect off;
}
}(proxy.key, and proxy.bundle.crt are generated with the rmfakecloud-proxy install script) The result is pretty much the same: Pairing works, sync doesn't. Same I'm not sure what else I could try. Unfortunately I haven't been able to get termshark working on the tablet. Does anyone know of a static build? Update: #271 fixed the issue for me |
|
The error The notifications service creates a websocket, and after 1 minute without any exchange between rmfakecloud and the tablet, nginx takes the initiative to close the connection. This error occurs, and on the server side, we can see a warning: This is not a problem as the tablet reconnects a few seconds later. It can be delayed with nginx by adding @mfussenegger I just create a pull request for the 3.8 release. |
Hi,
Since a few months, my tablet does not synchronize with RMFakecloud. I use the most recent Docker image (tag: always) and my remarkable is up to date (3.2.3.1595).
In log.txt, I have this message :
When I install rmfakecloud with 'magic script', I have a sed error:
but the reverse proxy is runned and fonctionnal:
(192.168.1.84 is my laptop. I tested the reverse proxy with the IP of the tablet)
Do you have any solution ? Thanks in advance
The text was updated successfully, but these errors were encountered: