Linux AppImage: all libraries displaying 0/0 after successfully authenticating

Seafile Client
1

I recently reinstalled Linux and downloaded the latest version of the client AppImage. I’m able to authenticate, but all library categories display 0/0. I believe the server is functioning normally; my clients from other devices remain connected and syncing properly, and the web UI is mostly normal. (It’s failing to load my avatar, but I don’t know if that’s related). What information can I share to help troubleshoot this issue?

EDIT: The same thing is happening with the Windows client.

2

It sounds like the client is successfully authenticating but failing to fetch the library list from the API, and the missing avatar in the web UI suggests a broader issue with how the server is resolving paths or serving media.

To help narrow this down, could you provide the following information?

  1. Server Version: Which version of Seafile Server are you running?
  2. Client Logs: Please check the logs on the machine where you’re running the AppImage. You can usually find them in ~/.ccnet/logs/seafile.log. Look for any lines mentioning “failed to GET” or “SSL certificate” errors.
  3. URL Configuration:
    • Check your Service URL setting in the System Admin → Settings via the web UI. Does it exactly match the URL (including https://) that you are using to access the server?
    • If you are on a version older than 12.0, also verify the SERVICE_URL in ccnet.conf.
  4. Browser Console: In the web UI where the avatar is missing, right-click the page, select “Inspect”, and go to the Console tab. Are there any 404 or 500 errors related to loading the avatar? This might reveal if the server is pointing to the wrong domain or port.

Commonly, this happens if the server is behind a reverse proxy (like Nginx) and there is a mismatch in the port or protocol configuration.

3

Thank you very much for replying.

I performed a test by spinning up a second instance, to which the clients connected and displayed libraries correctly. This confirmed the issue was server-side. I reviewed all my logs and configuration files but couldn’t identify the issue. Ultimately I decided it was easiest to simply re-populate my data into the second instance. May not be a solution for everyone but got me squared away.

4

Thank you for the update! It’s good to hear you’re back up and running.

Setting up a fresh instance and migrating the data is a solid way to rule out persistent configuration or database state issues on the server side. While it didn’t pinpoint the exact cause in the original setup, it confirms the client itself (AppImage/Windows) was working correctly.

Since you’ve resolved this through migration, I’ll mark this topic as resolved. Feel free to start a new thread if you encounter any other issues!