Hello @freezziey, can you test this with the latest seafile client 9.0.3.Seafile 9.0.3 has modified some conditional compilation, which may affect the notification of the last version of the client.
Same behavior with 9.0.3
Hello @freezziey , can you set the SEAFILE_DEBUG environment variable to āNotificationā, and then try to start the client? There will be more logs about the notification server under seafile.log. For how to set environment variables on Windows, refer to Create and Modify Environment Variables on Windows . After you test it again, you can send the complete seafile.log to support@seafile.com.
I currently have lost access to the windows client as i mostly use linux. Will do asap.
I checked again on Windows. Now the log appears
On the first Windows test i did not check the log and only tested on linux. That explains that.
The issue remains existant on linux. How can i set the DEBUG log mode on linux for the client?
I fixed it.
Iām running seafile in docker and the host of the notification server is set to 127.0.0.1 by default, i.e. it only listened inside the container. Setting host = 0.0.0.0 in the seafile.conf resolved the issue.