Linux Joplin App keeps sending reset TCP RST packets to webdav server

ikwyl6 · 19 March 2024 23:42

As I'm continuing to work on my firewall rules for my https/webdav server, I notice that joplin linux desktop app always sends RST packets to the webdav server. Do we know why? I'm not sure that this is typical...

Upon startup of the Joplin app, the app includes to send five (5) TCP RST packets to the webdav server. Any ideas why Joplin would want to reset the TCP connection? I get no errors upon synchronisation.

roman_r_m · 19 March 2024 23:46

I remember fixing a similar issue, might be a regression.

roman_r_m · 20 March 2024 21:37

I have tried to replicate this but could not. Maybe it's because I was running apache locally and used plain http rather than https.

ikwyl6 · 20 April 2024 11:25

Do you remember which issue# it was or commit that you fixed?

roman_r_m · 20 April 2024 13:15

One of these

github.com/laurent22/joplin

Desktop: Speed up WebDAV/Nextcloud sync by ~30% (or even more)

laurent22:dev ← roman-r-m:http-keep-alive

opened 09:40PM - 05 Mar 21 UTC

roman-r-m

+1 -1

(Sorry for the catchy title, couldn't help myself.) Due to a typo Keep-Alive …wasn't sent so each time http connection has to be re-established from scratch). I have tested this with a server in my local network using plain http and got these results: * Before the change ``` 21:10:38: CommandService::execute: synchronize false ... 21:13:34: Sync: finished: Synchronisation finished [1614978638697] ``` almost exactly 3 minutes * After the change ``` 21:21:15: CommandService::execute: synchronize false ... 21:23:19: Sync: finished: Synchronisation finished [1614979275473] ``` ~2 minutes, so 30% speedup. For https I expect the effect would be even greater. Not too bad for a one-symbol change. Total synced volume was 188,621,312 bytes, items: ``` main-html.js:48 21:23:19: Operations completed: main-html.js:48 21:23:19: createRemote: 1264 main-html.js:48 21:23:19: fetchingTotal: 1265 main-html.js:48 21:23:19: fetchingProcessed: 1265 main-html.js:48 21:23:19: Total folders: 27 main-html.js:48 21:23:19: Total notes: 850 main-html.js:48 21:23:19: Total resources: 187 ``` PS Why is Linux-only? And why is httpAgent only used for WebDAV?

github.com/laurent22/joplin

Desktop: Set keep-alive for WebDAV/Nextcloud sync

laurent22:dev ← roman-r-m:webdav-keepalive

opened 12:33PM - 14 Mar 21 UTC

roman-r-m

+1 -1

This is a follow up to https://github.com/laurent22/joplin/pull/4625 I ran a …test on Windows 8: * Version 1.7.11 - no Keep-Alive ``` 22:56:40: Preparing scheduled sync ... 23:03:08: Operations completed: ``` ~6.5 minutes * Dev build with Keep-Alive ``` 21:33:49: Preparing scheduled sync ... 21:37:13: Operations completed ``` ~3 minutes The sync was pretty fast as the server was on the same network and did not have https. As with Linux, I expect the difference to be much higher with https enabled.

Topic		Replies	Views
Webdav sync problem after webdav address change Support	7	1371	2 July 2021
Joplin webdav reupload fails Support	13	491	24 October 2022
Moving my WebDAV server Support	10	1060	22 November 2022
Joplin server AND webdav (or local files) export Support	2	923	16 July 2022
Support for Rclone? Support	6	683	23 April 2021

Linux Joplin App keeps sending reset TCP RST packets to webdav server

Related Topics