seaf-cli throws an HTTP Error 404: Not Found

[Guess Whoiam]

Hello,

let me start by thanking you seafile team members for the great efforts on developing this awesome peace of software.
I am using seafile for almost a year now, and am still amazed by its performance, reliability, flexibility and the rapid development over this period. If sharing files and folders directly from the desktop clients (preferably the linux ones :) ) would/will be available, all my "private cloud" dreams would be fulfilled. But that's another story.

One of my latest projects is to make my rasp-pi able to connect to my server via seaf-cli.
I could install seaf-cli on my pi thanks to the information found on this forum and that link.
However, trying to download an existing library via

seaf-cli download -l "id" -s "https://<server>:<port>" -d "/mnt/data/<folder>/" -u "user" -p "pass"

fails with the following error:

Traceback (most recent call last):
  File "/usr/bin/seaf-cli", line 791, in <module>
    main()
  File "/usr/bin/seaf-cli", line 787, in main
    args.func(args)
  File "/usr/bin/seaf-cli", line 394, in seaf_download
    token = get_token(url, username, password, conf_dir)
  File "/usr/bin/seaf-cli", line 210, in get_token
    token_json = urlopen("%s/api2/auth-token/" % url, data=data)
  File "/usr/bin/seaf-cli", line 183, in urlopen
    resp = urllib2.urlopen(req)
  File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
    return _opener.open(url, data, timeout)
  File "/usr/lib/python2.7/urllib2.py", line 407, in open
    response = meth(req, response)
  File "/usr/lib/python2.7/urllib2.py", line 520, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python2.7/urllib2.py", line 445, in error
    return self._call_chain(*args)
  File "/usr/lib/python2.7/urllib2.py", line 379, in _call_chain
    result = func(*args)
  File "/usr/lib/python2.7/urllib2.py", line 528, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 404: Not Found

It doesn't matter if I use "seaf-cli sync" or "download", or use another valid library-id. The seafile-server is actually on the same machine behind an nginx setup, but neither the outward dns address works, nor "localhost" or "127.0.0.1" with the respective port.

Thanks for any help or clues to make it work,
Nix

[Guess Whoiam]

No idea what might be causing this problem, anyone?
Could it be related to my self-signed ssl certificate?

Here some further/condensed info of the setup:
 - server version is 4.0.1 running via nginx + fastcgi
 - configured for https/ssl - all working well and as expected
 - client v4.0.5 manually compiled for arm architecture following instructions by the given link

Is there a way to connect to the server locally? Used all localhost/127.0.0.1 and port combinations (8000,8082), but to no avail.

Thx again

[Guess Whoiam]

I have to apologize - it's a bit embarrassing to admit, but I simply forgot the subdomain(?) "seafile" in my server information.

seaf-cli download -l "id" -s "https://<server>:<port>/seafile/" -d "/mnt/data/<folder>/" -u "user" -p "pass"

So the message 404 came from nginx, as it's supposed to.
Everyting working neatly now - Sorry again!

Nix

Am Dienstag, 6. Januar 2015 03:33:31 UTC+1 schrieb Guess Whoiam: