Skip to content

Notification Server in Seafile cluster

In Seafile Pro edition, the notification server is the same as community edition notification server.

If you enable clustering, You need to deploy notification server on one of the servers. The load balancer should forward websockets requests to this node. The notification server configuration corresponding to each node of the cluster is as follows.

The notification server configuration should be the same as in community edition:

enabled = true
# the ip of notification server.
host =
# the port of notification server
port = 8083
# the log level of notification server
log_level = info
# jwt_private_key is used to generate jwt token and authenticate seafile server
jwt_private_key = M@O8VWUb81YvmtWLHGB2I_V7di5-@0p(MF*GrE!sIws23F

You need to configure load balancing according to the following forwarding rules:

  1. Forward /notification/ping requests to notification server via http protocol.
  2. Forward websockets requests with URL prefix /notification to notification server.

Here is a configuration that uses haproxy to support notification server, and haproxy version needs to be >= 2.0. You should use similar configurations for the other load balancers.


# Other existing haproxy configurations

frontend seafile
    mode http
    option httplog
    option dontlognull
    option forwardfor
    acl notif_ping_request  url_sub -i /notification/ping
    acl ws_requests  url_sub -i /notification
    acl hdr_connection_upgrade hdr(Connection)  -i upgrade
    acl hdr_upgrade_websocket  hdr(Upgrade)     -i websocket
    use_backend ws_backend if hdr_connection_upgrade hdr_upgrade_websocket
    use_backend notif_ping_backend if notif_ping_request
    use_backend ws_backend if ws_requests
    default_backend backup_nodes

backend backup_nodes
    cookie SERVERID insert indirect nocache
    server seafileserver01

backend notif_ping_backend
    option forwardfor
    server ws

backend ws_backend
    option forwardfor # This sets X-Forwarded-For
    server ws