Seafile community edition 10.0 is ready!

Announcement
21

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”

nginx.config

location /notification/ping {
proxy_pass http://127.0.0.1:8083/ping;
access_log /var/log/nginx/notification_access.log seafileformat;
error_log /var/log/nginx/notification_error.log;
}
location /notification {
proxy_pass http://127.0.0.1:8083/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “upgrade”;
access_log /var/log/nginx/notification_access.log seafileformat;
error_log /var/log/nginx/notification_error.log;
}

docker-compose

ports:
  - "127.0.0.1:80:80"
  - "127.0.0.1:8080:8080"
  - "127.0.0.1:8083:8083"
22

Found the problem

with docker use that without the host part and it works.

Hope that helps.

[notification]
enabled = true
port = 8083
log_level = info
jwt_private_key = ‘xxx’

23

How to check if the notification server is actually working? The log says

2023/06/15 13:22:40 notification server started.

but I cannot see anything anywhere on the clients.

24

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.

2 Likes
26

Thanks,

is returned. :+1:

I am using client v9.0.1 (Win11 & 8.0.5 for debian) and I thought that it could be visible from somewhere within the client.

27

There is a log message in the client log, if notification server is used. The message is like:

Notification server is enabled on the remote server

28

I have

applet.log
events.log
seafile.log

in the logs folder but in neither of them I can find any referral to the notification server. Is that where I should look?

30

Hmm… I cannot find that, the only reference to ‘notification’ is:

[06/26/23 22:48:45] libcurl failed to GET https://seafile.domain.net/notification/ping: SSL connect error.

However, when I connect to the address manually in a browser, it returns

{"ret": "pong"}

Seeing as this happened several days ago, shouldn’t either this error be visible more often or the success message as in your log snippet?

32

Stopping, deleting and restarting was the solution. Somehow restarting it alone did not work.
Thanks! :slight_smile:

1 Like
33

hi all,
when I want to visit file version history,
it’s very slow to load the result using seafile10.0.1 via web browser

34

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