Open teymour-aldridge opened 3 years ago
Is this for your own self-hosted server or on our server?
Your server.
Potentially an infinite loop in the client? Can you open the Network tab in the dev console in the desktop/web app and see if you're seeing runaway sync requests?
I am also having this issue on a self-hosted server.
I have about 177 notes and only 47 of them are being synced.
I have tried signing in and out and rebooting my sync server. It only seems to sync the same 47 notes.
This happens right after an unencrypted import of my notes...
The Error I am getting just says "Sync Unreachable"
Can you open the dev console and see if there are any exceptions reported? Also open the Network tab to see if there is an endless amount of requests being initiated.
@moughxyz
dev console
Pardon my ignorance... I am having a hard time figuring out where this is. I don't see a network tab either...
If using the desktop app choose the top level Help > Open Error Console menu. Then choose the Console tab or the Network tab.
I apologize, I was trying to do this with the web app.
Here is what I see:
Everything's pointing at a 413 Error (Entity Too Large)
Hmm, how big is the backup file you're importing?
1.8 Mb
About 205 Notes including items in the trash.
Here's something different. Don't know if its related.
How are you hosting your server? Is it behind Nginx? Check to see what the maximum payload size your server is allowing. Nginx may default at say 1MB.
Thanks for the help!
I was able to do this by following these instructions:
Open this file. /etc/nginx/domain.tld.conf/snserver.conf domain.tld is your domain (Could be a different path, but than I have to take a look)
And put this after Line 8
# set client body size to 2M client_max_body_size 2M;
You can also try and increase the 2M, if it is not enough.
After that you need to reload nginx.
sudo systemctl reload nginx
As mentioned here: https://github.com/YunoHost-Apps/snserver_ynh/issues/34#issuecomment-1062108808
I keep getting this error in the web and desktop apps.
(this might need fixing in the Desktop app instead of on the server, not sure though)