Pydio Documentation Library

Deploy, administrate & extend Pydio

Pydio v8

Troubleshooting

WARNING This documentation is for Cells v1. Looking for Pydio Cells v2 docs?

In this section, we gather known installation problems with strategies to fix them.

Various Information

Files location

On a linux-like system, using the pydio user, you will find the Pydio files at the following locations:

  • Configuration: /home/pydio/.config/pydio/cells/pydio.json
  • Logs: /home/pydio/.config/pydio/cells/logs.
  • Data: /home/pydio/.config/pydio/cells/data

Installation issues

Progress freezes during browser install

  • No progress appears during install

During the installation process, if there is no progress bar but the console is still showing some activities; it is OK. A manual refresh at the end of the install will load the login page.

  • The wizard is stucked at the end of the install

After the install, if the page does not refresh automatically in ssl self-signed mode it is OK.
A manual refresh will load the login page.

Networking issues

Unable to bind port 443

You have configured the bind URL with port 443 and enable redirection of port 80. You get an error page "Unable to connect" when you try to connect.

Check the error log, if you sse such an error:

2018-05-21T10:55:57.532+0200   ERROR   pydio.grpc.gateway.proxy   Could not run   {"error": "listen tcp :443: bind: permission denied"}

You probably did not give permission to the cells binary file to use reserved ports. To fix this:

sudo setcap 'cap_net_bind_service=+ep' cells

0.0.0.0 address

If you wish to use the 0.0.0.0 address you must respect this rule, cells_bind has to be exactly like this cells_bind=0.0.0.0:<port> and cells_external=<domain name,address>:<port>, the port is mandatory in both otherwise you will have a grey screen stuck in the loading

Unable to log in

After a re-install, when trying to login, you get a could not load session store: securecookie: the value is not valid error.

This is bound to the part of the session mechanism that resides in the browser, on client side.

To solve the issue, get rid of all cookie for this site and refresh the page.

Still stuck?

In case you do not find the answer you are looking for here, please do not ask question in github issues, nor in Twitter or other social feed: our preferred communication channel is our Forum.

So, what should I do in case of:

And only if you're invited to:

  • Post a github issue: make sure to put as much detail as possible.
  • or submit a pull request.
Back to top