I have the same problem tried it with the manual without success.
No pong or anything else
notification-server.log
2023/05/17 14:23:38 notification server started.
2023/05/17 14:29:14 notification server started.
2023/05/17 14:50:36 notification server started.
2023/05/17 19:29:00 notification server started.
2023/05/17 19:31:06 notification server started.
2023/05/17 19:47:47 notification server started.
nginx error log
2023/05/17 19:29:45 [error] 365884#0: *37 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 11.22.33.44, server: xxx.yyy.zz, request: âGET /notification/ping HTTP/2.0â, upstream: âhttp://127.0.0.1:8083/pingâ, host: âxxx.yyy.zzâ
2023/05/17 19:29:45 [error] 365884#0: *37 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 11.22.33.44, server: xxx.yyy.zz, request: âGET /notification/ping HTTP/2.0â, upstream: âhttp://127.0.0.1:8083/pingâ, host: âxxx.yyy.zzâ
Hello @Cantello, which version of client are you using ? Have you configured nginx/apache correctly? There is the {server}/notification/ping endpoint you can access from your browser, which should answer {"ret": "pong"} when the notification server is working.
this notification line is displayed each time the desktop client is started. [06/27/23 15:44:32] Notification server is enabled on the remote server https://XXX.YYYYY.ZZZ.
try to close the desktop client, delete the log files, and restart the client, this line should appear at the beginning of seafile.log
this is how it works on my pc
if Libraries is several MB in size, itâs fast.
if Libraries is 20 GB in size, itâs slow.
if Libraries is 1 TB in size, itâs very slow to get the version history.
didnât see this in community docker deployed version before 10