From 5b7bde22e7057775d5d55983c43fb677bce4f25e Mon Sep 17 00:00:00 2001 From: feiniks <36756310+feiniks@users.noreply.github.com> Date: Sun, 9 Jul 2023 17:38:44 +0800 Subject: [PATCH] Checking notification server status (#171) * Checking notification server status * Update notification-server.md --------- Co-authored-by: heran yang Co-authored-by: Jiaqiang Xu --- manual/deploy/notification-server.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/manual/deploy/notification-server.md b/manual/deploy/notification-server.md index 3cb546350..9fc9a7d56 100644 --- a/manual/deploy/notification-server.md +++ b/manual/deploy/notification-server.md @@ -84,9 +84,16 @@ After that, you can run notification server with the following command: ``` +## Checking notification server status +When the notification server is working, you can access `http://127.0.0.1:8083/ping` from your browser, which will answer `{"ret": "pong"}`. If you have a proxy configured, you can access `https://{server}/notification/ping` from your browser instead. + ## Compatible client 1. Seadrive 3.0.1 or later. 2. Seafile client 8.0.11 or later. +If the client works with notification server, there should be a log message in seafile.log or seadrive.log. +``` +Notification server is enabled on the remote server xxxx +```