Hello everyone, I am new to seafile, I have already uploaded all my information and I am very happy with seafile, and I have created a user for my wife…
When I go to see the user information, an error appears, I attach an image and if someone has had this problem and has solved it, I would appreciate your help.
Server: Ubuntu 22.04
Seafile Version: 10.0.0
I have this problem too! Any fixes?
Do we need to set permission for our admin user to see this information somewhere in the seahub_settings.py, or something like that?
I would like to see the info for my admin user because seadrive keeps on setting my root folder as an annoying abbreviation of my username…
EDIT:
I have found that the browser console is throwing up a 404 errors when trying to load those pages:
GET
https://seafile.xxxxxxxx.co.uk/api/v2.1/admin/users/user%40xxxxxxx.co.uk/?avatar_size=160
Status
404 Not Found
Version HTTP/2
Transferred 2.01 kB (3.73 kB size)
Referrer Policy strict-origin-when-cross-origin
DNS Resolution System
Is this page not being found because I’m looking for the page through https instead of http?
Steps to Troubleshoot:
Check the Logs: The Seafile logs usually contain useful information about errors. You can check the relevant log files to gather more insight on what’s happening.
Seahub logs (for errors in the web interface):
cat /opt/seafile/logs/seahub.log
Seafile logs (for backend errors):
cat /opt/seafile/logs/seafile.log
Look for entries that match the timestamp when you encountered the error.
Verify Database Connectivity: Sometimes, issues with the database can cause the interface to fail when fetching user information. Verify that the Seafile server can connect to the database:
Check your seahub_settings.py for the correct database credentials:
DATABASES = {
‘default’: {
‘ENGINE’: ‘django.db.backends.mysql’,
‘NAME’: ‘seahub_db’,
‘USER’: ‘seafile’,
‘PASSWORD’: ‘your_db_password’,
‘HOST’: ‘127.0.0.1’,
‘PORT’: ‘3306’,
‘OPTIONS’: {‘charset’: ‘utf8mb4’},
}
}
Test the connection to the database:
mysql -u seafile -p -h 127.0.0.1 -P 3306 seahub_db
If there is an issue with the database, it could explain why the user information is not being displayed.
Enable Debug Mode: Enabling debug mode in Seafile can help provide more detailed error messages.
Open seahub_settings.py and add or modify the following line:
DEBUG = True
Restart Seafile services:
sudo systemctl restart seafile seahub
With DEBUG enabled, Seafile will show more detailed error information on the web page, which can help you pinpoint the cause.
Check Browser Console: Sometimes the error is related to JavaScript or frontend issues. Open your browser’s developer tools (usually by pressing F12), navigate to the “Console” tab, and check for any error messages that appear when you try to load the user information page.
Clear Cache and Sessions: Sometimes session or cache-related issues can cause Seafile to display errors. Try clearing the cache and restarting the services:
sudo systemctl restart seafile seahub
Check for Missing Dependencies: Ensure all required packages and dependencies are installed, especially after an upgrade or fresh installation. Missing dependencies may cause certain features of Seafile, like user information, to fail.
In my particular case:
The error (PermissionError: [Errno 13] Permission denied) indicates that Seafile doesn’t have the necessary permissions to access or write to the cache directory (/tmp/seahub_cache/). This could be due to incorrect file or directory permissions.
Steps to Resolve the Permission Issue:
Check and Set Correct Permissions: Ensure that the user running Seafile has read and write access to the /tmp/seahub_cache/ directory.
First, check the current permissions:
ls -ld /tmp/seahub_cache/
If the directory is owned by the wrong user or group, change the ownership. Assuming Seafile is running under the seafile user, use the following command to set the correct ownership:
sudo chown -R seafile:seafile /tmp/seahub_cache/
Set the correct permissions for the directory:
sudo chmod -R 700 /tmp/seahub_cache/
Restart Seafile: After adjusting the permissions, restart the Seafile services to apply the changes:
sudo systemctl restart seafile seahub
Ensure Correct Cache Directory: It’s also a good idea to make sure Seafile is using the correct cache directory. You can configure a more appropriate location for the cache in the seahub_settings.py file by adding or modifying the following line:
CACHES = {
‘default’: {
‘BACKEND’: ‘django.core.cache.backends.filebased.FileBasedCache’,
‘LOCATION’: ‘/opt/seafile/seahub_cache/’, # Change this to a more appropriate path
‘OPTIONS’: {
‘MAX_ENTRIES’: 1000,
},
}
}
This changes the cache location from /tmp/ to a more permanent directory under /opt/seafile/, where Seafile should have the correct permissions by default.
Create Cache Directory (if not exists): If the new cache directory (/opt/seafile/seahub_cache/) does not exist, create it and assign the correct permissions:
sudo mkdir -p /opt/seafile/seahub_cache/
sudo chown seafile:seafile /opt/seafile/seahub_cache/
sudo chmod 700 /opt/seafile/seahub_cache/
Restart Seafile Again: Restart the services to apply the cache configuration change:
sudo systemctl restart seafile seahub