Seafile 10
Linux Ubuntu server 22.04
As you can see from the picture the location “https://cloud.xxxxxxxxxx.co.uk/api/v2.1/admin/users/?page=1&per_page=25” is accessable, but anything to do with the user is getting 404.
This gives me an error inside the “users” section of the “system admin” dashboard.
I have found that if I try to access:
curl -I https://cloud.xxxxxxxxxx.co.uk/api/v2.1/admin/users/admin%40seafile.local
I get:
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Wed, 11 Oct 2023 17:46:18 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 0
Connection: keep-alive
Location: /api/v2.1/admin/users/admin@seafile.local/
Vary: Accept-Language
Content-Language: en
Update:
Okay, I think I might be onto something -
My URL seems to be changing the “@” sign in the url to “%2540” when the address is at “%40”
Maybe some kind of character encoding thing?
If I go to the addresses at “%40” I can see the data.
Nope, I don’t think that is the problem:
This is why
It is interesting that I can find the data through the URL and seafile can’t, though.
Here is another piece of information if anyone reads this…
I might be wrong here:
but i think the problem is coming from the file seafile-api.js (the file compiled in the browser)
It appears that the property “_ref” coming from init() doesn’t have the “server” property and "should be
var server = _ref.origin
I’ve looked for this file in the same place “media/assets/…” but it must be put together at runtime or something?
Where can I find this file? I’ve seen its on github and I can install it? Should I do this?
seafile-api
Anyone got any ideas or fixed this themselves?