Linux CLI seaf-cli using IP or internal url not working


#1

Hi,

I am installing seaf-cli on a Debian machine and trying to sync a library. I can’t get it to connect to an IP address or a internal DNS address that does not include “http : //” in the beginning.

I run:

seaf-cli sync -l 1798af03-a717-48f7-80e6-xxxx -s 192 . 168 . 0 . 96:443 -d /mnt/external_media/DocScans/ -u user@ myemail . com

I get the error:
urllib2.URLError: <urlopen error unknown url type: 192 . 168 . 0 . 96>

When I try to use the internal LAN URL I have set up with my Unbound DNS, seafile . mydomain . com, I get this error:
ValueError: unknown url type: seafile . mydomain . com/api2/auth-token/

I think the CLI Client needs the “http : //” in front, which for some reason doesn’t work on my internal unbound DNS as when I try to ping from my terminal, it doesn’t work and I get this error:

svarto@testVM:~# ping https : // seafile . mydomain . com
ping: https : // seafile . mydomain . com: No address associated with hostname

However, skipping the https : // works super:

svarto@testVM:~# ping seafile . mydomain . com
PING seafile . mydomain . com (192.168.0.96) 56(84) bytes of data.
64 bytes from Seafile . localdomain (192.168.0.96): icmp_seq=1 ttl=63 time=0.663 ms

Would really appreciate some help if anyone has any idea?


#2

You have to tell it the protocol. Either http or https. There is nothing wrong with it.

Ping does only take a destination on the other hand. Telling it to use some protocol is not supported and makes no sense at all (unless one expects it to do a request using the protocol and measure how much time it takes to respond - but something like that is not supported)


#4

I noticed that my firewall was blocking traffic and any protocol that was not ICMP.