PydioSync with Cells > Not yet ready


#1

Hi everyone.
I recently changed my installation from Pydio 8 to Cells. The truth is that I do not see significant improvements, but that is irrelevant now.
The problem is that now the PydioSync client does not connect, it always shows the following error:
Error while trying to connect to https://xxxxxxxxxxx :
An SSL error happened! Is your server using a self-signed certificate? In that case please check ‘Trust SSL certificate’
The certificate is valid and works on all common browsers (Chrome, Firefox, Safari, Opera). There is no way to connect, even if I leave checked the option “Trust SSL certificate”.
I have tried from 3 different clients (all with macOS 10.13) and shows the same error on 3 Macs. On Windows 7, client works fine and can connect without problems.
The server is Pydio Cells Home Edition 1.0.1 on Centos 7.
Regards.


#2

Hi,
right now we are working on a pydio sync for cells,
i will keep you updated when there will be more informations.


#3

Hi Zayn
I run Cells in a docker env on a ubuntu host. installation is up and running.
I have share directory on host with bind mount that is picked up as a datasource and visible in workspace.
host ip 192.xxxxxx, container ip 172.xxxx

a) But how can I create a datasource chosing the host as in the peer-list ?
b) Any difference if container configured with ip on host network 192.xxx ?
c) Is it only os with a Cell installation that can be chosen as peer or even via ftp?
d) Another way would maybe be to install a sync client on the host, I run a server without desktop. Any linux sync client with poosibility to be managed by cli ?

Appreciate some clarification on above 4 questions as I havent found them in the docs.

Regards

J


#4

Hi,

a): Because it’s a container it’s on the host, if you want the data just create a volume and it will be stored on your local machine even though you are selection the docker address.

b)you can use the same ip as the host, you just have to map the good port for the internal and the external that you chose for your container.

c)

i didnt get that one,

d) Having a sync on the host kinda kills the purpose of the sync client, as for the linux version it’s on our roadmap.


#5

On point c)
Right now I have my container configured with bridge network giving it a 172 address. But if I choose host network giving it the hostadress what is then defined as peers? Other servers on the LAN through sftp/ftp?
I mean a different server/host on the LAN. Can they appear in the peer list? Does it require a cells installation to be a peer?
Or do I have to mount other servers on the host through nfs/cifs shares?
/J


#6

Hi,
on the peers will only appear the cells server for you case the container, even though you access the container using the ip of the machine that is running the container, right now i’m unsure but i believe that you will be able to run storage on another machines and link it to your pydio cells through the ip with the peer field.


#7

Hi Zayn,

Will you keep us updated here in the forum? We have an enterprise license, but are fond of Pydio sync. And I would like to use Pydio Cells.
What to do? :wink:
Marten


#8

Hi,
right now we are still working on it, doing heavy testing and we still have stuff to fix,
i cannot give you a exact deadline but when it will be finished you will see it on our site, twitter etc …


#9

Hi there,

The current version of the Pydio Sync client does not have support for Pydio Cells. But it’ll be available soon.

Besides, we’ve been improving The Pydio Sync client and here below is a link to download the latest versions for Wondows and OSX:

https://download.pydio.com/pub/pydio-sync/develop/packages/

Regards


#10

Same problem, watch on it.


#11

Hello folks,

Any news on this matter?

Thanks, Marten


#12

Hi Marten,
Please be patient and stick to P8 if you wish to use the Sync Client. We want to make sure that when we give a go for Sync + Cells it’s a real go, not a half-baked stuff. This requires some significant optimizations on the server side. Now that we finally removed PHP totally, this is definitely on a good path.
-c